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 Not Deleting

We're running SQL Server 2000 service pack 4. I've created a Maintenance
Plan that backs up all user databases, each to its own subfolder, every
night. The plan is supposed to delete old copies as well which it is not
doing. If I change the plan to backup only 1 database it works (old copies
deleted). When I switch it to all user databases, no more deletes. And the
sqlmaint log file does not even show that any deletes were attempted. Note
that we do have some databases offline, so those are skipped, of course, and
the job does fail.
Please help! What's the secret to get the older files to delete?
Here's the Step on the SQL Agent job:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
21EA0A98-9812-4AEA-8BC0-08AEAEAB24EC -Rpt "c:\temp\DB Maintenance
Plan14.txt" -DelTxtRpt 1WEEKS -WriteHistory -VrfyBackup -BkUpMedia
DISK -BkUpDB "D:\Backup" -DelBkUps 1DAYS -CrBkSubDir -BkExt "BAK"'
Thanks,
Krip
>I believe that deletion is done *at the end* of the job, so if anything
>fails, it bails out and no deletion is performed. You can try by first
>including only database so the whole job succeeds.
Tibor,
Thanks for the tip! I detached all our offline databases, and job finishes
without error, and deletes the old backups. Beautiful.
-Krip
|||I have also seen this behavior when the plan includes both Full and Simple
Recovery model databases.
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Krip" <amk@.kynetix.com> wrote in message
news:7A2C4350-5AED-4F70-A22A-47E64ED68DFD@.microsoft.com...
> Tibor,
> Thanks for the tip! I detached all our offline databases, and job
> finishes without error, and deletes the old backups. Beautiful.
> -Krip
>

BackupIoRequest::WaitForIoCompletion failure when restoring database

I have MS SQL 200 Server Developer Edition Installed from MSDN collection. (New installation with service pack 2). When I try to restore 7GB or bigger database, following error occurs in eventlog:

Source: MSSQLSERVER
Category: (6)
ID: 18210
Date: 11.9.2007
Time: 14:50:09
Description:
BackupIoRequest::WaitForIoCompletion: write failure on backup device ''. Operating system error 1450(here is message in local language like "here is no resources to complete requested service").

But I am not writting to backup device, I am restoring. Thank for any helpful answer.

Not sure about the cause of the error.. Check if its related to this KB : http://support.microsoft.com/default.aspx?scid=kb;en-us;304101

|||

Thank you, dinakar.

KB howto i tried, but with no success.

Backup/Restore SP2 to SP3?

Can I take a Backup created on a server running SQL Server
2000 (Service Pack 2) and Restore it on a server running
SQL Server 2000 (Service Pack 3)? (Without problems, of
course).
I want to not only restore User DBs, but also System DBs
sush as Master, Model, and msdb.
ThanksSystem databases, no. YOu cannot restore a previous
version (i.e. SP2) under SP3.
For user dbs, sure.
>--Original Message--
>Can I take a Backup created on a server running SQL
Server
>2000 (Service Pack 2) and Restore it on a server running
>SQL Server 2000 (Service Pack 3)? (Without problems, of
>course).
>I want to not only restore User DBs, but also System DBs
>sush as Master, Model, and msdb.
>Thanks
>.
>|||Allan
Does this mean that I can restore a user database saved on SP2 into SP3?
Ron Lounsbury
"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
news:561601c3b2c4$5b6ed470$a601280a@.phx.gbl...
> System databases, no. YOu cannot restore a previous
> version (i.e. SP2) under SP3.
> For user dbs, sure.
> >--Original Message--
> >Can I take a Backup created on a server running SQL
> Server
> >2000 (Service Pack 2) and Restore it on a server running
> >SQL Server 2000 (Service Pack 3)? (Without problems, of
> >course).
> >
> >I want to not only restore User DBs, but also System DBs
> >sush as Master, Model, and msdb.
> >
> >Thanks
> >
> >.
> >|||Yes, of course, you can. I do that all the time. Imagine
if you couldn't restore an SP2 user database to an SP3
instance, you would have to upgrade your Dev and prod
environments at the same time if you want to copy any
databases from the prod to the Dev for whatever purposes.
Linchi
>--Original Message--
>Allan
> Does this mean that I can restore a user database
saved on SP2 into SP3?
>Ron Lounsbury
>
>"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
>news:561601c3b2c4$5b6ed470$a601280a@.phx.gbl...
>> System databases, no. YOu cannot restore a previous
>> version (i.e. SP2) under SP3.
>> For user dbs, sure.
>> >--Original Message--
>> >Can I take a Backup created on a server running SQL
>> Server
>> >2000 (Service Pack 2) and Restore it on a server
running
>> >SQL Server 2000 (Service Pack 3)? (Without problems, of
>> >course).
>> >
>> >I want to not only restore User DBs, but also System
DBs
>> >sush as Master, Model, and msdb.
>> >
>> >Thanks
>> >
>> >.
>> >
>
>.
>