Error: fcb::close-flush: Operating system error 21(The device is not ready.) encountered

We are using sql server 2005 Enterprise Edition with service pack1

I got the following error messages in the SQL log

The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000090000 in file '....mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. fcb::close-flush: Operating system error 21(The device is not ready.) encountered.

I got these errors for about 2 hrs and after that I see these messages in the sql log

Starting up database ' ' 1 transactions rolled forward in database '' (). This is an informational message only. No user action is required. 0 transactions rolled back in database ' ' (). This is an informational message only. No user action is required. Recovery is writing a checkpoint in database ' ' ( ). This is an informational message only. No user action is required. CHECKDB for database '' finished without errors on (local time). This is an informational message only; no user action is required.

Can anyone please help me in troubleshooting this issue. Why this migh have happened.

any help would be appreciated.

Thanks

This sounds like an IO subsystem issue, i.e. SQL Server is having difficulty talking to one of your drives. Are you using direct attached storage or a SAN?|||

Thanks for the reply. We have Netapp SCSI disk storage. Could you please tell me how do I troubleshoot this so that I wont get such errors in future.

Thanks

|||Based on this and what you describe in your other post, you really ought to give Microsoft PSS a call.|||

Do read this kb before contacting PSS. You might be running on an unsupported device.

http://support.microsoft.com/kb/304261

Error: Could not find an entry for table or index with partition ID xxxxxx in database & Ser

Hello! guys

I am using sql server 2005 enterprise edition (x64) with sp1

Periodically, the sql server is crashing. Before crashing i am getting these messages in the error log

1) During undoing of a logged operation in database 'msdb', an error occurred at log record ID (). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

2) Could not find an entry for table or index with partition ID xxxxxx in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

3) Unable to drop worktable with partition ID xxxxx after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.

4) Error occurred while attempting to drop worktable with partition ID xxxxx.

5) SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.

6)The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Usually i get (2),(3),(4) (5) error message. But last time i also got (1) and (6)
Why msdb database is mentioned in error messages? Whats wrong with msdb dattabase?

Can someone tell me how to fix this issue?

I have seen this hotfix -

http://support.microsoft.com/kb/916086
( FIX: Errors may be generated in the tempdb database when you create and then drop many temporary tables in SQL Server 2005 BUG #: 518 sql )

Should i apply this hotfix? or should apply SP2? I checked SP2 bug list but i dont see anywhere about above bug. Does that mean it is not included in SP2?

Has anyone experienced such an issue? How you have resolved it?

Please any help would be apprecited.

Thanks

Database id:1 is master, :2 is tempdb. msdb database id should be 4.

It's a good thing to apply that hotfix. Also, please post the sql log. It gives us a lot more info than windows event log.

|||
Thanks so much for the reply.

All the above errors are from sql log only. I looked at the event log and it shows the same error messages.

Also that hotfix says-

This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

So is it safe to apply that hotfix? and if not does sp2 includes this hotfix bug?

Also wondering why the error message showing msdb database?

Thanks

|||

All hotfixes have that disclaimer. Basically, hotfixes are released to customers who truly need the fix before a formal release of a service pack (which they could wait for a long time for).

Sql2k5 sp2 does have this fix included. You can tell by looking at the build number (hotfix: 1533 and sp2: 3042).

The "missing log for msdb" error implies your sqlserver can't get to the log file (*.ldf) which implies a storage problem. Please check system event log for any indication of hardware failure.

sql

Error: Could not find an entry for table or index with partition ID xxxxxx in database & Ser

Hello! guys

I am using sql server 2005 enterprise edition (x64) with sp1

Periodically, the sql server is crashing. Before crashing i am getting these messages in the error log

1) During undoing of a logged operation in database 'msdb', an error occurred at log record ID (). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

2) Could not find an entry for table or index with partition ID xxxxxx in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

3) Unable to drop worktable with partition ID xxxxx after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.

4) Error occurred while attempting to drop worktable with partition ID xxxxx.

5) SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.

6)The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Usually i get (2),(3),(4) (5) error message. But last time i also got (1) and (6)
Why msdb database is mentioned in error messages? Whats wrong with msdb dattabase?

Can someone tell me how to fix this issue?

I have seen this hotfix -

http://support.microsoft.com/kb/916086
( FIX: Errors may be generated in the tempdb database when you create and then drop many temporary tables in SQL Server 2005 BUG #: 518 sql )

Should i apply this hotfix? or should apply SP2? I checked SP2 bug list but i dont see anywhere about above bug. Does that mean it is not included in SP2?

Has anyone experienced such an issue? How you have resolved it?

Please any help would be apprecited.

Thanks

Database id:1 is master, :2 is tempdb. msdb database id should be 4.

It's a good thing to apply that hotfix. Also, please post the sql log. It gives us a lot more info than windows event log.

|||
Thanks so much for the reply.

All the above errors are from sql log only. I looked at the event log and it shows the same error messages.

Also that hotfix says-

This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

So is it safe to apply that hotfix? and if not does sp2 includes this hotfix bug?

Also wondering why the error message showing msdb database?

Thanks

|||

All hotfixes have that disclaimer. Basically, hotfixes are released to customers who truly need the fix before a formal release of a service pack (which they could wait for a long time for).

Sql2k5 sp2 does have this fix included. You can tell by looking at the build number (hotfix: 1533 and sp2: 3042).

The "missing log for msdb" error implies your sqlserver can't get to the log file (*.ldf) which implies a storage problem. Please check system event log for any indication of hardware failure.

error: CoCreate of DSO for BULKIMPORTSTREAM

Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:

> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>

error: CoCreate of DSO for BULKIMPORTSTREAM

Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:

> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There reall
y
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when usin
g
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but n
ow
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>

error: CoCreate of DSO for BULKIMPORTSTREAM

Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:

> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There reall
y
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when usin
g
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but n
ow
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>sql

error: CoCreate of DSO for BULKIMPORTSTREAM

Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:

> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>

error: CoCreate of DSO for BULKIMPORTSTREAM

Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:

> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>

error: CoCreate of DSO for BULKIMPORTSTREAM

Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>

Error: 17883 - problem with Scheduler

Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
Igor
Hi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>
|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>
|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>
|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>

Error: 17883 - problem with Scheduler

Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
IgorHi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>

Error: 17883 - problem with Scheduler

Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
IgorHi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We are running SQL Server 200 SP Enterprise Edition on Windows 2003
>> with SAN components. Just recently, we got an error message in SQL Server
>> error log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be
>> non-yielding on Scheduler 0.'
>> I found a couple of articles on MS website:
>> http://support.microsoft.com/kb/319892
>> http://support.microsoft.com/kb/810885
>> http://support.microsoft.com/kb/890637
>> One of the articles refers to High-End disk system as possible source. I
>> am wondering whether anyone had similar problem and had been able to
>> detect the cause of this type of error message.
>>
>> Thanks,
>> Igor
>>
>|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> We had the issue as our SANs are very fast.
>> Once we identified the problem, we went to hotfix build 818 and then 952
>> and as soon as SP4 came out, we applied it.
>> The problems do not occur anymore.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
>> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We are running SQL Server 200 SP Enterprise Edition on Windows 2003
>> with SAN components. Just recently, we got an error message in SQL
>> Server error log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to
>> be non-yielding on Scheduler 0.'
>> I found a couple of articles on MS website:
>> http://support.microsoft.com/kb/319892
>> http://support.microsoft.com/kb/810885
>> http://support.microsoft.com/kb/890637
>> One of the articles refers to High-End disk system as possible source. I
>> am wondering whether anyone had similar problem and had been able to
>> detect the cause of this type of error message.
>>
>> Thanks,
>> Igor
>>
>>
>|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>> Did you happen to remember when exactly problem disappear? We are on
>> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
>> AWE related issues with SP4 that's why I am reluctant to install SP4.
>> Thanks,
>> Igor
>>
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> We had the issue as our SANs are very fast.
>> Once we identified the problem, we went to hotfix build 818 and then 952
>> and as soon as SP4 came out, we applied it.
>> The problems do not occur anymore.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
>> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We are running SQL Server 200 SP Enterprise Edition on Windows 2003
>> with SAN components. Just recently, we got an error message in SQL
>> Server error log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to
>> be non-yielding on Scheduler 0.'
>> I found a couple of articles on MS website:
>> http://support.microsoft.com/kb/319892
>> http://support.microsoft.com/kb/810885
>> http://support.microsoft.com/kb/890637
>> One of the articles refers to High-End disk system as possible source.
>> I am wondering whether anyone had similar problem and had been able to
>> detect the cause of this type of error message.
>>
>> Thanks,
>> Igor
>>
>>
>>
>

Error: 17883

Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
--
David Gugick
Imceda Software
www.imceda.com

Error: 17883

Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already
.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031
,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8
.Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
David Gugick
Imceda Software
www.imceda.com

Error: 17883

Dear All,
My sql server 2000 RAID 5, clustered, window 2003 enterprise server keep
encountered the below errors continueously (30+ times a day), a week already.
And the performance is seriously degraded and most of the time, can't be
connected becasuse of timeout. Do any had applied the security pack MS03-031,
and is that really can solved the problem? Any concern before I apply it to
the cluster environment? Please advise!
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context 0x0AB86BB8.
Henry wrote:
> Dear All,
> My sql server 2000 RAID 5, clustered, window 2003 enterprise server
> keep encountered the below errors continueously (30+ times a day), a
> week already. And the performance is seriously degraded and most of
> the time, can't be connected becasuse of timeout. Do any had applied
> the security pack MS03-031, and is that really can solved the
> problem? Any concern before I apply it to the cluster environment?
> Please advise!
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 122, ECID 0, UMS Context
> 0x0AB86BB8.
See if this helps:
http://support.microsoft.com/?kbid=816840
David Gugick
Imceda Software
www.imceda.com

Error with Registering a SQL Server 2000.

Anyone heard of this error when attempting to Register a
SQL Server from Enterprise Manager Standard 2000 client.
Invalid attribute/Option Identifier. If so, how have you
resolved it?
The error is usually related to an MDAC issue. Try
reapplying SP3a.
-Sue
On Wed, 24 Mar 2004 12:58:00 -0800, "Jackson_Greg"
<anonymous@.discussions.microsoft.com> wrote:

>Anyone heard of this error when attempting to Register a
>SQL Server from Enterprise Manager Standard 2000 client.
>Invalid attribute/Option Identifier. If so, how have you
>resolved it?

Error with Registering a SQL Server 2000.

Anyone heard of this error when attempting to Register a
SQL Server from Enterprise Manager Standard 2000 client.
Invalid attribute/Option Identifier. If so, how have you
resolved it?The error is usually related to an MDAC issue. Try
reapplying SP3a.
-Sue
On Wed, 24 Mar 2004 12:58:00 -0800, "Jackson_Greg"
<anonymous@.discussions.microsoft.com> wrote:

>Anyone heard of this error when attempting to Register a
>SQL Server from Enterprise Manager Standard 2000 client.
>Invalid attribute/Option Identifier. If so, how have you
>resolved it?

Error with Linked Servers

From time to time the linked servers we have set up cannot be accessed. When
I click on the tables node under the linked server within enterprise manager
the session hangs and no error message is displayed. When querying the data
via an openquery no error is thrown, the query simply runs until manually
aborted.
I've created a linked server OK but immediately cannot open it. The only way
around this problem we have is a reboot of the server. Does anyone know how
to resolve this problem and also what would cause this.
Thanks
MikeMikeD
Do you have ping to linked server?
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
> From time to time the linked servers we have set up cannot be accessed.
> When
> I click on the tables node under the linked server within enterprise
> manager
> the session hangs and no error message is displayed. When querying the
> data
> via an openquery no error is thrown, the query simply runs until manually
> aborted.
> I've created a linked server OK but immediately cannot open it. The only
> way
> around this problem we have is a reboot of the server. Does anyone know
> how
> to resolve this problem and also what would cause this.
> Thanks
> Mike|||I can ping the server that sql is on if that's what you mean. I can see and
create linked servers but cannot query them - see below.
"Uri Dimant" wrote:

> MikeD
> Do you have ping to linked server?
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
>
>|||MikeD
Do you run the query in this way?
SELECT <> FROM Server.dbname.dbo.table
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...[vbcol=seagreen]
>I can ping the server that sql is on if that's what you mean. I can see and
> create linked servers but cannot query them - see below.
> "Uri Dimant" wrote:
>|||No - it's an openquery so it's :
SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name'
But the problem isn't so much in the query it's the fact that when you
select the linked server the system hangs with no error message and the only
way we have of resolving the issue is a server reboot
"Uri Dimant" wrote:

> MikeD
> Do you run the query in this way?
> SELECT <> FROM Server.dbname.dbo.table
>
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...
>
>|||Well, is it large set data you want to return?
exec sp_serveroption 'servername','data access','true'
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...[vbcol=seagreen]
> No - it's an openquery so it's :
> SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name
'
> But the problem isn't so much in the query it's the fact that when you
> select the linked server the system hangs with no error message and the
> only
> way we have of resolving the issue is a server reboot
> "Uri Dimant" wrote:
>|||It's nothing to do with the query or the size of data. the problem is that
the linked server cannot be accessed until a reboot is done.
"Uri Dimant" wrote:

> Well, is it large set data you want to return?
> exec sp_serveroption 'servername','data access','true'
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...
>
>

Error with install of sept CTP Enterprise edition

Does SQL Server 2005 Sept CTP not support installation on XP? When I am installing, it gives me a warning that some things may not work with this OS, then when I get to the next screen I can't install anything.

Have you checked the pre-requisites such as .NET framework and IE version etc.
BTW what is the edition of XP & edition of CTP used?|||I am trying to install the september ctp enterprise edition on a machine with xp/sp2. I have reviewed the prereqs and I meet all of them. It says XP with sp2 and 512 ram; both are satisfied. I don't see any prereqs for .NET and I think that is because it installs .NET 2.0 when it installs. Any other ideas?|||Here is the warning I get when starting the install of the september CTP Enterprise version on a machine with XP/SP2 installed. If i continue to the components available for install, then the only thing enabled is 'Workstation components, ...'. All the actual database stuff is disable for install.

- SQL Server Edition Operating System Compatibility (Warning)

Messages

SQL Server Edition Operating System Compatibility

Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.

|||Enterprise Edition needs a server OS. You can install Express, Workgroup, Std and Developer Editions on XP, ie Desktop OS's|||I figured that was the problem. However, the download site does list XP/SP2 as a compatible OS for the enterprise edition. The bullet below was copied directly from the download page.

Supported Operating Systems: Microsoft Windows 2000 Service Pack 4; Windows Server 2003 Service Pack 1; Windows XP Service Pack 2

Error with a fieldname that does not exist anymore.

I get an :
[Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
'oldfieldname_eid'
While inserting in the Enterprise Manager. The 'oldfieldname_eid' does not
exist in any table of the target database. The error only occurs if an
insert trigger is defined. The insert trigger does not contain a string
resembling the 'oldfieldname_eid'. The name has been used in the past for a
field.
The error does reproduce, after a reset of the client, after setting the
database offline and online again.
The error does disappear when the trigger is 'removed' but reappears
again when the trigger is recreated. The error does not appear when
a 'dummy' trigger is used, only containing "print 'hello'"
Does anybody have a suggestion ?
ben brugmanIt would have been quite helpful if you had posted the text of the trigger,
because that seems to be where the problem is, now we have to make a guess.
One thing I can think of is if you have a view on the table that contained
the 'oldfieldname_eid' column, and that view contains SELECT *. The
definition of a view is not updated automatically when the underlying table
changes, so the column might still exist in the view definition.
Try SELECT table_name FROM information_schema.columns
WHERE column_name = 'oldfieldname_eid'
to find a view or table that includes a column with that name.
--
Jacco Schalkwijk
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:O$T6PNioDHA.2512@.TK2MSFTNGP09.phx.gbl...
> I get an :
> [Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
> 'oldfieldname_eid'
> While inserting in the Enterprise Manager. The 'oldfieldname_eid' does not
> exist in any table of the target database. The error only occurs if an
> insert trigger is defined. The insert trigger does not contain a string
> resembling the 'oldfieldname_eid'. The name has been used in the past for
a
> field.
> The error does reproduce, after a reset of the client, after setting the
> database offline and online again.
> The error does disappear when the trigger is 'removed' but reappears
> again when the trigger is recreated. The error does not appear when
> a 'dummy' trigger is used, only containing "print 'hello'"
> Does anybody have a suggestion ?
> ben brugman
>
>|||> Try SELECT table_name FROM information_schema.columns
> WHERE column_name = 'oldfieldname_eid'
The field 'oldfieldname_eid' does not appear in any View/table or trigger.
It does not appear anywhere anymore in the complete database.
There does not exist a field 'oldfieldname_eid'.
If we change the fieldname into 'AAAAAA' we get the following error
that the field 'newfieldname_eid' does not exist
> > [Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
> > 'newfieldname_eid'
> It would have been quite helpful if you had posted the text of the
trigger,
> because that seems to be where the problem is, now we have to make a
guess.
For the trigger see the end of the message.
Adding a new column to the table with 'newfieldname_eid' next to 'AAAAAA'
and
then deleting the 'AAAAAA' field did solve the problem. We expect that the
count
of columns did have a mismatch in the internal meta data and that this was
solved
by adding and deletion of columns. (But this is a guess).
(The table appears to be exactly as when the error occured but the error is
'gone').
(probably a bug).
We still would like to know what happened !
ben brugman
The trigger.
The trigger :
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE TRIGGER [TR_I_Tabel2] ON dbo.Tabel1
FOR INSERT
NOT FOR REPLICATION
AS
INSERT INTO
Tabel2 (Field1, Field2, Field3, Field4, Field5, Field6)
SELECT
Field1, Field2, Field3, current_Field4, current_Field5, current_Field6
FROM inserted
UPDATE
Tabel1
SET
Field7 =NULL
FROM
Tabel1
INNER JOIN
inserted
ON
Tabel1.Field3 = inserted.Field3
INNER JOIN
Table3
ON
Table3.Field4 = inserted.current_Field4
WHERE
Table3.status_nbr >= 50
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
> Jacco Schalkwijk
> SQL Server MVP
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:O$T6PNioDHA.2512@.TK2MSFTNGP09.phx.gbl...
> > I get an :
> >
> > [Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
> > 'oldfieldname_eid'
> >
> > While inserting in the Enterprise Manager. The 'oldfieldname_eid' does
not
> > exist in any table of the target database. The error only occurs if an
> > insert trigger is defined. The insert trigger does not contain a string
> > resembling the 'oldfieldname_eid'. The name has been used in the past
for
> a
> > field.
> > The error does reproduce, after a reset of the client, after setting the
> > database offline and online again.
> >
> > The error does disappear when the trigger is 'removed' but reappears
> > again when the trigger is recreated. The error does not appear when
> > a 'dummy' trigger is used, only containing "print 'hello'"
> >
> > Does anybody have a suggestion ?
> >
> > ben brugman
> >
> >
> >
>