The particular kb article says this problem was fixed in SP2. Installing SP2
or later should fix it.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
Hi Hilary
As soon as you can see, i´m not apply a SP4, but SP3a and hot fix ms031 was
apllied.
Any suggestions ?
In article 308797 , exist a reference for a particular hotfix.
How can I get this hotfix ??
TIA
> The particular kb article says this problem was fixed in SP2. Installing SP2
> or later should fix it.
[quoted text clipped - 28 lines]
> >
> > http://go.microsoft.com/fwlink/events.asp.
Hilary Cotter - 17 May 2005 22:23 GMT
I don't see where it mentions a hot fix. I do see this:
STATUS
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2
It is probable that the sp was not applied correctly, I would try to really
SP3 and ensure you upgrade SQL FTS. It is possible that there has been some
corruption of mssdmn.exe

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
> Hi Hilary
>
[quoted text clipped - 45 lines]
>> >
>> > http://go.microsoft.com/fwlink/events.asp.