Error: Column Name "X" appears more than once in the result column list.

Hello,

I am trying to follow along with the Data Access tutorial under the the "Learn->Videos" section of this website, however I am running into an error when I try to use the "Edit -> Update" function of the Details View form:

I'll post the error below. Any clues on how to fix this? Thanks in advance!!!

~Derrick

Column name 'Assigned_To' appears more than once in the result column list.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: Column name 'Assigned_To' appears more than once in the result column list.

Source Error:

Line 1444: }Line 1445: try {Line 1446: int returnValue = this.Adapter.UpdateCommand.ExecuteNonQuery();Line 1447: return returnValue;Line 1448: }

What does your UPDATE command look like?|||

Thanks for the reply. When I go to my Details.aspx page (the page giving me the error), I click on the Details View Control -> Configure Data Source, Click the Update Tab, and here is the Method Signature:

Update(String Assigned_To, String Request_type, String First_Name, String Last_Name, String Username, Nullable Created_On, String Request_Summary, String Expr1, Int16 Original_Request_Id), returns Int32

Does this help?

|||

I was able to resolve this issue. It had to do with the "String Expr1" part of the Update function. I removed any reference to Expr1 from all my data sets, refreshed the schemes in the web forms, and everything worked as it should.

Thanks for anyone who looked into it!

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
Jeff
Some anti-virus software perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegro ups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>
|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.
|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g2000hsg.go oglegroups.com...
>
>
It might be possible but why always the same database each time?
|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegro ups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>
|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:[vbcol=seagreen]
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegro ups.com...
>
>
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?
|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to exclude them... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegr oups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>
sql

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
JeffSome anti-virus software perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegroup
s.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g20
00hsg.googlegroups.com...
>
>
>
>
It might be possible but why always the same database each time?|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:[vbcol=seagreen]
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
>
>
>
>
>
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to ex
clude them... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegroups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
JeffSome anti-virus software perhaps?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> > Every couple of weeks it appears that my MSDB database is getting
> > corrupt. Here is my situation.
> > Everyday at 4 am I take a backup off all the instances, then at 5 am
> > the computer reboots. Once the computer is up all the instances try to
> > start up except MSDB will have a problem. When I log into Enterprise
> > Manager the instance is listed as Suspect. I have to restore the
> > database from the backup taken at 4 am and everything is fine.
> > Here is the error from the log file the last time it happened.
> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> > But I have also received this error:
> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> > process cannot access the file because it is being used by another
> > process.) during the creation/opening of physical device C:\Program
> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> > for virtual device number (VDN) 1.
> > I have no idea what this other process would be.
> > Any ideas?
> > Thanks,
> > Jeff
It might be possible but why always the same database each time?|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
--
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> > Every couple of weeks it appears that my MSDB database is getting
> > corrupt. Here is my situation.
> > Everyday at 4 am I take a backup off all the instances, then at 5 am
> > the computer reboots. Once the computer is up all the instances try to
> > start up except MSDB will have a problem. When I log into Enterprise
> > Manager the instance is listed as Suspect. I have to restore the
> > database from the backup taken at 4 am and everything is fine.
> > Here is the error from the log file the last time it happened.
> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> > But I have also received this error:
> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> > process cannot access the file because it is being used by another
> > process.) during the creation/opening of physical device C:\Program
> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> > for virtual device number (VDN) 1.
> > I have no idea what this other process would be.
> > Any ideas?
> > Thanks,
> > Jeff
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to exclude them... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegroups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
>> Try excluding msdb from the backup and see if you get the same error
>> post-reboot. Also if you skip the reboot, does sql continue indefinitely
>> without a problem?
>> Someone mentioned antivirus. Not sure that would cause your particular
>> issue, but you do have the AV set to exclude .mdf and .ldf file types,
>> right?
>> --
>> TheSQLGuru
>> President
>> Indicium Resources, Inc.
>> <jeffchi...@.gmail.com> wrote in message
>> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
>> > Every couple of weeks it appears that my MSDB database is getting
>> > corrupt. Here is my situation.
>> > Everyday at 4 am I take a backup off all the instances, then at 5 am
>> > the computer reboots. Once the computer is up all the instances try to
>> > start up except MSDB will have a problem. When I log into Enterprise
>> > Manager the instance is listed as Suspect. I have to restore the
>> > database from the backup taken at 4 am and everything is fine.
>> > Here is the error from the log file the last time it happened.
>> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
>> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
>> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
>> > But I have also received this error:
>> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
>> > process cannot access the file because it is being used by another
>> > process.) during the creation/opening of physical device C:\Program
>> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
>> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
>> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
>> > for virtual device number (VDN) 1.
>> > I have no idea what this other process would be.
>> > Any ideas?
>> > Thanks,
>> > Jeff
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>

Error: 17883, The Scheduler 0 appears to be hung...

I've Googled myself silly on this and I'm not sure what I should do to fix
it. Will SP4 do it? These errors happen every day at 8:00 PM yet there are
no SQL Server Agent jobs running during that time. Any ideas?
2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
.
.
2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D0E28.
2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first LSN:
789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'F:\SQL_BAK\iGreentree\iGreentree_db_200605220130.BAK'}).
2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
LSN: 789966:19764:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605221200.TRN'}).
2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
59, ECID 0, UMS Context 0x039D27E8.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C5A68.
2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first LSN:
790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'F:\SQL_BAK\iGreentree\iGreentree_db_200605230130.BAK'}).
2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
LSN: 790091:2027:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605231200.TRN'}).
2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D7AA8.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D6F60.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039DCD98.Scagnetti,
Try refresh on the jobs collection also take a look at your Database
Maintenance Plans. Is this a target server for a master server?
HTH
Jerry
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605221200.TRN'}).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605231200.TRN'}).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>|||The scheduler referenced in the error message isn't SQL Agent - it's the
internal task scheduler UMS - User Mode Scheduler. This basically means
that a thread became stuck. Here are a few possible causes:
http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&spid=global&query=17883&adv=&mode=r&cat=False
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605221200.TRN'}).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> {'F:\SQL_BAK\iGreentree\iGreentree_db_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: {'F:\SQL_BAK\iGreentree\iGreentree_tlog_200605231200.TRN'}).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>

Error: 17883, The Scheduler 0 appears to be hung...

I've Googled myself silly on this and I'm not sure what I should do to fix
it. Will SP4 do it? These errors happen every day at 8:00 PM yet there are
no SQL Server Agent jobs running during that time. Any ideas?
2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
.
.
2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D0E28.
2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first LSN:
789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
LSN: 789966:19764:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}).
2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C3D10.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
59, ECID 0, UMS Context 0x039D27E8.
2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039C5A68.
2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex) executed
by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first LSN:
790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
LSN: 790091:2027:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}).
2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D3548.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D7AA8.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039D6F60.
2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x039DCD98.Scagnetti,
Try refresh on the jobs collection also take a look at your Database
Maintenance Plans. Is this a target server for a master server?
HTH
Jerry
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}
).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}
).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>|||The scheduler referenced in the error message isn't SQL Agent - it's the
internal task scheduler UMS - User Mode Scheduler. This basically means
that a thread became stuck. Here are a few possible causes:
http://support.microsoft.com/search...ode=r&cat=False
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Scagnetti" <Scagnetti@.discussions.microsoft.com> wrote in message
news:6635ACAF-0BD1-48BE-BFD4-4D459F34786E@.microsoft.com...
> I've Googled myself silly on this and I'm not sure what I should do to fix
> it. Will SP4 do it? These errors happen every day at 8:00 PM yet there
> are
> no SQL Server Agent jobs running during that time. Any ideas?
> 2006-05-21 12:25:36.71 server Microsoft SQL Server 2000 - 8.00.760 (Intel
> X86)
> .
> .
> 2006-05-21 20:20:09.00 server Error: 17883, Severity: 1, State: 0
> 2006-05-21 20:20:09.00 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D0E28.
> 2006-05-22 01:10:07.29 spid63 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-22 01:36:50.81 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 667205, first
> LSN:
> 789963:13179:1, last LSN: 789963:19503:1, number of dump devices: 1,
> device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605220130.BAK'}).
> 2006-05-22 12:02:03.96 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789814:10524:1, last
> LSN: 789966:19764:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605221200.TRN'}
).
> 2006-05-22 20:11:08.85 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:11:08.85 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C3D10.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 1 appears to be hung. SPID
> 59, ECID 0, UMS Context 0x039D27E8.
> 2006-05-22 20:12:08.86 server Error: 17883, Severity: 1, State: 0
> 2006-05-22 20:12:08.86 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039C5A68.
> 2006-05-23 01:10:06.00 spid52 DBCC CHECKDB (iGreentree, noindex)
> executed
> by CORP\svc-hr-sql found 0 errors and repaired 0 errors.
> 2006-05-23 01:37:12.34 backup Database backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), pages dumped: 668013, first
> LSN:
> 790081:6357:1, last LSN: 790081:12597:1, number of dump devices: 1, device
> information: (FILE=1, TYPE=DISK:
> & #123;'F:\SQL_BAK\iGreentree\iGreentree_d
b_200605230130.BAK'}).
> 2006-05-23 12:01:04.71 backup Log backed up: Database: iGreentree,
> creation date(time): 2003/07/28(16:29:20), first LSN: 789966:19764:1, last
> LSN: 790091:2027:1, number of dump devices: 1, device information:
> (FILE=1,
> TYPE=DISK: & #123;'F:\SQL_BAK\iGreentree\iGreentree_t
log_200605231200.TRN'}
).
> 2006-05-23 20:22:08.77 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:22:08.77 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 0 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D3548.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 1 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D7AA8.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 2 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039D6F60.
> 2006-05-23 20:23:08.82 server Error: 17883, Severity: 1, State: 0
> 2006-05-23 20:23:08.82 server The Scheduler 3 appears to be hung. SPID
> 0,
> ECID 0, UMS Context 0x039DCD98.
>

Error: 17883, Severity: 1, State: 0

Hi ,
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
PrabhuTry to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL server
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effect
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:
> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu

Error: 17883, Severity: 1, State: 0

Hi ,
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
PrabhuTry to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL serve
r
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effec
t
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:

> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu

Error: 17883, Severity: 1, State: 0

Hi ,
We are getting 17833 error with below message .
Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
Scheduler 3.
We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
but I still see this in SQL log at least once a week .
Can you pl. suggest the solution .
Thanks,
Prabhu
Try to open a case with MS, when we did, they asked us to forward the
minidump file that gets created when that error is recorded in the SQL server
logs. Once MS took a look at the dump file, they determined that the errors
indicate possible underlying hardware issues on writes and reads, that effect
performance and hangs the scheduler. They recommended a thorough test of the
EMC hardware portion. So open a case and send them the minidump files you
should have on your harddrive and they can try to detect what may ba causing
SQL Server to throw error 17883. My understanding is that error 17883 can be
caused by many reasons, could be SQL server related and could be other
resource related.
"Prabhu" wrote:

> Hi ,
> We are getting 17833 error with below message .
> Process 54:0 (ac4) UMS Context 0x09F5C830 appears to be non-yielding on
> Scheduler 3.
> We have SQL 2000 SP4 , per MS documentation this bug has been fixed in SP4
> but I still see this in SQL log at least once a week .
> Can you pl. suggest the solution .
> Thanks,
> Prabhu
sql

Error: 17883 - The scheduler 0 appears to be hung...

Environment:
Clustered SQL Server 2K sp3a (single instance)
Product version: 8.00.760
Problem:
I end up in error 17883.
I am aware that the solution is to apply this patch:
821277 MS03-031:Security Patch for SQL Server 2000 Service
Pack 3.
I am also aware that after you install this cumulative
patch you will end up in this problem:
826161 FIX: You are prompted for password after you change
a standard SQL Server login.
After reading this one I found that there are 2
possibility to solve this problem, one if you have already
installed the security patch from MS03-031 and another one
if you do NOT have installed this patch.
Question:
Do I only need to apply this last one (is it also
cumulative?) or do I need to first apply MS03-031 and then
later the FIX 826161?
Please advise.
Kind regards.
You will need to follow the instructions in the section "If you have not
installed the security patch for Microsoft Security Bulletin
MS03-031,Q826161..." . This will include the
fix for the Enterprise Manager issue.
Additionally, this will not fix the cause of the 17883. This will only
provide additional diagnostic information for Microsoft Support should a
17883 occur which was not available in previous builds. If you believe you
are seeing performance issues at the time the 17883's are being recorded, I
urge you to open a case with Microsoft Support for assistance.
Regards,
Farooq Mahmud [MS SQL Support]
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
|||Thank you so much for your answer.
I still don't understand why, when you read MS KB article
810885,under resolution, you find the reference for MS03-
031 Cumulative Security Patch for SQL Server.
What does this cumulative patch solve?
I was sure that it will solve many problems, most of them
security related, but also the 17883 problem.
If this cumulative patch does not solve the 17883 problem
so I don't need to install any patch, right?
Am I wrong?
Please advise.

Error: [DBNETLIB]ConnectionCheckForData

I have gotten an error, which appears to be a query optimizer bug:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I admit that the query is a bit complex -- it joins three tables and uses a
view -- but it is perfect okay. If I make minor, irrelevant, changes to the
syntax it works. For example, the failing query contains WHERE TBL_D.sold_to
= 60414; if I change this to WHERE TBL_D.sold_to BETWEEN 60414 and 60414 then
the query works. It returns in a few seconds with 5 rows. Also, if I change
the query to say INNER LOOP JOIN instead of INNER JOIN then it will work
correctly.
Running dbcc checktable on the tables shows no error.
The query is generated by a Report Generator, so I cannot just make manual
changes to it; the only thing I can do is to find out the underlying cause. I
am running SQL Server 2000 version 8.00.760 (Intel X86) (Build 2195: Service
Pack 4).
Has anyone seen this kind of error, or aware of any patch that will fix it?Tycus,
This sounds like a problem in your networking hardware or configuration
somewhere. Look at your network interface settings - especially duplex
settings. Sometimes setting the NICs to Auto duples causes these errors
(sometimes they don't).
Is there anything further in the SQL Server error log? Stack dumps? Once
you've checked your networking components, and you still get the error, raise
a call with Microsoft Product Support.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Tycus" wrote:
> I have gotten an error, which appears to be a query optimizer bug:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I admit that the query is a bit complex -- it joins three tables and uses a
> view -- but it is perfect okay. If I make minor, irrelevant, changes to the
> syntax it works. For example, the failing query contains WHERE TBL_D.sold_to
> = 60414; if I change this to WHERE TBL_D.sold_to BETWEEN 60414 and 60414 then
> the query works. It returns in a few seconds with 5 rows. Also, if I change
> the query to say INNER LOOP JOIN instead of INNER JOIN then it will work
> correctly.
> Running dbcc checktable on the tables shows no error.
> The query is generated by a Report Generator, so I cannot just make manual
> changes to it; the only thing I can do is to find out the underlying cause. I
> am running SQL Server 2000 version 8.00.760 (Intel X86) (Build 2195: Service
> Pack 4).
> Has anyone seen this kind of error, or aware of any patch that will fix it?

Error: [DBNETLIB]ConnectionCheckForData

I have gotten an error, which appears to be a query optimizer bug:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForD
ata
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I admit that the query is a bit complex -- it joins three tables and uses a
view -- but it is perfect okay. If I make minor, irrelevant, changes to the
syntax it works. For example, the failing query contains WHERE TBL_D.sold_to
= 60414; if I change this to WHERE TBL_D.sold_to BETWEEN 60414 and 60414 the
n
the query works. It returns in a few seconds with 5 rows. Also, if I change
the query to say INNER LOOP JOIN instead of INNER JOIN then it will work
correctly.
Running dbcc checktable on the tables shows no error.
The query is generated by a Report Generator, so I cannot just make manual
changes to it; the only thing I can do is to find out the underlying cause.
I
am running SQL Server 2000 version 8.00.760 (Intel X86) (Build 2195: Servic
e
Pack 4).
Has anyone seen this kind of error, or aware of any patch that will fix it?Tycus,
This sounds like a problem in your networking hardware or configuration
somewhere. Look at your network interface settings - especially duplex
settings. Sometimes setting the NICs to Auto duples causes these errors
(sometimes they don't).
Is there anything further in the SQL Server error log? Stack dumps? Once
you've checked your networking components, and you still get the error, rais
e
a call with Microsoft Product Support.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Tycus" wrote:
[vbcol=seagreen]
> I have gotten an error, which appears to be a query optimizer bug:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckFo
rData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I admit that the query is a bit complex -- it joins three tables and uses
a
> view -- but it is perfect okay. If I make minor, irrelevant, changes to th
e
> syntax it works. For example, the failing query contains WHERE TBL_D.sold_
to
> = 60414; if I change this to WHERE TBL_D.sold_to BETWEEN 60414 and 60414 t
hen
> the query works. It returns in a few seconds with 5 rows. Also, if I chang
e
> the query to say INNER LOOP JOIN instead of INNER JOIN then it will work
> correctly.
> Running dbcc checktable on the tables shows no error.
> The query is generated by a Report Generator, so I cannot just make manual
> changes to it; the only thing I can do is to find out the underlying cause
. I
> am running SQL Server 2000 version 8.00.760 (Intel X86) (Build 2195: Serv
ice
> Pack 4).
> Has anyone seen this kind of error, or aware of any patch that will fix it?[/vbcol
]

Error: [DBNETLIB]ConnectionCheckForData

I have gotten an error, which appears to be a query optimizer bug:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I admit that the query is a bit complex -- it joins three tables and uses a
view -- but it is perfect okay. If I make minor, irrelevant, changes to the
syntax it works. For example, the failing query contains WHERE TBL_D.sold_to
= 60414; if I change this to WHERE TBL_D.sold_to BETWEEN 60414 and 60414 then
the query works. It returns in a few seconds with 5 rows. Also, if I change
the query to say INNER LOOP JOIN instead of INNER JOIN then it will work
correctly.
Running dbcc checktable on the tables shows no error.
The query is generated by a Report Generator, so I cannot just make manual
changes to it; the only thing I can do is to find out the underlying cause. I
am running SQL Server 2000 version 8.00.760 (Intel X86) (Build 2195: Service
Pack 4).
Has anyone seen this kind of error, or aware of any patch that will fix it?
Tycus,
This sounds like a problem in your networking hardware or configuration
somewhere. Look at your network interface settings - especially duplex
settings. Sometimes setting the NICs to Auto duples causes these errors
(sometimes they don't).
Is there anything further in the SQL Server error log? Stack dumps? Once
you've checked your networking components, and you still get the error, raise
a call with Microsoft Product Support.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Tycus" wrote:

> I have gotten an error, which appears to be a query optimizer bug:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I admit that the query is a bit complex -- it joins three tables and uses a
> view -- but it is perfect okay. If I make minor, irrelevant, changes to the
> syntax it works. For example, the failing query contains WHERE TBL_D.sold_to
> = 60414; if I change this to WHERE TBL_D.sold_to BETWEEN 60414 and 60414 then
> the query works. It returns in a few seconds with 5 rows. Also, if I change
> the query to say INNER LOOP JOIN instead of INNER JOIN then it will work
> correctly.
> Running dbcc checktable on the tables shows no error.
> The query is generated by a Report Generator, so I cannot just make manual
> changes to it; the only thing I can do is to find out the underlying cause. I
> am running SQL Server 2000 version 8.00.760 (Intel X86) (Build 2195: Service
> Pack 4).
> Has anyone seen this kind of error, or aware of any patch that will fix it?