ERROR: SQL Server could not spawn process_loginread thread

  • After SQL Server option change we got this error. SQL server didn't allow any client connections and the only way to bring it to normal work was the restart. 

    Let me provide last events from SQL server logs:

    Configuration option 'nested triggers' changed from 1 to 0. Run the RECONFIGURE statement to install.

    Error: 15457, Severity: 0, State: 1

    Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..

    SQL Server could not spawn process_loginread thread.

    this error had shown up about 10min till we restarted the server

    After some google I've found that this error tells about memory leak. Our SQL server memory configuration was set to dynamic from 0 to 4GB.

    Our version:

    Microsoft SQL Server  2000 - 8.00.2039 (Intel X86) (sp4)  May  3 2005 23:18:38   Copyright (c) 1988-2003 Microsoft Corporation  Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

     

    Does anyone know what causes were of this?

  • If it started occuring because you changed an option then I do not have any idea about the possible causes for it. But there are several issues listed at Microsoft knowledge base where the symptoms includes this message. One of them that I have encountered myself is when you cancel a remote query, and another one discusses memory problems when there are very many databases on a server.

  • I had the same issue on the cluster server, and I did the failover, and then I reboot the server, and did the failover again that resolve this issue.

    Ripal.

  • I had same problem..how you resolve the issue??

  • I also have the same problem.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply