January 10, 2008 at 6:55 pm
Thanks guys for keeping this thread up. I've had this error for almost 2 years on a SQL 2000 SP4 server and can't see any fix to make it go away. There is no usefull info on the web until I see this thread.
January 10, 2008 at 8:24 pm
Did you read the following discussions? Hopefully, it will be helpful.
January 10, 2008 at 8:43 pm
That was an old post. btw we don't use NOLOCK in our queries.
April 23, 2009 at 11:30 am
Hi, did anyone find a solution to this error. We are running SQL Server 2000 SP4 on Windows 2003 and had this error on one of the production servers.
April 23, 2009 at 11:43 am
We no longer see this error on the server. I don't remember doing anything to fix it except patching the server with windows update.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply