By name: error-26078-state-15 description: In XDBHost, when a login request is dequeued we try to ensure that the login has not been in the queue for more than 10 seconds. If the login has remained in the queue for 10 seconds, xdbhost forcibly closes the named pipe connection with SQL and clears the socket duplication queue. While this is in progress, all logins in the queue fail with 26078/15 and all new incoming logins are failed with 40613/13.
Relative Error Codes
- Error 40613 State 13
- Error 40613 State 15
Potential causes
- Slow socket duplication: During the login process, XDBHost duplicates the client socket to establish a connection to the backend SQL instance. If the socket duplication is slow, it can lead to increased time holding locks on the login queue, causing other login requests to timeout.
- High login volume: If there is a sudden surge in login requests to a SQL instance, it can lead to increased contention for the login queue lock in XDBHost.
- HighCPU Consumption for XDBHost and LSASS.
- CPU Consumption for SQL instances: If the backend SQL instance is under heavy load and experiencing high CPU usage, it can lead to slower processing of login requests.
Troubleshooting Steps
Follow the skill and output after each step: .github/skills/Connectivity/connectivity-utilities/xdbhost-metric-check/SKILL.md