July 2, 2003 at 11:48 pm
SQL Server could not spawn process_loginread thread.
Running SQL 2000 Enterprise SP2 WITH hotfixes 8.00.679
on Win2k Advanced Server sp 2 with hotfixes
The following appeared in the sql server error log 13 times since the 30th of June
'SQL Server could not spawn process_loginread thread.'
Today (the 3rd July) The server died and had to be rebooted.
This appears to be a memory leak issue.
According to the following KB articles
FIX: SP_OA Procedures Leak Memory and Cause Various Errors
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B282229
FIX: Handle Leak Occurs in SQL Server When Service or Application Repeatedly Connects and Disconnects with Shared Memory Network Library
http://support.microsoft.com/default.aspx?scid=kb;en-us;317748
Now having contacted MS the FIX: SP_OA Procedures Leak Memory and Cause Various Errors was fixed in sp1 and they were adamant that it had not been reintroduced (not sure if i believe them)
The second fix
FIX: Handle Leak Occurs in SQL Server When Service or Application Repeatedly Connects and Disconnects with Shared Memory Network Library
i'm very wary about applying as the server already has hotfixes .
Anyways has someone come across this error before ? is there any workaround ?
July 3, 2003 at 10:14 pm
As far as i can tell we do not use SP_OA Procedures
Does SQL Mail use them ???
July 4, 2003 at 12:26 am
No help to solving your problem
http://dbforums.com/arch/70/2002/11/549598
Maybe one them have found a work around.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply