Error 18210 Backup up SQL Server 2005 Database to network drive

I have 2 different servers that run nightly backup jobs to a network drive using the UNC format. I am noticing the larger databases encountering the following errors on a regular basis

Error: 18210, Severity: 16, State: 1.

'\\fnfssql3\SQLBackups\MNSQL05\<database>.BAK'. Operating system error 64(The specified network name is no longer available.).

BACKUP failed to complete the command BACKUP DATABASE <database>. Check the backup application log for detailed messages.

There are 5 databases on this server all backed up by the same job and 3 of them wortk fine and 2 of them fail so it is not a permissions problem. Have there been any problems with backing up to a network drive in 2005?

Well, backing up to networks drives is not officially *supported*, thats why the browser only display the local drives.

The reason for that and the logical explanation why you shouldn′t do that is, because the network is less reliable than local drives. If you want to make sure the database is backuped to network, you will have to either make sure the windows where the backups are streamed to the network don′t interfer with each other or you use a local backup to a drive and copy the files later over. Thats the most reliable option beside using a NAS / SAN.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Network hic-up can do this. One can see such error without sql involved.

Try trapping the error and retry the operation. Also, try backing up locally as suggested by Jens.

|||

Backing up database to a UNC path is fully supported. You must be thinking of running the database from a network drive.

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

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspx

|||

Oj,

the reason why I put *supported* in stars is, that it is sure supported, but not reliable in terms of just having a network share associated on a UNC share. (I thought he explanation should made that clearer, sorry for the poor explanation :-) ) The reliablity descrease due to your mentioned outages on the network. Having big backup files for the transfer over the network is there not recommended undless you have a SAN or a NAS which ensures more reliablity for the transfer. I often used the UNC path backup too on customer sites but either tried to shape the task to copy the files to different time windows or used a local backup and copied the files over with a mechanism (like xcopy / robocopy) to restart in the case of a connection loss.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Error 18204 on backup of Transaction log

I have used SQL Server 2005 Database Maintenance Plans to establish full backups and hourly transaction log backups. The jobs that stem from the DB Subplans run fine and report no errors when I view the history on them, however I have noticed the following error in my SQL Server error log. I am not seeing a similar error for my database backups, only the hourly log backups. Space is not an issue. Any guidance on this one would be greatly appreciated.

18204 :
BackupDiskFile::CreateMedia: Backup device <'Path\logname'> failed to create. Operating system
error = 2(The system cannot find the file specified.).

Thanks,

Jason

Have you checked that all directories exists that are used in your maintenance plan?

Daan

|||Is the job which to take full and log backups succeeds ? if not check check if the sql startup account has modify privileges to the path mentioned in the maintenanance plan....

Thanxx
Deepak
|||

Please check if you have all the necessary permissions on the destination driver as Deepak said. Also, please check if this KB is applicable to you: http://support.microsoft.com/kb/255235

HTH

Error 18204 on backup of Transaction log

I have used SQL Server 2005 Database Maintenance Plans to establish full backups and hourly transaction log backups. The jobs that stem from the DB Subplans run fine and report no errors when I view the history on them, however I have noticed the following error in my SQL Server error log. I am not seeing a similar error for my database backups, only the hourly log backups. Space is not an issue. Any guidance on this one would be greatly appreciated.

18204 :
BackupDiskFile::CreateMedia: Backup device <'Path\logname'> failed to create. Operating system
error = 2(The system cannot find the file specified.).

Thanks,

Jason

Have you checked that all directories exists that are used in your maintenance plan?

Daan

|||Is the job which to take full and log backups succeeds ? if not check check if the sql startup account has modify privileges to the path mentioned in the maintenanance plan....

Thanxx
Deepak
|||

Please check if you have all the necessary permissions on the destination driver as Deepak said. Also, please check if this KB is applicable to you: http://support.microsoft.com/kb/255235

HTH

sql

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
--
Best wishesSee if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:

> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>
>|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...[vbcol=seagreen]
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
>|||I have just installed 818. How do I do a minidump then?
"Adrian Zajkeskovic" wrote:

> Backups should not spike your CPUs. My guess is that you have another
> problem on this server and it's hanging SQL. You should engage MS support
> and have them review 17883 minidumps. You need to be on build 818 (MS03-03
1
> patch) or higher to generate good minidumps.
> Adrian
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
>
>|||Backups should not cause this but could trigger behavior that you don't
expect.
Perhaps this will help.
The 17883 is a generic message (often referred to as the service engine
light) indicating that the UMS scheduling mechanism has detected a
worker that is not properly yielding to other workers within SQL Server.
The message was added in SQL 2000 SP3 but a later build (8.00.818
Security patch) is required to get extended diags. When the error is
first encountered a mini-dump is generated capturing the state of the
non-yielding thread. The mini-dump can be used by SQL support to
determine where in the code the SQL Server is non-yielding.
Since SP3 Microsoft has corrected or protected the engine in approx 25
places in the SQL Server code base that may not yield to other workers
properly, diminishing concurrency of the database engine. That is why
you find so many references to upgrade to a later QFE. I generally
recommend going to 8.00.997 to obtain the majority of these corrections
if you have encountered the 17883 on SP3 (8.00.760) where the mini dump
is not generated so the cause can not be determined.
Future versions of SQL Server are working to make these mini-dumps
Watson enabled so they can be directly submitted to the Watson site and
automated responses generated.
The problems have ranged from SQL Server bugs to getting stuck in API
calls that should return quickly but from time to time do not. For
example if we make a call to a security API and the PDC/BDC does not
return a response for 60 seconds (unusual and unexpected) the worker
ties up the specific UMS scheduler.
Do not be mislead, the worker is still an NT thread or fiber and must
honor NT scheduling. The design of SQL Server (UMS scheduling) is such
that only a single worker on a given scheduler can be scheduled by the
OS at any point in time. As each completes major phases or work
(natural yield points) the UMS scheduler coordinates the scheduling of
another worker on the same scheduler. It is rather simple, each worker
does a WaitForSingleObject with in INFINITE timeout so NT does not see
them as a viable worker to schedule. When a the active worker finishes
the unit of work it signals the next worker and waits on its event and
the cycle continues. Without going into more detail in this thread it
is a very simplistic non-preemptive system inside the SQL Server setup
to maximize resource usage and increase scalability. There is not need
for a lock waiter to do anything until the lock owner signals it to
execute so use the CPU for something more meaningful.
Bob Dorr
Microsoft SQL Server Escalation Support - Senior EE
*** Sent via Developersdex http://www.codecomments.com ***sql

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
--
Best wishesSee if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:
> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
> >I get this message every time i try to take a backup. Both manually and via
> > the Scheduler. What is the problem?
> > --
> > Best wishes
>
>|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
>> See if these help:
>> http://support.microsoft.com/kb/815056
>> http://support.microsoft.com/kb/810885
>>
>> --
>> -oj
>>
>> "Mats" <Mats@.discussions.microsoft.com> wrote in message
>> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>> >I get this message every time i try to take a backup. Both manually and
>> >via
>> > the Scheduler. What is the problem?
>> > --
>> > Best wishes
>>

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
Best wishes
See if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes
|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:

> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>
>
|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...[vbcol=seagreen]
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
|||I have just installed 818. How do I do a minidump then?
"Adrian Zajkeskovic" wrote:

> Backups should not spike your CPUs. My guess is that you have another
> problem on this server and it's hanging SQL. You should engage MS support
> and have them review 17883 minidumps. You need to be on build 818 (MS03-031
> patch) or higher to generate good minidumps.
> Adrian
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
>
>
|||Backups should not cause this but could trigger behavior that you don't
expect.
Perhaps this will help.
The 17883 is a generic message (often referred to as the service engine
light) indicating that the UMS scheduling mechanism has detected a
worker that is not properly yielding to other workers within SQL Server.
The message was added in SQL 2000 SP3 but a later build (8.00.818
Security patch) is required to get extended diags. When the error is
first encountered a mini-dump is generated capturing the state of the
non-yielding thread. The mini-dump can be used by SQL support to
determine where in the code the SQL Server is non-yielding.
Since SP3 Microsoft has corrected or protected the engine in approx 25
places in the SQL Server code base that may not yield to other workers
properly, diminishing concurrency of the database engine. That is why
you find so many references to upgrade to a later QFE. I generally
recommend going to 8.00.997 to obtain the majority of these corrections
if you have encountered the 17883 on SP3 (8.00.760) where the mini dump
is not generated so the cause can not be determined.
Future versions of SQL Server are working to make these mini-dumps
Watson enabled so they can be directly submitted to the Watson site and
automated responses generated.
The problems have ranged from SQL Server bugs to getting stuck in API
calls that should return quickly but from time to time do not. For
example if we make a call to a security API and the PDC/BDC does not
return a response for 60 seconds (unusual and unexpected) the worker
ties up the specific UMS scheduler.
Do not be mislead, the worker is still an NT thread or fiber and must
honor NT scheduling. The design of SQL Server (UMS scheduling) is such
that only a single worker on a given scheduler can be scheduled by the
OS at any point in time. As each completes major phases or work
(natural yield points) the UMS scheduler coordinates the scheduling of
another worker on the same scheduler. It is rather simple, each worker
does a WaitForSingleObject with in INFINITE timeout so NT does not see
them as a viable worker to schedule. When a the active worker finishes
the unit of work it signals the next worker and waits on its event and
the cycle continues. Without going into more detail in this thread it
is a very simplistic non-preemptive system inside the SQL Server setup
to maximize resource usage and increase scalability. There is not need
for a lock waiter to do anything until the lock owner signals it to
execute so use the CPU for something more meaningful.
Bob Dorr
Microsoft SQL Server Escalation Support - Senior EE
*** Sent via Developersdex http://www.codecomments.com ***

Error 17883

Hi ~
I realize that this has been posted on, but I am confused. We are
getting an error in our event logs at odd times (not at backup times or
anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
Scheduler 3, or a variant there of.. and so far, the only solution
that I can see for this problem on a Win2K server running SQL 2000 SP4
is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
option though, as this would open the server to known security flaws,
etc... correct? Are there any other options?
Hi
17883 errors have been around since SP3 (the error was introduced to show
issues that were there, but were not detectable by users).
More and more have been fixed in the various hotfixes since then. It is best
for you to open a case with Microsoft Support so that they can sort the
problem out for you.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>
|||I had this error after MS05-027 applied. Removing MS05-027 fixed the
problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
drivers were up-to-date. Engineers from MS admitted it was a rare bug
reported only by 2 customers. Since it affected only 2 customers MS didn't
want to think of a fix and asked us to seal the port 454.
<shandain@.gmail.com> wrote in message
news:1125535239.274678.73180@.o13g2000cwo.googlegro ups.com...
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>
|||I met this error on SP3a after moving to SAN. Now we are trying to install
SP4 to fix this issue. You can find my post on Sept 1. Are you running on
SAN?
Bill
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>
|||How do i remove MS05-027 as it is not showing up in the add remove programs.
(I'm not sure if i have removed it but i am still getting the 17883 errors
when trying to backup databases)
"ME" wrote:

> I had this error after MS05-027 applied. Removing MS05-027 fixed the
> problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
> drivers were up-to-date. Engineers from MS admitted it was a rare bug
> reported only by 2 customers. Since it affected only 2 customers MS didn't
> want to think of a fix and asked us to seal the port 454.
>
> <shandain@.gmail.com> wrote in message
> news:1125535239.274678.73180@.o13g2000cwo.googlegro ups.com...
>
>

Error 17883

Hi ~
I realize that this has been posted on, but I am confused. We are
getting an error in our event logs at odd times (not at backup times or
anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
Scheduler 3, or a variant there of.. and so far, the only solution
that I can see for this problem on a Win2K server running SQL 2000 SP4
is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
option though, as this would open the server to known security flaws,
etc... correct? Are there any other options?Hi
17883 errors have been around since SP3 (the error was introduced to show
issues that were there, but were not detectable by users).
More and more have been fixed in the various hotfixes since then. It is best
for you to open a case with Microsoft Support so that they can sort the
problem out for you.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I had this error after MS05-027 applied. Removing MS05-027 fixed the
problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
drivers were up-to-date. Engineers from MS admitted it was a rare bug
reported only by 2 customers. Since it affected only 2 customers MS didn't
want to think of a fix and asked us to seal the port 454.
<shandain@.gmail.com> wrote in message
news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I met this error on SP3a after moving to SAN. Now we are trying to install
SP4 to fix this issue. You can find my post on Sept 1. Are you running on
SAN?
Bill
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||How do i remove MS05-027 as it is not showing up in the add remove programs.
(I'm not sure if i have removed it but i am still getting the 17883 errors
when trying to backup databases)
"ME" wrote:

> I had this error after MS05-027 applied. Removing MS05-027 fixed the
> problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. Al
l
> drivers were up-to-date. Engineers from MS admitted it was a rare bug
> reported only by 2 customers. Since it affected only 2 customers MS didn'
t
> want to think of a fix and asked us to seal the port 454.
>
> <shandain@.gmail.com> wrote in message
> news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
>
>

error 17883

Hi, ALL
We are getting error 17883
Backup for DB "GBK" was not creating.
19:22 first error.
~ 07:00 users begin to work. Server does not response.
~ 07:13 administrator log in to console.
07:31 server restart. there are no error in error log.
Errorlog:
2006-04-06 19:20:03.24 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6750:1, last LSN:
1131478:6786:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:21:08.93 server Error: 17883, Severity: 1, State: 0
2006-04-06 19:21:08.93 server The Scheduler 2 appears to be hung. SPID
58, ECID 0, UMS Context 0x07A92978.
2006-04-06 19:22:03.13 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6786:1, last LSN:
1131478:6814:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:22:08.93 server Error: 17883, Severity: 1, State: 0
2006-04-06 19:22:08.93 server The Scheduler 2 appears to be hung. SPID
58, ECID 0, UMS Context 0x07A92978.
2006-04-06 19:24:03.21 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6814:1, last LSN:
1131478:6850:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:26:03.12 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6850:1, last LSN:
1131478:6867:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:28:03.20 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6867:1, last LSN:
1131478:6919:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:30:02.70 backup Log backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), first LSN: 46544:183:1, last LSN:
46544:183:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'GSM_log'}).
2006-04-06 19:30:04.65 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6919:1, last LSN:
1131478:6962:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:31:08.93 server Error: 17883, Severity: 1, State: 0
2006-04-06 19:31:08.93 server The Scheduler 2 appears to be hung. SPID
58, ECID 0, UMS Context 0x07A92978.
2006-04-06 19:32:03.18 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:6962:1, last LSN:
1131478:7027:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:34:03.23 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7027:1, last LSN:
1131478:7070:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:36:03.31 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7070:1, last LSN:
1131478:7096:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:37:08.94 server Error: 17883, Severity: 1, State: 0
2006-04-06 19:37:08.94 server The Scheduler 2 appears to be hung. SPID
58, ECID 0, UMS Context 0x07A92978.
2006-04-06 19:38:03.28 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7096:1, last LSN:
1131478:7127:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:40:02.13 backup Log backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), first LSN: 46544:183:1, last LSN:
46544:183:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'GSM_log'}).
2006-04-06 19:40:03.22 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7127:1, last LSN:
1131478:7175:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:42:03.19 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7175:1, last LSN:
1131478:7220:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:44:03.22 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7220:1, last LSN:
1131478:7247:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:44:08.94 server Error: 17883, Severity: 1, State: 0
2006-04-06 19:44:08.94 server The Scheduler 2 appears to be hung. SPID
58, ECID 0, UMS Context 0x07A92978.
2006-04-06 19:46:03.24 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7247:1, last LSN:
1131478:7264:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:48:03.24 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7264:1, last LSN:
1131478:7286:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:50:02.13 backup Log backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), first LSN: 46544:183:1, last LSN:
46544:183:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'GSM_log'}).
2006-04-06 19:50:03.28 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7286:1, last LSN:
1131478:7293:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:52:03.21 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7293:1, last LSN:
1131478:7305:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:54:03.18 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7305:1, last LSN:
1131478:7307:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:56:03.11 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7307:1, last LSN:
1131478:7309:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 19:58:03.10 backup Log backed up: Database: gbk, creation
date(time): 2004/07/24(12:45:40), first LSN: 1131478:7309:1, last LSN:
1131478:7319:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'gbk_log'}).
2006-04-06 22:30:02.74 spid55 Attempting to cycle errorlog.
2006-04-06 22:30:02.83 spid55 Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
2006-04-06 22:30:02.83 spid55 Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-06 22:30:02.83 spid55 All rights reserved.
2006-04-06 22:30:02.83 spid55 Server Process ID is 636.
2006-04-06 22:30:02.83 spid55 Logging SQL Server messages in file
'd:\mssql2000\MSSQL\log\ERRORLOG'.
2006-04-06 22:30:02.83 spid55 Errorlog has been reinitialized. See
previous log for older entries.
2006-04-06 22:30:05.14 spid55 DBCC CHECKDB (master) executed by
domain\user found 0 errors and repaired 0 errors.
2006-04-06 22:30:06.81 backup Database backed up: Database: master,
creation date(time): 2006/03/24(20:39:08), pages dumped: 1963, first LSN:
312:455:1, last LSN: 312:457:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK: {'master_full'}).
2006-04-06 22:30:08.88 spid54 DBCC CHECKDB (msdb) executed by domain\user
found 0 errors and repaired 0 errors.
2006-04-06 22:30:12.94 backup Database backed up: Database: msdb,
creation date(time): 2000/08/06(01:40:56), pages dumped: 4811, first LSN:
18066:979:1, last LSN: 18066:982:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK: {'msdb_full'}).
2006-04-06 22:30:13.89 spid54 DBCC CHECKDB (sqladmin) executed by
domain\user found 0 errors and repaired 0 errors.
2006-04-06 22:30:14.99 backup Database backed up: Database: sqladmin,
creation date(time): 2003/04/21(14:44:13), pages dumped: 258, first LSN:
27404:239:1, last LSN: 27404:241:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK: {'sqladmin_full'}).
2006-04-06 22:30:17.50 spid55 DBCC CHECKDB (GSM) executed by domain\user
found 0 errors and repaired 0 errors.
2006-04-06 22:30:31.42 backup Database log truncated: Database: GSM.
2006-04-06 22:30:33.74 backup Database backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), pages dumped: 3750, first LSN: 46638:361:1,
last LSN: 46638:363:1, number of dump devices: 1, device information:
(FILE=1, TYPE=DISK: {'GSM_full'}).
2006-04-06 22:44:07.73 spid56 DBCC CHECKDB (gbk) executed by domain\user
found 0 errors and repaired 0 errors.
2006-04-07 00:18:47.12 backup Database log truncated: Database: gbk.
2006-04-07 07:14:53.14 server Error: 17883, Severity: 1, State: 0
2006-04-07 07:14:53.14 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x07A86300.
2006-04-07 07:14:56.42 backup Log backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), first LSN: 46638:361:1, last LSN:
46638:368:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'GSM_log'}).
2006-04-07 07:20:03.00 backup Log backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), first LSN: 46638:368:1, last LSN:
46638:368:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'GSM_log'}).
2006-04-07 07:30:03.30 backup Log backed up: Database: GSM, creation
date(time): 2004/06/05(00:34:40), first LSN: 46638:368:1, last LSN:
46638:368:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK: {'GSM_log'}).
2006-04-07 07:31:17.07 backup BACKUP failed to complete the command PRINT
'creating full backup GBK'
backup database [gbk] to [gbk_full] with stats=100, init, skip
2006-04-07 07:31:27.73 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
...
Server restartHello
In essence all this 17883 message tells us is that no context switches were
made on the scheduler. The two things that I can think of are a) a hung
scheduler, or b) a thread that is not properly yielding to the scheduler.
I would suggest opening up a case with PSS since this need memory dump to
find clues to troubleshoot the issue.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Also, please make sure you have latest service pack installed on the
server.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: error 17883
>thread-index: AcZaGCgcfWSWeH5/QoCXiTp9pSJ7YQ==>X-WBNR-Posting-Host: 212.12.3.11
>From: =?Utf-8?B?dmFkaW1t?= <white@.community.nospam>
>Subject: error 17883
>Date: Fri, 7 Apr 2006 00:52:02 -0700
>Lines: 186
>Message-ID: <1961654E-C620-4AFA-BD4A-A731BCA877CE@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:427204
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi, ALL
>We are getting error 17883
>Backup for DB "GBK" was not creating.
> 19:22 first error.
>~ 07:00 users begin to work. Server does not response.
>~ 07:13 administrator log in to console.
> 07:31 server restart. there are no error in error log.
>Errorlog:
>2006-04-06 19:20:03.24 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6750:1, last LSN:
>1131478:6786:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:21:08.93 server Error: 17883, Severity: 1, State: 0
>2006-04-06 19:21:08.93 server The Scheduler 2 appears to be hung. SPID
>58, ECID 0, UMS Context 0x07A92978.
>2006-04-06 19:22:03.13 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6786:1, last LSN:
>1131478:6814:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:22:08.93 server Error: 17883, Severity: 1, State: 0
>2006-04-06 19:22:08.93 server The Scheduler 2 appears to be hung. SPID
>58, ECID 0, UMS Context 0x07A92978.
>2006-04-06 19:24:03.21 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6814:1, last LSN:
>1131478:6850:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:26:03.12 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6850:1, last LSN:
>1131478:6867:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:28:03.20 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6867:1, last LSN:
>1131478:6919:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:30:02.70 backup Log backed up: Database: GSM, creation
>date(time): 2004/06/05(00:34:40), first LSN: 46544:183:1, last LSN:
>46544:183:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'GSM_log'}).
>2006-04-06 19:30:04.65 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6919:1, last LSN:
>1131478:6962:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:31:08.93 server Error: 17883, Severity: 1, State: 0
>2006-04-06 19:31:08.93 server The Scheduler 2 appears to be hung. SPID
>58, ECID 0, UMS Context 0x07A92978.
>2006-04-06 19:32:03.18 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:6962:1, last LSN:
>1131478:7027:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:34:03.23 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7027:1, last LSN:
>1131478:7070:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:36:03.31 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7070:1, last LSN:
>1131478:7096:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:37:08.94 server Error: 17883, Severity: 1, State: 0
>2006-04-06 19:37:08.94 server The Scheduler 2 appears to be hung. SPID
>58, ECID 0, UMS Context 0x07A92978.
>2006-04-06 19:38:03.28 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7096:1, last LSN:
>1131478:7127:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:40:02.13 backup Log backed up: Database: GSM, creation
>date(time): 2004/06/05(00:34:40), first LSN: 46544:183:1, last LSN:
>46544:183:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'GSM_log'}).
>2006-04-06 19:40:03.22 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7127:1, last LSN:
>1131478:7175:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:42:03.19 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7175:1, last LSN:
>1131478:7220:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:44:03.22 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7220:1, last LSN:
>1131478:7247:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:44:08.94 server Error: 17883, Severity: 1, State: 0
>2006-04-06 19:44:08.94 server The Scheduler 2 appears to be hung. SPID
>58, ECID 0, UMS Context 0x07A92978.
>2006-04-06 19:46:03.24 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7247:1, last LSN:
>1131478:7264:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:48:03.24 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7264:1, last LSN:
>1131478:7286:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:50:02.13 backup Log backed up: Database: GSM, creation
>date(time): 2004/06/05(00:34:40), first LSN: 46544:183:1, last LSN:
>46544:183:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'GSM_log'}).
>2006-04-06 19:50:03.28 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7286:1, last LSN:
>1131478:7293:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:52:03.21 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7293:1, last LSN:
>1131478:7305:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:54:03.18 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7305:1, last LSN:
>1131478:7307:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:56:03.11 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7307:1, last LSN:
>1131478:7309:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 19:58:03.10 backup Log backed up: Database: gbk, creation
>date(time): 2004/07/24(12:45:40), first LSN: 1131478:7309:1, last LSN:
>1131478:7319:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'gbk_log'}).
>2006-04-06 22:30:02.74 spid55 Attempting to cycle errorlog.
>2006-04-06 22:30:02.83 spid55 Microsoft SQL Server 2000 - 8.00.760
>(Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
>2006-04-06 22:30:02.83 spid55 Copyright (C) 1988-2002 Microsoft
>Corporation.
>2006-04-06 22:30:02.83 spid55 All rights reserved.
>2006-04-06 22:30:02.83 spid55 Server Process ID is 636.
>2006-04-06 22:30:02.83 spid55 Logging SQL Server messages in file
>'d:\mssql2000\MSSQL\log\ERRORLOG'.
>2006-04-06 22:30:02.83 spid55 Errorlog has been reinitialized. See
>previous log for older entries.
>2006-04-06 22:30:05.14 spid55 DBCC CHECKDB (master) executed by
>domain\user found 0 errors and repaired 0 errors.
>2006-04-06 22:30:06.81 backup Database backed up: Database: master,
>creation date(time): 2006/03/24(20:39:08), pages dumped: 1963, first LSN:
>312:455:1, last LSN: 312:457:1, number of dump devices: 1, device
>information: (FILE=1, TYPE=DISK: {'master_full'}).
>2006-04-06 22:30:08.88 spid54 DBCC CHECKDB (msdb) executed by
domain\user
>found 0 errors and repaired 0 errors.
>2006-04-06 22:30:12.94 backup Database backed up: Database: msdb,
>creation date(time): 2000/08/06(01:40:56), pages dumped: 4811, first LSN:
>18066:979:1, last LSN: 18066:982:1, number of dump devices: 1, device
>information: (FILE=1, TYPE=DISK: {'msdb_full'}).
>2006-04-06 22:30:13.89 spid54 DBCC CHECKDB (sqladmin) executed by
>domain\user found 0 errors and repaired 0 errors.
>2006-04-06 22:30:14.99 backup Database backed up: Database: sqladmin,
>creation date(time): 2003/04/21(14:44:13), pages dumped: 258, first LSN:
>27404:239:1, last LSN: 27404:241:1, number of dump devices: 1, device
>information: (FILE=1, TYPE=DISK: {'sqladmin_full'}).
>2006-04-06 22:30:17.50 spid55 DBCC CHECKDB (GSM) executed by
domain\user
>found 0 errors and repaired 0 errors.
>2006-04-06 22:30:31.42 backup Database log truncated: Database: GSM.
>2006-04-06 22:30:33.74 backup Database backed up: Database: GSM,
creation
>date(time): 2004/06/05(00:34:40), pages dumped: 3750, first LSN:
46638:361:1,
>last LSN: 46638:363:1, number of dump devices: 1, device information:
>(FILE=1, TYPE=DISK: {'GSM_full'}).
>2006-04-06 22:44:07.73 spid56 DBCC CHECKDB (gbk) executed by
domain\user
>found 0 errors and repaired 0 errors.
>2006-04-07 00:18:47.12 backup Database log truncated: Database: gbk.
>2006-04-07 07:14:53.14 server Error: 17883, Severity: 1, State: 0
>2006-04-07 07:14:53.14 server The Scheduler 2 appears to be hung. SPID
0,
>ECID 0, UMS Context 0x07A86300.
>2006-04-07 07:14:56.42 backup Log backed up: Database: GSM, creation
>date(time): 2004/06/05(00:34:40), first LSN: 46638:361:1, last LSN:
>46638:368:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'GSM_log'}).
>2006-04-07 07:20:03.00 backup Log backed up: Database: GSM, creation
>date(time): 2004/06/05(00:34:40), first LSN: 46638:368:1, last LSN:
>46638:368:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'GSM_log'}).
>2006-04-07 07:30:03.30 backup Log backed up: Database: GSM, creation
>date(time): 2004/06/05(00:34:40), first LSN: 46638:368:1, last LSN:
>46638:368:1, number of dump devices: 1, device information: (FILE=1,
>TYPE=DISK: {'GSM_log'}).
>2006-04-07 07:31:17.07 backup BACKUP failed to complete the command
PRINT
>'creating full backup GBK'
>backup database [gbk] to [gbk_full] with stats=100, init, skip
>2006-04-07 07:31:27.73 spid3 SQL Server is terminating due to 'stop'
>request from Service Control Manager.
>...
>Server restart
>

Error 17883

Hi ~
I realize that this has been posted on, but I am confused. We are
getting an error in our event logs at odd times (not at backup times or
anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
Scheduler 3, or a variant there of.. and so far, the only solution
that I can see for this problem on a Win2K server running SQL 2000 SP4
is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
option though, as this would open the server to known security flaws,
etc... correct? Are there any other options?Hi
17883 errors have been around since SP3 (the error was introduced to show
issues that were there, but were not detectable by users).
More and more have been fixed in the various hotfixes since then. It is best
for you to open a case with Microsoft Support so that they can sort the
problem out for you.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"shandain@.gmail.com" wrote:
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I had this error after MS05-027 applied. Removing MS05-027 fixed the
problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
drivers were up-to-date. Engineers from MS admitted it was a rare bug
reported only by 2 customers. Since it affected only 2 customers MS didn't
want to think of a fix and asked us to seal the port 454. :)
<shandain@.gmail.com> wrote in message
news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I met this error on SP3a after moving to SAN. Now we are trying to install
SP4 to fix this issue. You can find my post on Sept 1. Are you running on
SAN?
Bill
"shandain@.gmail.com" wrote:
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||How do i remove MS05-027 as it is not showing up in the add remove programs.
(I'm not sure if i have removed it but i am still getting the 17883 errors
when trying to backup databases)
"ME" wrote:
> I had this error after MS05-027 applied. Removing MS05-027 fixed the
> problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
> drivers were up-to-date. Engineers from MS admitted it was a rare bug
> reported only by 2 customers. Since it affected only 2 customers MS didn't
> want to think of a fix and asked us to seal the port 454. :)
>
> <shandain@.gmail.com> wrote in message
> news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
> > Hi ~
> >
> > I realize that this has been posted on, but I am confused. We are
> > getting an error in our event logs at odd times (not at backup times or
> > anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> > 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> > Scheduler 3, or a variant there of.. and so far, the only solution
> > that I can see for this problem on a Win2K server running SQL 2000 SP4
> > is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> > option though, as this would open the server to known security flaws,
> > etc... correct? Are there any other options?
> >
>
>

Error 15007 - login 'user1' does not exist

I restored a test database from a backup of production
and my users using a user account called user could not
login again. I try to create a new user and get the above
message. Any help please.This is a multi-part message in MIME format.
--=_NextPart_000_026A_01C34FA0.C1C01AE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Check out sp_change_users_login in the BOL.
-- Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Aboki" <waco361@.hotmail.com> wrote in message =news:099201c34fc1$7b3948a0$a001280a@.phx.gbl...
I restored a test database from a backup of production and my users using a user account called user could not login again. I try to create a new user and get the above message. Any help please.
--=_NextPart_000_026A_01C34FA0.C1C01AE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Check out sp_change_users_login in the =BOL.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Aboki" wrote in =message news:099201c34fc1$7b=3948a0$a001280a@.phx.gbl...I restored a test database from a backup of production and my users =using a user account called user could not login again. I try to create a =new user and get the above message. Any help please.

---

--=_NextPart_000_026A_01C34FA0.C1C01AE0--

Error 0: Timeout Expired HYT00 when trying to backup DBs

I am getting this error when I try to back up the larger DB's on my
server. The smaller ones back up ok. Is there a parameter I can change
to increase this timeout? I have gone into ODBC, Query Analyzer, and
SQL server properties and played around with some settings, but nothing
seems to work.
Any help is appreciated!

Phil(Iam74gibson@.houston.rr.com) writes:
> I am getting this error when I try to back up the larger DB's on my
> server. The smaller ones back up ok. Is there a parameter I can change
> to increase this timeout? I have gone into ODBC, Query Analyzer, and
> SQL server properties and played around with some settings, but nothing
> seems to work.
> Any help is appreciated!

So from where do you run this backup?

The timeout is a client-side thing, and different clients have different
timeouts. Many run with 30 seconds which is the default for ODBC,
Enterprise Manager and many others. In Query Analyzer there is no
timeout by default. Neither is there any default timeout for Agent jobs.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Error

receiving error during backup.

Microsoft SQL-DMO (ODBC SQLState: 42000)

The media set for database '%' has 2 family members but only 3 are provided. All members must be provided. BACKUP DATABASE is terminating abnormally.

You might want to check your backup device definition. Remember that you can't mix a multi-file device with a single file device.