M
Michael H.
One of the customer facing websites at the company I work for has been
locking up for awhile. To 'unlock' the server our support group has to
restart the application pool for this application. I have done some research
on the issue and added some additional logging and found that when this
lockup occurs we are receiving a "Server Error 500" when our login page is
calling an asp (legacy using remote scripting) page to check permissions and
setup the user. I also found that when this lockup occurs it does not affect
everyone; some people are still able to log in. I have looked at the users
that generate errors and there is no connection between them. I have also
verified that this happens when using secure and non-secure connections,
appears to happen at random and could be once a day or once a month, and it
continues until the application pool is reset.
This issue has not always happened and prior to it starting there were no
changes (that I'm aware of). Since it began the server has been setup again,
we've tried seperate application pools, and we've even tried a different
server (hardware) in case there was something odd going on with the hardware
itself that might be causing the problem. I've spent a good bit of time
looking at "Error 500" websites and so far I'm not finding anything that has
helped or that has pointed us in the right direction.
The server is a 64bit Windows 2003 R2 server. The website that locks up is
an older web site that runs a mix of classic asp, javascript, and a few .net
2.0 pages. We also use a fairly large amount of remote scripting and the site
is heavily database driven.
So to sum it up: we get "error 500" when our login page uses remote
scripting to call functions from a different file. It doesn't happen to
everyone. When it starts we have to restart the application pool to get it
working properly again. No correlation between the users or connection
(secure or non-secure). Server has been reconfigured and even replaced. The
function being called when we get the error is not always the same.
Sorry for the long post but wanted to try to give some information that
might help provide answers. Any advice or suggestions would be greatly
appreciated. Our goal is to try to isolate the issue to determine what is
causing the error and hopefully find a way to resolve it.
Thanks,
Michael
locking up for awhile. To 'unlock' the server our support group has to
restart the application pool for this application. I have done some research
on the issue and added some additional logging and found that when this
lockup occurs we are receiving a "Server Error 500" when our login page is
calling an asp (legacy using remote scripting) page to check permissions and
setup the user. I also found that when this lockup occurs it does not affect
everyone; some people are still able to log in. I have looked at the users
that generate errors and there is no connection between them. I have also
verified that this happens when using secure and non-secure connections,
appears to happen at random and could be once a day or once a month, and it
continues until the application pool is reset.
This issue has not always happened and prior to it starting there were no
changes (that I'm aware of). Since it began the server has been setup again,
we've tried seperate application pools, and we've even tried a different
server (hardware) in case there was something odd going on with the hardware
itself that might be causing the problem. I've spent a good bit of time
looking at "Error 500" websites and so far I'm not finding anything that has
helped or that has pointed us in the right direction.
The server is a 64bit Windows 2003 R2 server. The website that locks up is
an older web site that runs a mix of classic asp, javascript, and a few .net
2.0 pages. We also use a fairly large amount of remote scripting and the site
is heavily database driven.
So to sum it up: we get "error 500" when our login page uses remote
scripting to call functions from a different file. It doesn't happen to
everyone. When it starts we have to restart the application pool to get it
working properly again. No correlation between the users or connection
(secure or non-secure). Server has been reconfigured and even replaced. The
function being called when we get the error is not always the same.
Sorry for the long post but wanted to try to give some information that
might help provide answers. Any advice or suggestions would be greatly
appreciated. Our goal is to try to isolate the issue to determine what is
causing the error and hopefully find a way to resolve it.
Thanks,
Michael