Until recently we received backups of a clients database
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.
If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.
|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL
>
>.
>
|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
Showing posts with label received. Show all posts
Showing posts with label received. Show all posts
Wednesday, March 21, 2012
Faulty Restore
Until recently we received backups of a clients database
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
--
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
>> Until recently we received backups of a clients
database
>> and restored it with no problems. They are running SQL
>> 2000 on NT 4.0. About a month ago we noticed some
problem
>> with the backups, DBCC CHECKDB revealed consistency
>> errors in the databases after restore. We are running
SQL
>> 2000 SP3a on XP Pro. They can restore there backup
>> locally but when ever we restore them we get errors.
>> Any help would be very much appreciated.
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
--
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> >--Original Message--
> >If there are consistency errors with the restored db it
> is most likely they
> >exist in the original one. They need to fix the errors
> in the original db
> >before you can get good backups.
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Geoff Aukett" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> >> Until recently we received backups of a clients
> database
> >> and restored it with no problems. They are running SQL
> >> 2000 on NT 4.0. About a month ago we noticed some
> problem
> >> with the backups, DBCC CHECKDB revealed consistency
> >> errors in the databases after restore. We are running
> SQL
> >> 2000 SP3a on XP Pro. They can restore there backup
> >> locally but when ever we restore them we get errors.
> >>
> >> Any help would be very much appreciated.
> >
> >
> >.
> >
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
--
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
>> Until recently we received backups of a clients
database
>> and restored it with no problems. They are running SQL
>> 2000 on NT 4.0. About a month ago we noticed some
problem
>> with the backups, DBCC CHECKDB revealed consistency
>> errors in the databases after restore. We are running
SQL
>> 2000 SP3a on XP Pro. They can restore there backup
>> locally but when ever we restore them we get errors.
>> Any help would be very much appreciated.
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
--
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> >--Original Message--
> >If there are consistency errors with the restored db it
> is most likely they
> >exist in the original one. They need to fix the errors
> in the original db
> >before you can get good backups.
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Geoff Aukett" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> >> Until recently we received backups of a clients
> database
> >> and restored it with no problems. They are running SQL
> >> 2000 on NT 4.0. About a month ago we noticed some
> problem
> >> with the backups, DBCC CHECKDB revealed consistency
> >> errors in the databases after restore. We are running
> SQL
> >> 2000 SP3a on XP Pro. They can restore there backup
> >> locally but when ever we restore them we get errors.
> >>
> >> Any help would be very much appreciated.
> >
> >
> >.
> >
Faulty Restore
Until recently we received backups of a clients database
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
> news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL[vbcol=seagreen]
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx
.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
>
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
> news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL[vbcol=seagreen]
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx
.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
>
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
Monday, March 19, 2012
Fatal error 7105
We have received this error 5 times since 30 Sep 2003.
Has anyone seen it before? Does anyone know why it occurs
and/or what it means?
I have tried using DBCC CHECKTABLE and DBCC CHECKDB to
identify problem areas but they all come back ok.Don't know if this will help, but worth checking:
http://support.microsoft.com/default.aspx?scid=kb;en-us;304847&Product=sql
"Robert Marda" <postmaster@.marda.htmlplanet.com> wrote in message
news:01ca01c38c1e$a3683950$a101280a@.phx.gbl...
> We have received this error 5 times since 30 Sep 2003.
> Has anyone seen it before? Does anyone know why it occurs
> and/or what it means?
> I have tried using DBCC CHECKTABLE and DBCC CHECKDB to
> identify problem areas but they all come back ok.
Has anyone seen it before? Does anyone know why it occurs
and/or what it means?
I have tried using DBCC CHECKTABLE and DBCC CHECKDB to
identify problem areas but they all come back ok.Don't know if this will help, but worth checking:
http://support.microsoft.com/default.aspx?scid=kb;en-us;304847&Product=sql
"Robert Marda" <postmaster@.marda.htmlplanet.com> wrote in message
news:01ca01c38c1e$a3683950$a101280a@.phx.gbl...
> We have received this error 5 times since 30 Sep 2003.
> Has anyone seen it before? Does anyone know why it occurs
> and/or what it means?
> I have tried using DBCC CHECKTABLE and DBCC CHECKDB to
> identify problem areas but they all come back ok.
Friday, February 24, 2012
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Subscribe to:
Posts (Atom)