Last post Feb 09, 2006 12:23 AM by HotFixer
Jan 26, 2006 06:11 AM|webguru03|LINK
Jan 28, 2006 08:05 PM|netguy|LINK
Feb 01, 2006 07:00 AM|webguru03|LINK
Feb 01, 2006 10:23 AM|netguy|LINK
Feb 02, 2006 06:39 AM|webguru03|LINK
Feb 02, 2006 02:56 PM|netguy|LINK
Feb 02, 2006 05:09 PM|nbc|LINK
OK, so it would be a server overload rather than anything to do with DNN...
Thats quite likely - if you could see the server performance at the same time you get this message you could see how busy it is, what the aspnet worker process is using memory wise etc.
But it could be a range of issues - for instance network access or a module you have in the DNN install.
Can you post your server config here (OS, memory etc)?
Feb 06, 2006 11:38 PM|webguru03|LINK
Yes, it can be other issues, but in most cases the server overload would be the cause. This installation is on a shared server, and I don;t have a precise config - it does not mean much anyway, it depends how load balancing is managed and how well the admin
addresses the issue when it comes up.
Feb 07, 2006 10:32 AM|nbc|LINK
You are on a shared server with load balancing?
As you say the error message is generated by IIS so is prob likely to be at that end but I have also seen this on DNN apps where there is an issue with the application (or a related one on the same box).
Feb 08, 2006 10:50 PM|webguru03|LINK
After discussion with the sysadmin I'm happy that there was no problem with my DNN installation. In fact on shared server it is not uncommon for an application to "behave badly" and that affects the rest of the server in acertain way. Usually memory leaks
and runs low, so plain HTML sites still serve OK (which was the case) but any web apps requiring memory take too long to serve so "Service Unavailable" is served as response instead...
If you are on a shared server you might see this from time to time. A good host would investigate recurring problems like this and shut down the "bad" application.
Feb 09, 2006 12:23 AM|HotFixer|LINK
This is a generic error message which can be cause by various reasons. One common reason is due to lack of permissions to ACL's or if IIS is unable to launch the aspnet_wp.exe worker process. (w3wp.exe in IIS 6.0)
The application event log will give you a lot more detail along with the event ID which can be used to find the root cause. What do you see in the event logs?