I have a ASP.net 2.0 application running on a server(s) and all is well. Almost.
The
two load balanced ASP machines are running Windows Server 2003 and IIS
6.0, and it's on a local connection to a Windows Server 2003 running MS
SQL 2005. I am using the SQL method of state, as the load balancing
means you never really know which server you are pulling from. The
website files are common though, something through DFS, my IT guys tell
me.
When a particular operation is completed on the ASP website,
intermittently, the ASP application can no longer make a connection to
the SQL server. SQL appears to be intact, as I can log into it from
multiple locations, including locally, and even locally from the ASP
machine that the application cannot get to it from. The operation that
causes this is fairly simple, I gather some data from the .aspx page,
manipulate it, update the SQL server, it all goes well, the aspx page
reports everything correctly, and then that's it, we're done talking to
SQL apparently.
A server restart fixes this until the next time it happens, so, not really a fix. I cannot at this moment remember if an IIS restart works, but I don't think it does.
Could this be an IIS thing? OS thing? Some sloppy code causing this issue?
While the problem basically locks up the application, if you
wait a while, it goes away. Logins are stored in SQL and the customers
who have had this problem tell me that after they do this operation,
they can't do anythign anymore, can log in, but a few hours later all
is well with the world, and that the operation that caused the problem
appeared to work fine.
I have no other ASP.net applications running on this server to see if they go down too when the main one goes down, but I suppose I could whip something up. This problem has never happened on my development machine ever
I
am not an expert debugger, so I have no idea where to even start. I
don't have Visual studio on the deployment machine, so I cannot get to
errors in a way I know how, although I am sure I can check a log
somewhere to see what the actual problem is.
Any ideas what
this could be, or how I could better find the problem or force the
symptoms and better diagnose it? I have similar post in the ASP.net forums.
If anyone has any ideas of how to detect and band-aid this problem in the mean time, I would also love to hear that. Some script I can write to reboot IIS every 5 minutes or something. I am grasping here.
Thanks in advance for any tips, suggestions, miracle cures, or divine inspiration you may lend,
Jason