Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005

Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?

05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181

Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?

Thanks,
Samuel Lester (MSFT)

|||

From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.

05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied

Please reboot and try again. May be SNAC reboot has halted the installation until reboot.

|||

did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error

'failed because a higher version already exists on the machine'

Is it safe to uninstall backward compatability and reinstall it?

Thanks,

Kerry

|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.

Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005

Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?

05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181

Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?

Thanks,
Samuel Lester (MSFT)

|||

From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.

05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied

Please reboot and try again. May be SNAC reboot has halted the installation until reboot.

|||

did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error

'failed because a higher version already exists on the machine'

Is it safe to uninstall backward compatability and reinstall it?

Thanks,

Kerry

|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.

Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005

Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?

05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181

Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?

Thanks,
Samuel Lester (MSFT)

|||

From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.

05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied

Please reboot and try again. May be SNAC reboot has halted the installation until reboot.

|||

did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error

'failed because a higher version already exists on the machine'

Is it safe to uninstall backward compatability and reinstall it?

Thanks,

Kerry

|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.

Backups Failed

Dear All,
We recently changed our user for the SQL Agent. On Sunday
nights we backup all our databases and perform checks,
this Sunday they did not work. The error is as follows: -
'
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'INVESTMENTS1' as 'NT AUTHORITY\SYSTEM'
(trusted)
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 229:
[Microsoft][ODBC SQL Server Driver][SQL Server]SELECT
permission denied on object 'sysdbmaintplans',
database 'msdb', owner 'dbo'.'
The odd thing however is we have other jobs that run on a
day by day basis that still work, can anyone help?
Thanks
PeterHi,
Check whether local administrators group on the machine still a member of
the
sysadmin server role? Else add it and verify the job.
Incase if you still have issues then,
Can you please add that user (User inwhich u start SQL Agent) to
buildin\administrators group and verify the execution.
or else give select permission on 'sysdbmaintplans' table to the user in
which you have started SQL Agent.
Thanks
Hari
MCDBA
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:a44e01c40a74$e3ee35e0$a601280a@.phx.gbl...
> Dear All,
> We recently changed our user for the SQL Agent. On Sunday
> nights we backup all our databases and perform checks,
> this Sunday they did not work. The error is as follows: -
> '
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'INVESTMENTS1' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 229:
> [Microsoft][ODBC SQL Server Driver][SQL Server]SELECT
> permission denied on object 'sysdbmaintplans',
> database 'msdb', owner 'dbo'.'
> The odd thing however is we have other jobs that run on a
> day by day basis that still work, can anyone help?
> Thanks
> Peter|||Thanks Hari,
Someone took out the Sysadmin access to the BUILTIN\Admin
right.
Peter

>--Original Message--
>Hi,
>Check whether local administrators group on the machine
still a member of
>the
>sysadmin server role? Else add it and verify the job.
>Incase if you still have issues then,
>Can you please add that user (User inwhich u start SQL
Agent) to
>buildin\administrators group and verify the execution.
>or else give select permission on 'sysdbmaintplans' table
to the user in
>which you have started SQL Agent.
>
>
>Thanks
>Hari
>MCDBA
>
>
>"Peter" <anonymous@.discussions.microsoft.com> wrote in
message
>news:a44e01c40a74$e3ee35e0$a601280a@.phx.gbl...
Sunday
follows: -
a
>
>.
>

BackupDiskFile::CreateMedia: Backup device failed to create.

Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/micro...error+%3D+1130(Not+enough+server+storage+is+a
vailable+to+process+this+command.).&rnum=1&hl=en#d 438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel Chan
Hello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
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: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==
>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.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.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/micro...browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACrea te
Media%3A+Backup+device+failed+to+create.+Operating +system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+thi s+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>

BackupDiskFile::CreateMedia: Backup device failed to create.

Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreateMedia%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
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: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.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.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>

BackupDiskFile::CreateMedia: Backup device failed to create.

Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/micr...+error+%3D+1130(Not+enough+serv
er+storage+is+a
vailable+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
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: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==
>X-WBNR-Posting-Host: 206.253.218.194
>From: examnotes <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.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.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/micr.../browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+p
rocess+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>

BackupDiskFile::CreateMedia: Backup device failed to create

Hi,
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
=== BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
BingNever mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===> BACKUP failed to complete the command Backup database SharePoint_WebSpace To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
> system error=32 (The process cannot access the file because it is being used
> by another process.)
> ===> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file? I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the IIS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing

BackupDiskFile::CreateMedia: Backup device failed to create

Hi,
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
===
BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
Bing
Never mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:

> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===
> BACKUP failed to complete the command Backup database SharePoint_WebSpace To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
> system error=32 (The process cannot access the file because it is being used
> by another process.)
> ===
> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file? I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the IIS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing

BackupDiskFile::CreateMedia: Backup device failed to create

Hi,
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
===
BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspac
e.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace
.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
BingNever mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:

> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===
> BACKUP failed to complete the command Backup database SharePoint_WebSpace
To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspac
e.BAK' failed to create. Operatin
g
> system error=32 (The process cannot access the file because it is being us
ed
> by another process.)
> ===
> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace
.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file?
I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the I
IS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing

Backup Wizard 2005 Standard

I have a new installation of SQL 2005 standard and I cannot create an
automatic backup. When I launch the wizard I get an error " Failed to
retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid column
name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I ca
n
then create my backup job, but upon completion I get these 2 error:
Invalid column name 'from_msx'.
Invalid column name 'has_target'.
I have to manually launch the backups each night and that work fine. I
previously was using Sql 2000 and the backup jobs ran without any problems.On Apr 19, 1:40 pm, Todd <T...@.discussions.microsoft.com> wrote:[vbcol=seagreen]
> I have a new installation of SQL 2005 standard and I cannot create an
> automatic backup. When I launch the wizard I get an error " Failed to
> retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid colu
mn
> name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I
can
> then create my backup job, but upon completion I get these 2 error:
> Invalid column name 'from_msx'.
> Invalid column name 'has_target'.
> I have to manually launch the backups each night and that work fine. I
> previously was using Sql 2000 and the backup jobs ran without any problems.[/vbcol
]
Is this a server you upgraded to 2005 was a target server and prior to
upgrade did the server have master server?|||No this is a new Server not an upgrade. I moved the 2000 db over to this
server.
"Bulent" wrote:

> On Apr 19, 1:40 pm, Todd <T...@.discussions.microsoft.com> wrote:
> Is this a server you upgraded to 2005 was a target server and prior to
> upgrade did the server have master server?
>

Backup Wizard 2005 Standard

I have a new installation of SQL 2005 standard and I cannot create an
automatic backup. When I launch the wizard I get an error " Failed to
retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid column
name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I can
then create my backup job, but upon completion I get these 2 error:
Invalid column name 'from_msx'.
Invalid column name 'has_target'.
I have to manually launch the backups each night and that work fine. I
previously was using Sql 2000 and the backup jobs ran without any problems.On Apr 19, 1:40 pm, Todd <T...@.discussions.microsoft.com> wrote:
> I have a new installation of SQL 2005 standard and I cannot create an
> automatic backup. When I launch the wizard I get an error " Failed to
> retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid column
> name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I can
> then create my backup job, but upon completion I get these 2 error:
> Invalid column name 'from_msx'.
> Invalid column name 'has_target'.
> I have to manually launch the backups each night and that work fine. I
> previously was using Sql 2000 and the backup jobs ran without any problems.
Is this a server you upgraded to 2005 was a target server and prior to
upgrade did the server have master server?|||No this is a new Server not an upgrade. I moved the 2000 db over to this
server.
"Bulent" wrote:
> On Apr 19, 1:40 pm, Todd <T...@.discussions.microsoft.com> wrote:
> > I have a new installation of SQL 2005 standard and I cannot create an
> > automatic backup. When I launch the wizard I get an error " Failed to
> > retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid column
> > name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I can
> > then create my backup job, but upon completion I get these 2 error:
> > Invalid column name 'from_msx'.
> > Invalid column name 'has_target'.
> >
> > I have to manually launch the backups each night and that work fine. I
> > previously was using Sql 2000 and the backup jobs ran without any problems.
> Is this a server you upgraded to 2005 was a target server and prior to
> upgrade did the server have master server?
>

Backup Wizard 2005 Standard

I have a new installation of SQL 2005 standard and I cannot create an
automatic backup. When I launch the wizard I get an error " Failed to
retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid column
name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I can
then create my backup job, but upon completion I get these 2 error:
Invalid column name 'from_msx'.
Invalid column name 'has_target'.
I have to manually launch the backups each night and that work fine. I
previously was using Sql 2000 and the backup jobs ran without any problems.
On Apr 19, 1:40 pm, Todd <T...@.discussions.microsoft.com> wrote:
> I have a new installation of SQL 2005 standard and I cannot create an
> automatic backup. When I launch the wizard I get an error " Failed to
> retrieve data for this request. (Microsoft.Sqlserver.SmoEnum) Invalid column
> name 'msx_job_id'. (Microsoft SQL Server, Error: 207). I click okay and I can
> then create my backup job, but upon completion I get these 2 error:
> Invalid column name 'from_msx'.
> Invalid column name 'has_target'.
> I have to manually launch the backups each night and that work fine. I
> previously was using Sql 2000 and the backup jobs ran without any problems.
Is this a server you upgraded to 2005 was a target server and prior to
upgrade did the server have master server?
|||No this is a new Server not an upgrade. I moved the 2000 db over to this
server.
"Bulent" wrote:

> On Apr 19, 1:40 pm, Todd <T...@.discussions.microsoft.com> wrote:
> Is this a server you upgraded to 2005 was a target server and prior to
> upgrade did the server have master server?
>

backup to tape failed

I was trying to do a backup to tape but it failed with the following message:

Msg 3229, Level 16, State 2, Line 2

Request for device '\\.\Tape0' timed out.

Msg 3013, Level 16, State 1, Line 2

BACKUP DATABASE is terminating abnormally.

Any clues why this happened?

Any help is appreciated.

Take a look at the system event log and sql errorlogs.

You may have a hardware issue with the tape drive (or the connection to it...).

If the OS returned an error code to sql server, it will have been logged in the errorlog.

That 3229 is also raised if a tape mount was pending but a new tape was not loaded prior to the timeout. However, that instance should have "state = 1" and not 2 as you report.

|||

Thanks for the help. The problem was with the MEDIANAME. i was specifying a new Medianame.

If MEDIANAME is specified, it must match the previously specified media name already existing on the backup volume.

Thanks Anyways