During a Litespeed backup or restore the application or even SQL Server may hang.
You receive a "Non-yielding Scheduler" error intermittently.
In the SQL Server error logs you may see the following error messages:
Process %ld:%ld:%ld (0x%lx) Worker 0x%p appears to be non-yielding on Scheduler %ld. Thread creation time: %time. Approx Thread CPU Used: kernel 0x ms, user 0x ms. Process Utilization 0x%. System Idle 0x%. Interval: 0x ms.
Or
error code 26073 - // ErrorFormat: TCP connection closed but a child process of SQL Server may be holding a duplicate of the connection's socket
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center