Reply to thread

Message

<blockquote data-quote="chriton227" data-source="post: 4536094" data-attributes="member: 33263">I'm still getting the 500 error too.As someone who develops web applications for a living, a default 500 server error is one of those things you never want to intentionally send to your clients/customers.&nbsp; If the site is going to be down for maintenance, you put up a page to that effect, preferably with an estimate of when the site will be back up (especially for scheduled maintenance).&nbsp; If the user is getting a 500 error, that means the web service is up and processing requests, but that there is a server side problem.&nbsp; Most of the times I have seen 500 errors, it wasn't because of a scheduled outage, but rather a problem in the code or something like an out of memory issue with the server itself.&nbsp; If they had fully taken the server down for maintenance then the service wouldn't be responding at all, so there wouldn't be anything there to send back the 500 error (you would get a DNS error or server not found error). Most companies I know of also don't take their sites down during the day for scheduled outages, they try to do it during the lowest usage times (typically the middle of the night). The Wizards site uses Microsoft Active Server Pages, so they are more than likely running a Windows/IIS back end.&nbsp; If that is the case, it only takes about 5 clicks to set the server to display a user friendly error page with support contact information instead of that generic 500 error.&nbsp; Also, for the vast majority of things, you don't have to take IIS down to install new apps, usually the most you have to do is restart the service (only takes a couple minutes max).&nbsp; Seeing the Wizards site down for 2+ hours without even getting a &quot;experiencing technical difficulties&quot; page put up doesn't instill confidence for me in the quality and support for the DDI apps.Edit: I just tried going to the base site (http:\\<a href="http://www.wizards.com" target="_blank">www.wizards.com</a>) and got a VBScript out of memory error.&nbsp; So it seems like this truly is a server issue, not a scheduled outage.</blockquote>

[QUOTE="chriton227, post: 4536094, member: 33263"] I'm still getting the 500 error too. As someone who develops web applications for a living, a default 500 server error is one of those things you never want to intentionally send to your clients/customers. If the site is going to be down for maintenance, you put up a page to that effect, preferably with an estimate of when the site will be back up (especially for scheduled maintenance). If the user is getting a 500 error, that means the web service is up and processing requests, but that there is a server side problem. Most of the times I have seen 500 errors, it wasn't because of a scheduled outage, but rather a problem in the code or something like an out of memory issue with the server itself. If they had fully taken the server down for maintenance then the service wouldn't be responding at all, so there wouldn't be anything there to send back the 500 error (you would get a DNS error or server not found error). Most companies I know of also don't take their sites down during the day for scheduled outages, they try to do it during the lowest usage times (typically the middle of the night). The Wizards site uses Microsoft Active Server Pages, so they are more than likely running a Windows/IIS back end. If that is the case, it only takes about 5 clicks to set the server to display a user friendly error page with support contact information instead of that generic 500 error. Also, for the vast majority of things, you don't have to take IIS down to install new apps, usually the most you have to do is restart the service (only takes a couple minutes max). Seeing the Wizards site down for 2+ hours without even getting a "experiencing technical difficulties" page put up doesn't instill confidence for me in the quality and support for the DDI apps. Edit: I just tried going to the base site (http:\\[url]www.wizards.com[/url]) and got a VBScript out of memory error. So it seems like this truly is a server issue, not a scheduled outage. [/QUOTE]

Verification