Microsoft
Software
Hardware
Network
Question : Timeout problem
Hi all, here's the error:
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationExc
eption: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
And yes - I've read all of the other posts about this error. They don't seem to apply. This was working fine a few days ago and then it stopped. I have to rule out the code as being the issue. If I restart the IIS application, it will work - ONCE. Then will stop working. The code is identical to the code I use in other projects and I double checked that it's releasing connections when done.
There's only one person accessing the application, so I can't believe it's running out of connections with 1 user.
Any new suggestions? We're running Windows Server 2003, SQL2005. Just installed ASP.net 4.0, and I can't blame it on that because we have other apps running the same connection code just fine on the server.
Answer : Timeout problem
www.snapfiles.com/freeware
look for Spyware Terminator, install w/clam antivirus.
run in safe mode.
Random Solutions
Most commonly used and useful ESX Service Console commands?
PL/SQL Performance
Help With IIS Error MSDPLOY The AppPoolNotFound dependency check
IMAP, SSL or TLS
How do I have a field displayed in a report for all data options except one
Mapi example Microsoft
using Task.IsCompleted
Mikrotik Dst-Nat Problem with internal web server
Was there prophet school in Israel in ancient times?
recover missing emails - information store service stopped