Error: 7886, Severity: 20, State: 1.

Hi All

I am seeing this error being logged in my SQL 2005 Ent machine

A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

It seems to be arising out of a read of a text column.

Any info on this will be appreciated. Thanks

K T

You're not running CTP version, right?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=233339&SiteID=1|||

No

Its build 9.0.2153

|||

Hi Kts,

Do you use Row versioning in you database?

I waiting for your answer.

Regards,

|||

No !

|||

Hi kts,

What you TRANSACTION ISOLATION LEVEL do you run the code?

Can you post the query here?

Regards,

|||

hi

Like the message says READ UNCOMMITTED . its actually just a select with NO LOCK. The problem is I can only guess which proc it is but not know for sure as I am not able to recreate the problem manually.

|||

Ah, you use 'nolock' hint. There are issues with using such hint. I suggest you take a look at the following KB.

http://search.support.microsoft.com/kb/235880

|||

I'm still having the same problem..

My sql query results about 100Mb of information.

What can I do?

Error: 7886, Severity: 20, State: 1.

Hi All

I am seeing this error being logged in my SQL 2005 Ent machine

A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

It seems to be arising out of a read of a text column.

Any info on this will be appreciated. Thanks

K T

You're not running CTP version, right?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=233339&SiteID=1|||

No

Its build 9.0.2153

|||

Hi Kts,

Do you use Row versioning in you database?

I waiting for your answer.

Regards,

|||

No !

|||

Hi kts,

What you TRANSACTION ISOLATION LEVEL do you run the code?

Can you post the query here?

Regards,

|||

hi

Like the message says READ UNCOMMITTED . its actually just a select with NO LOCK. The problem is I can only guess which proc it is but not know for sure as I am not able to recreate the problem manually.

|||

Ah, you use 'nolock' hint. There are issues with using such hint. I suggest you take a look at the following KB.

http://search.support.microsoft.com/kb/235880

|||

I'm still having the same problem..

My sql query results about 100Mb of information.

What can I do?

Error: 3314 serverity: 21, state: 4

I have this error, and it auto recovery after 1 minutes.. any idea? and it
involved more then one db.
Error while undoing logged operation in database 'hash'. Error at log record
i (20969:622890:4)..
Error : 9901,Severity: 21, state 1
the log file for database 'hash' is not available
Database hash cannot be open, it has been marked suspect for recovery, see
the sql server errorlog for more information.
starting up database 'hash'soonyu wrote:
> I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log record
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>
Is this a new installation, or one that has been running for a while?
Do you have any "bad block" events in your Windows Event Log around this
same time? My initial guess would be some sort of drive failure.|||This run for quite sometime.. more then year..
just notices this happen and twice already for this month..
first time, 2 db and auto recovery within one minutes..
second time, 1 db and auto recovery within one minutes as well..
Can't find any error.. and this is problem..
anybody have this kind of experience..
developer start mention about db problem..
soonyu.
"Tracy McKibben" wrote:
> soonyu wrote:
> > I have this error, and it auto recovery after 1 minutes.. any idea? and it
> > involved more then one db.
> >
> > Error while undoing logged operation in database 'hash'. Error at log record
> > i (20969:622890:4)..
> > Error : 9901,Severity: 21, state 1
> > the log file for database 'hash' is not available
> > Database hash cannot be open, it has been marked suspect for recovery, see
> > the sql server errorlog for more information.
> > starting up database 'hash'
> >
> Is this a new installation, or one that has been running for a while?
> Do you have any "bad block" events in your Windows Event Log around this
> same time? My initial guess would be some sort of drive failure.
>|||Perhaps you have auto-close turned on and some other process (like anti-virus) is opening the file?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log record
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>|||ok .. i will do two thing tommrow
1. check got bad block
2. check auto-close turned on?
3. antivirus scan/open this file?
but do you think auto-close will affected? auto-close you try to mentiion is
from sql enterprise manager->database->option->auto-close?
hopefully is not db corrupt.. but from can't find log and auto recovery, it
not seem db/log corrupt right? If so, the db will go to suspend mode?
--soonyu
"Tibor Karaszi" wrote:
> Perhaps you have auto-close turned on and some other process (like anti-virus) is opening the file?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
> >I have this error, and it auto recovery after 1 minutes.. any idea? and it
> > involved more then one db.
> >
> > Error while undoing logged operation in database 'hash'. Error at log record
> > i (20969:622890:4)..
> > Error : 9901,Severity: 21, state 1
> > the log file for database 'hash' is not available
> > Database hash cannot be open, it has been marked suspect for recovery, see
> > the sql server errorlog for more information.
> > starting up database 'hash'
> >
>|||soonyu wrote:
> ok .. i will do two thing tommrow
> 1. check got bad block
> 2. check auto-close turned on?
> 3. antivirus scan/open this file?
> but do you think auto-close will affected? auto-close you try to mentiion is
> from sql enterprise manager->database->option->auto-close?
>
That is the option she's referring to. Auto-close should never be
enabled on a production DB.
You also need to tell your antivirus software to exclude MDF, LDF, BAK,
and TRN files at minimum.

Error: 17059, Severity: 18, State: 0

What does this error mean? The next message was this:
Operating system error 10055: An operation on a socket could not be
performed because the system lacked sufficient buffer space or because a
queue was full...Please disregard. I found the answer here:
http://support.microsoft.com/kb/811274/en-us
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:OnNi9oxiGHA.4512@.TK2MSFTNGP04.phx.gbl...
> What does this error mean? The next message was this:
> Operating system error 10055: An operation on a socket could not be
> performed because the system lacked sufficient buffer space or because a
> queue was full...
>
>

Error: 17059, Severity: 18, State: 0

What does this error mean? The next message was this:
Operating system error 10055: An operation on a socket could not be
performed because the system lacked sufficient buffer space or because a
queue was full...Please disregard. I found the answer here:
http://support.microsoft.com/kb/811274/en-us
"Ron Hinds" < __ron__dontspamme@.wedontlikespam_garagei
q.com> wrote in message
news:OnNi9oxiGHA.4512@.TK2MSFTNGP04.phx.gbl...
> What does this error mean? The next message was this:
> Operating system error 10055: An operation on a socket could not be
> performed because the system lacked sufficient buffer space or because a
> queue was full...
>
>

Error: 14258

Hi Guru,
I just found out that one of my SQL 2005 reporting server is
experiencing this issue.
"Error 14258: Cannot perform this operation while SQLServerAgent is
starting. Try again later."
I've seen lots people fixed this issue by switching to thread mode.
However, the server has only 1 CPU and of course is running on default
configuration(thread mode).
We had a vendor used their tool (JAVA BASED) to pull data from Oracle
to SQL Server. I terminated this process a week ago when I found out
this tool would take three weeks to import 18 million records from
Oracle to SQL Server. SQL Server has been rolling back more than a week
and expecting a few more days to be completed.
Is this rolling back causing error 14258?
Thanks so much,Not likely from the rollback but more likely from the SQL Agent
service being stuck in a starting state (as opposed to a started
state). Did you check the SQL Agent error log - the SQLAgent.out file
in the default log directory for your installation?
Did you try restarting SQL Agent?
Did you check the System event log on the server where SQL Agent is
suppose to be running and check for any errors related to the service?
-Sue
On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:

>Hi Guru,
>I just found out that one of my SQL 2005 reporting server is
>experiencing this issue.
>"Error 14258: Cannot perform this operation while SQLServerAgent is
>starting. Try again later."
>I've seen lots people fixed this issue by switching to thread mode.
>However, the server has only 1 CPU and of course is running on default
>configuration(thread mode).
>We had a vendor used their tool (JAVA BASED) to pull data from Oracle
>to SQL Server. I terminated this process a week ago when I found out
>this tool would take three weeks to import 18 million records from
>Oracle to SQL Server. SQL Server has been rolling back more than a week
>and expecting a few more days to be completed.
>Is this rolling back causing error 14258?
>Thanks so much,|||Sue,
Thanks very much for your response. Below is the output from
SQLAgent.out file. I veriffied SQLAGENT is running from:
Configuration Manager - Started
Serice Applet - Started
EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
running.
GO
I stopped and restart agent many times with both NT domain and
localsystem account but nothing worked.
Other than that, I don't see any related errors on both NT and SQL
logs.
Please let me know if you have different thoughts now.
Thanks,
2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
databases...
Sue Hoegemeier wrote:[vbcol=seagreen]
> Not likely from the rollback but more likely from the SQL Agent
> service being stuck in a starting state (as opposed to a started
> state). Did you check the SQL Agent error log - the SQLAgent.out file
> in the default log directory for your installation?
> Did you try restarting SQL Agent?
> Did you check the System event log on the server where SQL Agent is
> suppose to be running and check for any errors related to the service?
> -Sue
> On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:
>|||Still not from the rollback...The error in general is almost
always related to a configuration issue. Other things you
would want to check -
Verify that lightweight pooling is not enabled again - run
sp_configure and check the run value and the config value
for lightweight pooling. The run value for this one is
important as if it's different from the config value, a
restart of SQL Server is needed on this configuration for
changes to take effect.
Also remove any mail profile associated with Agent Mail.
You most likely have some hints or clues in the SQLAgent.out
file.
The other thing I've seen cause problems is the service
account used to run SQL Agent. Have you tried creating a new
domain account to use for the service?
-Sue
On 21 Nov 2006 12:26:33 -0800, smounkhaty@.bremer.com wrote:
[vbcol=seagreen]
>Sue,
>Thanks very much for your response. Below is the output from
>SQLAgent.out file. I veriffied SQLAGENT is running from:
>Configuration Manager - Started
>Serice Applet - Started
>EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
>running.
>GO
>I stopped and restart agent many times with both NT domain and
>localsystem account but nothing worked.
>Other than that, I don't see any related errors on both NT and SQL
>logs.
>Please let me know if you have different thoughts now.
>Thanks,
>2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
>databases...
>Sue Hoegemeier wrote:

Error: 14258

Hi Guru,
I just found out that one of my SQL 2005 reporting server is
experiencing this issue.
"Error 14258: Cannot perform this operation while SQLServerAgent is
starting. Try again later."
I've seen lots people fixed this issue by switching to thread mode.
However, the server has only 1 CPU and of course is running on default
configuration(thread mode).
We had a vendor used their tool (JAVA BASED) to pull data from Oracle
to SQL Server. I terminated this process a week ago when I found out
this tool would take three weeks to import 18 million records from
Oracle to SQL Server. SQL Server has been rolling back more than a week
and expecting a few more days to be completed.
Is this rolling back causing error 14258?
Thanks so much,Not likely from the rollback but more likely from the SQL Agent
service being stuck in a starting state (as opposed to a started
state). Did you check the SQL Agent error log - the SQLAgent.out file
in the default log directory for your installation?
Did you try restarting SQL Agent?
Did you check the System event log on the server where SQL Agent is
suppose to be running and check for any errors related to the service?
-Sue
On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:
>Hi Guru,
>I just found out that one of my SQL 2005 reporting server is
>experiencing this issue.
>"Error 14258: Cannot perform this operation while SQLServerAgent is
>starting. Try again later."
>I've seen lots people fixed this issue by switching to thread mode.
>However, the server has only 1 CPU and of course is running on default
>configuration(thread mode).
>We had a vendor used their tool (JAVA BASED) to pull data from Oracle
>to SQL Server. I terminated this process a week ago when I found out
>this tool would take three weeks to import 18 million records from
>Oracle to SQL Server. SQL Server has been rolling back more than a week
>and expecting a few more days to be completed.
>Is this rolling back causing error 14258?
>Thanks so much,|||Sue,
Thanks very much for your response. Below is the output from
SQLAgent.out file. I veriffied SQLAGENT is running from:
Configuration Manager - Started
Serice Applet - Started
EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
running.
GO
I stopped and restart agent many times with both NT domain and
localsystem account but nothing worked.
Other than that, I don't see any related errors on both NT and SQL
logs.
Please let me know if you have different thoughts now.
Thanks,
2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
databases...
Sue Hoegemeier wrote:
> Not likely from the rollback but more likely from the SQL Agent
> service being stuck in a starting state (as opposed to a started
> state). Did you check the SQL Agent error log - the SQLAgent.out file
> in the default log directory for your installation?
> Did you try restarting SQL Agent?
> Did you check the System event log on the server where SQL Agent is
> suppose to be running and check for any errors related to the service?
> -Sue
> On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:
> >Hi Guru,
> >
> >I just found out that one of my SQL 2005 reporting server is
> >experiencing this issue.
> >
> >"Error 14258: Cannot perform this operation while SQLServerAgent is
> >starting. Try again later."
> >
> >I've seen lots people fixed this issue by switching to thread mode.
> >However, the server has only 1 CPU and of course is running on default
> >configuration(thread mode).
> >
> >We had a vendor used their tool (JAVA BASED) to pull data from Oracle
> >to SQL Server. I terminated this process a week ago when I found out
> >this tool would take three weeks to import 18 million records from
> >Oracle to SQL Server. SQL Server has been rolling back more than a week
> >and expecting a few more days to be completed.
> >
> >Is this rolling back causing error 14258?
> >
> >Thanks so much,|||Still not from the rollback...The error in general is almost
always related to a configuration issue. Other things you
would want to check -
Verify that lightweight pooling is not enabled again - run
sp_configure and check the run value and the config value
for lightweight pooling. The run value for this one is
important as if it's different from the config value, a
restart of SQL Server is needed on this configuration for
changes to take effect.
Also remove any mail profile associated with Agent Mail.
You most likely have some hints or clues in the SQLAgent.out
file.
The other thing I've seen cause problems is the service
account used to run SQL Agent. Have you tried creating a new
domain account to use for the service?
-Sue
On 21 Nov 2006 12:26:33 -0800, smounkhaty@.bremer.com wrote:
>Sue,
>Thanks very much for your response. Below is the output from
>SQLAgent.out file. I veriffied SQLAGENT is running from:
>Configuration Manager - Started
>Serice Applet - Started
>EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
>running.
>GO
>I stopped and restart agent many times with both NT domain and
>localsystem account but nothing worked.
>Other than that, I don't see any related errors on both NT and SQL
>logs.
>Please let me know if you have different thoughts now.
>Thanks,
>2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
>databases...
>Sue Hoegemeier wrote:
>> Not likely from the rollback but more likely from the SQL Agent
>> service being stuck in a starting state (as opposed to a started
>> state). Did you check the SQL Agent error log - the SQLAgent.out file
>> in the default log directory for your installation?
>> Did you try restarting SQL Agent?
>> Did you check the System event log on the server where SQL Agent is
>> suppose to be running and check for any errors related to the service?
>> -Sue
>> On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:
>> >Hi Guru,
>> >
>> >I just found out that one of my SQL 2005 reporting server is
>> >experiencing this issue.
>> >
>> >"Error 14258: Cannot perform this operation while SQLServerAgent is
>> >starting. Try again later."
>> >
>> >I've seen lots people fixed this issue by switching to thread mode.
>> >However, the server has only 1 CPU and of course is running on default
>> >configuration(thread mode).
>> >
>> >We had a vendor used their tool (JAVA BASED) to pull data from Oracle
>> >to SQL Server. I terminated this process a week ago when I found out
>> >this tool would take three weeks to import 18 million records from
>> >Oracle to SQL Server. SQL Server has been rolling back more than a week
>> >and expecting a few more days to be completed.
>> >
>> >Is this rolling back causing error 14258?
>> >
>> >Thanks so much,

Error: 14258

Hi Guru,
I just found out that one of my SQL 2005 reporting server is
experiencing this issue.
"Error 14258: Cannot perform this operation while SQLServerAgent is
starting. Try again later."
I've seen lots people fixed this issue by switching to thread mode.
However, the server has only 1 CPU and of course is running on default
configuration(thread mode).
We had a vendor used their tool (JAVA BASED) to pull data from Oracle
to SQL Server. I terminated this process a week ago when I found out
this tool would take three weeks to import 18 million records from
Oracle to SQL Server. SQL Server has been rolling back more than a week
and expecting a few more days to be completed.
Is this rolling back causing error 14258?
Thanks so much,
Not likely from the rollback but more likely from the SQL Agent
service being stuck in a starting state (as opposed to a started
state). Did you check the SQL Agent error log - the SQLAgent.out file
in the default log directory for your installation?
Did you try restarting SQL Agent?
Did you check the System event log on the server where SQL Agent is
suppose to be running and check for any errors related to the service?
-Sue
On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:

>Hi Guru,
>I just found out that one of my SQL 2005 reporting server is
>experiencing this issue.
>"Error 14258: Cannot perform this operation while SQLServerAgent is
>starting. Try again later."
>I've seen lots people fixed this issue by switching to thread mode.
>However, the server has only 1 CPU and of course is running on default
>configuration(thread mode).
>We had a vendor used their tool (JAVA BASED) to pull data from Oracle
>to SQL Server. I terminated this process a week ago when I found out
>this tool would take three weeks to import 18 million records from
>Oracle to SQL Server. SQL Server has been rolling back more than a week
>and expecting a few more days to be completed.
>Is this rolling back causing error 14258?
>Thanks so much,
|||Sue,
Thanks very much for your response. Below is the output from
SQLAgent.out file. I veriffied SQLAGENT is running from:
Configuration Manager - Started
Serice Applet - Started
EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
running.
GO
I stopped and restart agent many times with both NT domain and
localsystem account but nothing worked.
Other than that, I don't see any related errors on both NT and SQL
logs.
Please let me know if you have different thoughts now.
Thanks,
2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
databases...
Sue Hoegemeier wrote:[vbcol=seagreen]
> Not likely from the rollback but more likely from the SQL Agent
> service being stuck in a starting state (as opposed to a started
> state). Did you check the SQL Agent error log - the SQLAgent.out file
> in the default log directory for your installation?
> Did you try restarting SQL Agent?
> Did you check the System event log on the server where SQL Agent is
> suppose to be running and check for any errors related to the service?
> -Sue
> On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:
|||Still not from the rollback...The error in general is almost
always related to a configuration issue. Other things you
would want to check -
Verify that lightweight pooling is not enabled again - run
sp_configure and check the run value and the config value
for lightweight pooling. The run value for this one is
important as if it's different from the config value, a
restart of SQL Server is needed on this configuration for
changes to take effect.
Also remove any mail profile associated with Agent Mail.
You most likely have some hints or clues in the SQLAgent.out
file.
The other thing I've seen cause problems is the service
account used to run SQL Agent. Have you tried creating a new
domain account to use for the service?
-Sue
On 21 Nov 2006 12:26:33 -0800, smounkhaty@.bremer.com wrote:
[vbcol=seagreen]
>Sue,
>Thanks very much for your response. Below is the output from
>SQLAgent.out file. I veriffied SQLAGENT is running from:
>Configuration Manager - Started
>Serice Applet - Started
>EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
>running.
>GO
>I stopped and restart agent many times with both NT domain and
>localsystem account but nothing worked.
>Other than that, I don't see any related errors on both NT and SQL
>logs.
>Please let me know if you have different thoughts now.
>Thanks,
>2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
>databases...
>Sue Hoegemeier wrote:

Error with OPENXML

I am getting an error(XML parsing error: Not enough storage is
available to complete this operation.) while using OPENXML on server,
I think the problem is with bad version of MSXML.dll (someone said I
might be using 2.6 and NOT 3.0 Parser).
I want to know the service pack version of the SQL 2000 so that I would
then decide whether to apply SP3 or SP3a.
I would really appreciate if anyone can provide feedback on this.

Select @.@.version gives me this.
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000
00:57:48 Copyright (c) 1988-2000 Microsoft Corporation Enterprise
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

xp_msver gives me this
1ProductNameNULLMicrosoft SQL Server
2ProductVersion5242888.00.194
3Language1033English (United States)
4PlatformNULLNT INTEL X86
5CommentsNULLNT INTEL X86
6CompanyNameNULLMicrosoft Corporation
7FileDescriptionNULLSQL Server Windows NT
8FileVersionNULL2000.080.0194.00
9InternalNameNULLSQLSERVR
10LegalCopyrightNULL 1988-2000 Microsoft Corp. All rights
reserved.
11LegalTrademarksNULLMicrosoft is a registered trademark of
Microsoft Corporation. Windows(TM) is a trademark of Microsoft
Corporation
12OriginalFilenameNULLSQLSERVR.EXE
13PrivateBuildNULLNULL
14SpecialBuild65630NULL
15WindowsVersion1438515255.0 (2195)
16ProcessorCount22
17ProcessorActiveMask300000003
18ProcessorType586PROCESSOR_INTEL_PENTIUM
19PhysicalMemory20472047 (2146942976)
20Product IDNULLNULL<m.ramana@.gmail.com> wrote in message
news:1118151695.263944.198450@.o13g2000cwo.googlegr oups.com...
I am getting an error(XML parsing error: Not enough storage is
available to complete this operation.) while using OPENXML on server,
I think the problem is with bad version of MSXML.dll (someone said I
might be using 2.6 and NOT 3.0 Parser).
I want to know the service pack version of the SQL 2000 so that I would
then decide whether to apply SP3 or SP3a.
I would really appreciate if anyone can provide feedback on this.

Select @.@.version gives me this.

<snip
See here:

http://support.microsoft.com/defaul...kb;en-us;321185

Your installation has no servicepack installed; the current one is SP4.

Simon|||(m.ramana@.gmail.com) writes:
> I want to know the service pack version of the SQL 2000 so that I would
> then decide whether to apply SP3 or SP3a.

Since SP3 gives you protection aganist the slammer worm, you really
should install SP3. Or SP4 which has been for some time now.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks for the info. I will go a head and install service pack 4.0
Hope that will fix the error|||Did it work after you installed SP4

best Regards,
Chandra
http://groups.msn.com/SQLResource/
http://chanduas.blogspot.com/
------------

*** Sent via Developersdex http://www.developersdex.com ***|||I am guessing it will need a restart so waiting untill night to install
SP4 on production server. Will post my feedback