Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
SpinRecent hotfix installers are typically cluster aware. So in general you don'
t
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes fo
r
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it i
s
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>
Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts
Tuesday, March 20, 2012
Applying SQL hotfixes to a SQL cluster
Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
--
SpinRecent hotfix installers are typically cluster aware. So in general you don't
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes for
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it is
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>|||Hi gurus,
I have a problem. For security purposes I work with two databases; I
use one as production DB (pdb) and the other (cdb) serves as a secure
copy of the production database; and I want to regularly update the
secure copy with the work that I do in the production databasse i.e.
update exsiting stored procedures, tables, views and diagrams or copy
new ones into the secure copy.
A program that at the end of each session in the production db asks if
I want to update the secure copy.
Anyone has an idea for a begginner?
Thanks
Yao
Tony Rogerson wrote:
> Make sure Windows Task Schedular is running on both machines, the setup uses
> it to apply the hotfix to the other node.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
> Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Spin" <Spin@.spin.com> wrote in message
> news:4ifir0F3grg8U1@.individual.net...
> > Gurus,
> >
> > Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> > 2003 SP1 is the OS. Are there any special rules I must follow to execute
> > the SQL hotfix on each node of the cluster? I am assuming I just need to
> > apply the SQL hotfix to each cluster node and that's it. I am hoping it
> > is that easy.
> >
> > --
> > Spin
> >
> >sql
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
--
SpinRecent hotfix installers are typically cluster aware. So in general you don't
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes for
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it is
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>|||Hi gurus,
I have a problem. For security purposes I work with two databases; I
use one as production DB (pdb) and the other (cdb) serves as a secure
copy of the production database; and I want to regularly update the
secure copy with the work that I do in the production databasse i.e.
update exsiting stored procedures, tables, views and diagrams or copy
new ones into the secure copy.
A program that at the end of each session in the production db asks if
I want to update the secure copy.
Anyone has an idea for a begginner?
Thanks
Yao
Tony Rogerson wrote:
> Make sure Windows Task Schedular is running on both machines, the setup uses
> it to apply the hotfix to the other node.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
> Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Spin" <Spin@.spin.com> wrote in message
> news:4ifir0F3grg8U1@.individual.net...
> > Gurus,
> >
> > Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> > 2003 SP1 is the OS. Are there any special rules I must follow to execute
> > the SQL hotfix on each node of the cluster? I am assuming I just need to
> > apply the SQL hotfix to each cluster node and that's it. I am hoping it
> > is that easy.
> >
> > --
> > Spin
> >
> >sql
Monday, March 19, 2012
Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)
Hello,
I'm experiencing some issues with applying SP2. I'm getting a failure for the database engine (on two instances that have been installed on a server). I've noticed in the forum that a few others have had some issues in this area as well. The slightly strange thing is that if I check the version of SQL Server on each instance it is telling me that SP2 has been installed:
9.00.3042.00 SP2 Enterprise Edition (64-bit)
So, the logs tell me I have a failed upgrade, but SQL is telling me it has been upgraded.
Any help would be appreciated.
--
from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Fri Jun 22 11:52:44 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (1C:98) [11:52:44:201]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:201]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 11:52:44: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
the end of that file has the following information:
MSI (s) (1C:98) [11:52:44:701]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 1729
MSI (s) (1C:98) [11:52:44:701]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.
MSI (s) (1C:98) [11:52:44:748]: Attempting to delete file C:\WINDOWS\Installer\3cda1ca.msp
MSI (s) (1C:98) [11:52:44:794]: Cleaning up uninstalled install packages, if any exist
MSI (s) (1C:98) [11:52:44:794]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3cda1ca.msp'
MSI (s) (1C:98) [11:52:44:794]: MainEngineThread is returning 1603
MSI (s) (1C:94) [11:52:44:794]: Destroying RemoteAPI object.
MSI (s) (1C:BC) [11:52:44:794]: Custom Action Manager thread ending.
=== Logging stopped: 22/06/2007 11:52:44 ===
MSI (c) (60:AC) [11:52:44:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:AC) [11:52:44:841]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/06/2007 11:52:44 ===
Did you had a chance to look at
http://support.microsoft.com/default.aspx/kb/933945|||I have had a look at that but wasn't certain that it applied as it was for an earlier fix. I am thinking about trying to install the critical update for SP2 to see if that helps (http://support.microsoft.com/?kbid=934458). I haven't tried that, but am about to. If that works I will update this thread.
From Summary.txt from existing SP2 installation attempt:
-
Product : Database Services (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : Database Services (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
...and at the end of the file:
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29537
|||I tried applying the critical update for SP2 (http://support.microsoft.com/?kbid=934458).
I basically got very, very similar symptons to what I expereienced when installing SP2.
The logs tell me that the process was not successful for the database engine(s) and I am still getting different error messages per instance. Some logs are included:
-
Summary.txt
-
Product Installation Status
Product : SQL Server Database Services 2005 (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : SQL Server Database Services 2005 (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
-
SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
-
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='1802' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:43:40 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1802' GetLastError='0'>
MSI (s) (84:90) [16:43:40:476]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:476]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:43:40: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:43:40: INSTALL. Return value 3.
--
SQL9_Hotfix_KB934458_sqlrun_sql.msp_0.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:45:13 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (84:28) [16:45:13:713]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:713]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:45:13: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:45:13: INSTALL. Return value 3.
--
If I then check what version files are at, sqlservr.exe is at version 2005.90.3054.0 and Microsoft.SqlServer.MaintenancePlanTasks.dll is at version 9.0.3054.0.
select @.@.version is returning "Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)"
So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?
|||Could you check the version of Binaries ? sqlservr.exe|||Associated Hotfix Build: 3159
File version: 2005.090.3054.00
Product Version: 9.00.3054.00
This is for both instances. So, it looks as though the database engine got upgraded successfully - but the logs are telling me otherwise!
|||Exactly.
Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)
Hello,
I'm experiencing some issues with applying SP2. I'm getting a failure for the database engine (on two instances that have been installed on a server). I've noticed in the forum that a few others have had some issues in this area as well. The slightly strange thing is that if I check the version of SQL Server on each instance it is telling me that SP2 has been installed:
9.00.3042.00 SP2 Enterprise Edition (64-bit)
So, the logs tell me I have a failed upgrade, but SQL is telling me it has been upgraded.
Any help would be appreciated.
--
from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Fri Jun 22 11:52:44 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (1C:98) [11:52:44:201]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:201]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 11:52:44: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
the end of that file has the following information:
MSI (s) (1C:98) [11:52:44:701]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 1729
MSI (s) (1C:98) [11:52:44:701]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.
MSI (s) (1C:98) [11:52:44:748]: Attempting to delete file C:\WINDOWS\Installer\3cda1ca.msp
MSI (s) (1C:98) [11:52:44:794]: Cleaning up uninstalled install packages, if any exist
MSI (s) (1C:98) [11:52:44:794]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3cda1ca.msp'
MSI (s) (1C:98) [11:52:44:794]: MainEngineThread is returning 1603
MSI (s) (1C:94) [11:52:44:794]: Destroying RemoteAPI object.
MSI (s) (1C:BC) [11:52:44:794]: Custom Action Manager thread ending.
=== Logging stopped: 22/06/2007 11:52:44 ===
MSI (c) (60:AC) [11:52:44:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:AC) [11:52:44:841]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/06/2007 11:52:44 ===
Did you had a chance to look at
http://support.microsoft.com/default.aspx/kb/933945|||I have had a look at that but wasn't certain that it applied as it was for an earlier fix. I am thinking about trying to install the critical update for SP2 to see if that helps (http://support.microsoft.com/?kbid=934458). I haven't tried that, but am about to. If that works I will update this thread.
From Summary.txt from existing SP2 installation attempt:
-
Product : Database Services (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : Database Services (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
...and at the end of the file:
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29537
|||I tried applying the critical update for SP2 (http://support.microsoft.com/?kbid=934458).
I basically got very, very similar symptons to what I expereienced when installing SP2.
The logs tell me that the process was not successful for the database engine(s) and I am still getting different error messages per instance. Some logs are included:
-
Summary.txt
-
Product Installation Status
Product : SQL Server Database Services 2005 (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : SQL Server Database Services 2005 (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
-
SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
-
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='1802' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:43:40 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1802' GetLastError='0'>
MSI (s) (84:90) [16:43:40:476]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:476]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:43:40: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:43:40: INSTALL. Return value 3.
--
SQL9_Hotfix_KB934458_sqlrun_sql.msp_0.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:45:13 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (84:28) [16:45:13:713]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:713]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:45:13: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:45:13: INSTALL. Return value 3.
--
If I then check what version files are at, sqlservr.exe is at version 2005.90.3054.0 and Microsoft.SqlServer.MaintenancePlanTasks.dll is at version 9.0.3054.0.
select @.@.version is returning "Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)"
So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?
|||Could you check the version of Binaries ? sqlservr.exe|||Associated Hotfix Build: 3159
File version: 2005.090.3054.00
Product Version: 9.00.3054.00
This is for both instances. So, it looks as though the database engine got upgraded successfully - but the logs are telling me otherwise!
|||Exactly.
Sunday, March 11, 2012
apply server pack 3a to new instances?
How do I apply sp3a to a new instance of sql2000? The original is already upgraded. I added three new instances.Each instance will require the service pack.
When you start the service pack setup program you can select the instance
name from a drop down list.
HTH
Ryan Waight, MCDBA, MCSE
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:69DE0125-4A5C-4015-BE8A-BD15FFA75B1B@.microsoft.com...
> How do I apply sp3a to a new instance of sql2000? The original is already
upgraded. I added three new instances.
When you start the service pack setup program you can select the instance
name from a drop down list.
HTH
Ryan Waight, MCDBA, MCSE
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:69DE0125-4A5C-4015-BE8A-BD15FFA75B1B@.microsoft.com...
> How do I apply sp3a to a new instance of sql2000? The original is already
upgraded. I added three new instances.
Subscribe to:
Posts (Atom)