Hotfix for Bug # 473675 (SQL Server could not spawn process_loginread thread)

sc_simsl

Hi,

I get "SQL Server could not spawn process_loginread thread." errors. This is related to a bug in SQL 2000 and there is a hotfix for SP3a.

I am running SQL2000 with SP4. I checked the fix list of SP4 & this bug is not fixed in this SP4.

Can I apply the hotfix to resolve this problem on my server

tia.

JohDas

Hi,

SP4 is a superset of SP3,SP2,SP1

So this hotfix must be included in SP4.

You can't easily relate error messages and hotfixes, it could be another reason you are getting this message. Read carefully what the hotfix fixes, relate it to the situation you are dealing with and judge if the hotfix is relevant enough to your problem, so as to risk applying it.

Some more info (complete error message, hotfix info, when and where you get the error message) would help

Himanish

I am also facing the same problem..though we are using SP3.

Will upgrading to SP4 help

Do we need to do something else to get rid of the problem

Jerome Halmans

The most common cause of this message is a lack of free virtual address space. The most common cause of virtual address starvation on SQL 2000 are misbehaving com components from the use of sp_oacreate, misbehaving extended stored procedures, or poorly written OLEDB providers that are loaded by the use of linked servers.

Start by reviewing your use of these items and remove them from the system as possible.

Ron Van Zanten

Jerome,

This is an event that happens on our production server about once a week. It only lasts for 2-5 minutes. We are running SQL 2000 SP4. Is there any way to adjust the memory allocation

Thanks in advance.

Ron