Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. All pooled connections were in use and max pool size was reached.
The application’s connection pool was exhausted — all connections busy or leaked.
obtaining a connection from the poolmax pool size was reached Meaning
Connections not disposed/closed, long-running queries, or more concurrent requests than Max Pool Size (default 100 in ADO.NET).
Common causes
- Connections not disposed (missing using/close)
- Long queries holding connections
- Traffic spikes beyond pool size
⚡ Quick fix
- Always dispose connections (using/await using)
- Find slow queries and blocking
- Tune Max Pool Size with DB capacity in mind
Detailed fix by platform
.NET
await using var conn = new SqlConnection(cs); await conn.OpenAsync();
How to diagnose
- Pool — In-use vs max?
- Leaks — Connections closed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026