I was working on my DNN site and updated my module DLL's in the BIN directory for the site, and now when I go to see my DNN site all I get is the following, the application event log does not have any entries in it.  What would cuase the site to crash due to me updating 2 dll's in a custom module I have written?   Also how do I figure out what is going on?:

Server Application Unavailable

The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

That it the aspnet.exe recycling. It can take up to 20 minutes for it to reset itself and it may be coincidental that you were unlucky at the time it has reached it's maximum ram usage.

This can occur on any server, in fact I'm working with some network connection problems with my own server that are bringing up that error!! GRR..

If an administrator can see this problem, they can often log in via remote admin and reset the application, but it generally does rectify itself.

Not really a complete answer, but the other side is that you're custom dll has been incorrectly written, causing performance issues which also bring the server to a grinding halt.  Which is why I don't let developers on my server.  Custom Modules can do things to your server you never thought possible.

If it's local, you need to go to the task manager, processs, sort by alpha and look for the aspnet.exe - kill the process and then in some instances, you need to reset your web.config file, but first, I'd be removing those dlls to see if they aren't the cause.

All in a days learning!!

Nina Meiers

Thank you for the reply.   In my case it was a module that someone wrote for me that was not disconnecting from the SQL Server.   So it was opening connections and then never closing them.   I ended up having to do an IISRESET and then changing the code to make sure the SQL Connection had a .CLOSE() command added to it to make sure the connections where closed.  

So far it has been stable. 

ah ha!  I've been getting this error almost since day one.  I now always get it when I try to connect to the default/parent portal (e.g. mydomain.com/dnn).  Since I'm using all child portals right now I haven't needed (or wanted to spend the time) to debug it.

I'm on a borrowed server.  It's running Win2K, SQL, IIS all in 256Mb ram.  The root portal that gives me the problem is a default DNN 3.1 setup.  I ran the wizard on day one and simply chose club and picked some of the canned skins.  No outside customization, nothing other than core modules.  I do have 3rd party modules running on the child portals successfuly.

Does the root portal behave any differently than child portals?