January 9, 2009 at 6:58 am
Hello,
Has anyone come across this - SP3 installation on a standard SQL with two instances located in work group fails with this message:
"MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly."
I know the account that is logged and runs the services is the same and is a local Admin (server in a workgroup).
Anyone seen this?
Thanks
A.
January 9, 2009 at 8:24 am
The indication is that the account you are logged in as does not have the permissions to start the service. Try changing your login to an account that has those permissions.
January 9, 2009 at 8:51 am
Nope, like I mentioned, the account is a local admin and with SA privileges (full control) and I can start/stop services with that account just fine.
January 15, 2009 at 4:07 pm
I'm having the same problems!! Anybody else seen this?
Win2003 r2
SQL Server 2005 sp2 with update 9.
using my domain account with sysadmin privs or even SA, cat the error above.
January 16, 2009 at 6:13 am
Try changing the service to run under the localsystem account and see if it will start.
If that goes ok, change the service account back to the domain account from within SQL itself, and see if it's all good.
January 16, 2009 at 10:42 am
I have SQL 2005 server on Windows 2003 and I get the following error no matter if I use a domain account for the service or local service. I noticed the agent part succeeds but the Database Services (MSSQLSERVER) fails.
I have checked out the bogs and someone said to add C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData this path but it was already there. I tried using the local system account and this did not work.
The strange thing is after the installation it states that the entire server including Database Services (MSSQLSERVER) is 9.00.4035.00SP3Standard Edition which is up to date.
I found that even though it cannot restart the service after it goes down after the install I start the service. The log shows it failed but all other data say's it's good. When I try to install again the log states that all services are SP3 which is a good thin.
My question is why does it not start the service. This installation does not look good even though it works. Doing this for the Airforce doesn't bode well when there is errors in the log try explaining that errors are ok to them.
Thanks for your help and any quick replies
January 16, 2009 at 11:09 am
...errors in the log try explaining that errors are ok to them...
That's ok, I got told that tape backups are expected to fail :crazy:
Are there any entries in the event logs when you attempt to start the service? Or anything in the SQL logs?
January 16, 2009 at 12:00 pm
LOL Backups?? wow
Anyway thanks for the reply.. my first blog entry ever.. Anyway starting SP3 installs at 1:pm meanin now. I'll reply back in a moment with results of SQL Server Log. I guess I assumed the SQL summary and log from service pack entry was detailed enough.. Where is my brain I usually check stuff like that first.
January 16, 2009 at 12:03 pm
Throw up the bootstrap log if you can.
January 16, 2009 at 1:04 pm
I have a second to breathe in between installs and reboots. Just wanted to let you know that the Sql 2005 Veritas clustered servers and one other stand alone server worked perfectly error free. It was four of my stand alone servers that was throwing the error. I expected the cluster servers to fail for sure.
January 18, 2009 at 8:25 am
I have the same exact problem, it goes through the installation of sp3 and says the sql server patch failed, but the rest are ok. I can start the instance and it shows the correct number for sp3. When I look at the logs, they indicate that the patch failed to start the instance. I have to then presume that some more stuff was supposed to run with the instance up, but could not, therefore, I am really not patched all the way.
Anybody find a fix for this? It's really driving me nuts!!
January 18, 2009 at 9:16 am
Throw up a post witht the bootstrap logs if you can (start with any txt files in the bootstrap log folder and we can figure it from there), they often have the information needed, although it tends to be cunningly hidden amongst a bunch or worthless (or at least to us not relevant) information.
January 19, 2009 at 12:57 pm
Ok, here's some of the logs, after several attempts. You can see where it has loaded the other components and even the database component, but fails on it's install. Some of these are only partial logs. I do have them all zipped up if there is a place for an attachment or file upload, I would give you the whole thing.
Any suggestions would be helpful. THanks, Mike
****summary.txt
Time: 01/16/2009 15:53:11.559
KB Number: KB955706
Machine: DBFSPM24
OS Version: Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 3
Package Version: 4035
Command-line parameters specified:
Cluster Installation: No
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.3.4035 x86
Database Services (MSSQLSERVER) ENU SP3 2005.090.4035.00 x86 STANDARD
Analysis Services (MSSQLSERVER) ENU SP3 2005.090.4035.00 x86 STANDARD
Integration Services ENU SP3 9.00.4035.00 x86 STANDARD
SQL Server Native Client ENU 9.00.4035.00 x86
Client Components ENU SP3 9.3.4035 x86 STANDARD
MSXML 6.0 Parser ENU 6.20.1099.0 x86
SQLXML4 ENU 9.00.4035.00 x86
Backward Compatibility ENU 8.05.2312 x86
Microsoft SQL Server VSS Writer ENU 9.00.4035.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 4035
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 4035
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number : 29534
Error Description : MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 4035
Product Version (Final) : 4035
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB955706_sqlrun_as.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Integration Services
Product Version (Previous): 4035
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 4035
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 4035
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 1099
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 4035
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 2312
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 4035
Product Version (Final) :
Status : Not Selected
Log File :
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29534
****HOTFIX.LOG****
01/16/2009 15:48:32.545 Locked file: Checking for locked files
01/16/2009 15:48:50.092 Attempting to pause the 32 bit ngen queue
01/16/2009 15:48:50.983 Installing product: SQL9
01/16/2009 15:48:50.983 Installing instance: MSSQLSERVER
01/16/2009 15:48:50.998 Installing target: DBFSPM24
01/16/2009 15:48:50.998 Stopping service: SQLSERVERAGENT
01/16/2009 15:48:56.014 Stopped service: SQLSERVERAGENT
01/16/2009 15:48:56.030 Stopping service: MSSQLServer
01/16/2009 15:48:58.045 Stopped service: MSSQLServer
01/16/2009 15:48:58.045 Installing file: sqlrun_sql.msp
01/16/2009 15:48:58.108 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
01/16/2009 15:48:58.123 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
01/16/2009 15:48:58.123 Registry: Cannot read registry key value "Debug", error 0
01/16/2009 15:50:25.778 MSP Error: 29534 Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
01/16/2009 15:50:36.013 MSP returned 1603: A fatal error occurred during installation.
01/16/2009 15:50:36.013 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
01/16/2009 15:50:36.013 Registry: Cannot read registry key value "Debug", error 0
01/16/2009 15:50:36.450 Copy Engine: Error, unable to install MSP file: d:\3866b0906d8a047925\HotFixSQL\Files\sqlrun_sql.msp
01/16/2009 15:50:36.450 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/16/2009 15:50:36.450 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
01/16/2009 15:50:36.888 Watson: Param1 = StartServices
01/16/2009 15:50:36.888 Watson: Param2 = 0x735e
01/16/2009 15:50:36.888 Watson: Param3 = sqls::Service::Start
01/16/2009 15:50:36.888 Watson: Param4 = 0x735e
01/16/2009 15:50:36.888 Watson: Param5 = sqlsetuplib\service.cpp@301
01/16/2009 15:50:36.888 Watson: Param6 = Unknown
01/16/2009 15:50:36.888 Watson: Param7 = SQL9
01/16/2009 15:50:36.888 Watson: Param8 = Hotfix@
01/16/2009 15:50:36.888 Watson: Param9 = x86
01/16/2009 15:50:36.888 Watson: Param10 = 4035
01/16/2009 15:50:36.888 Installed product: SQL9
01/16/2009 15:50:36.888 Installing product: OLAP9
01/16/2009 15:50:36.888 Installing instance: MSSQLSERVER
01/16/2009 15:50:36.888 Installing target: DBFSPM24
01/16/2009 15:50:36.903 Stopping service: MSSQLServerOLAPService
01/16/2009 15:50:43.372 Stopped service: MSSQLServerOLAPService
01/16/2009 15:50:43.403 Installing file: sqlrun_as.msp
01/16/2009 15:50:43.481 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB955706_sqlrun_as.msp.log
01/16/2009 15:50:43.481 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
01/16/2009 15:50:43.481 Registry: Cannot read registry key value "Debug", error 0
01/16/2009 15:51:19.262 MSP returned 0: The action completed successfully.
01/16/2009 15:51:19.262 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
01/16/2009 15:51:19.262 Registry: Cannot read registry key value "Debug", error 0
01/16/2009 15:51:19.262 Copy Engine: Installed file: d:\3866b0906d8a047925\HotFixAS\Files\sqlrun_as.msp
01/16/2009 15:51:19.278 Restarting OLAP Service MSSQLServerOLAPService since it was previously running
01/16/2009 15:51:19.278 Starting service: MSSQLServerOLAPService
01/16/2009 15:51:22.934 Started service: MSSQLServerOLAPService
01/16/2009 15:51:22.934 Installed target: DBFSPM24
01/16/2009 15:51:22.966 Installed instance: MSSQLSERVER
01/16/2009 15:51:22.966 Installed product: OLAP9
01/16/2009 15:51:22.966 Hotfix package completed
01/16/2009 15:51:22.966 Attempting to continue the 32 bit ngen queue
****SQL9_Hotfix_KB955706_sqlrun_sql.msp.log****
Property(S): SqlToolsBin.2A66A9D0_1F4F_48E5_BA1A_DAE6A7F7FC26 = C:\Program Files\Microsoft SQL Server\90\dts\BinnProperty(S): SQL200532Hotfix4035 = C:\WINDOWS\Installer\8a21bcd5.msp
MSI (s) (40:98) [15:50:35:903]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 3 for SQL Server Database Services 2005 ENU (KB955706)' 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_KB955706_sqlrun_sql.msp.log.
MSI (s) (40:98) [15:50:35:903]: Note: 1: 1729
MSI (s) (40:98) [15:50:35:903]: Transforming table Error.
MSI (s) (40:98) [15:50:35:903]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:919]: Transforming table Error.
MSI (s) (40:98) [15:50:35:919]: Transforming table Error.
MSI (s) (40:98) [15:50:35:919]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:919]: Transforming table Error.
MSI (s) (40:98) [15:50:35:919]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:919]: Transforming table Error.
MSI (s) (40:98) [15:50:35:919]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:919]: Transforming table Error.
MSI (s) (40:98) [15:50:35:919]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:935]: Transforming table Error.
MSI (s) (40:98) [15:50:35:935]: Transforming table Error.
MSI (s) (40:98) [15:50:35:935]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:935]: Transforming table Error.
MSI (s) (40:98) [15:50:35:935]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:935]: Transforming table Error.
MSI (s) (40:98) [15:50:35:935]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:98) [15:50:35:935]: Product: Microsoft SQL Server 2005 -- Configuration failed.
MSI (s) (40:98) [15:50:35:935]: Attempting to delete file C:\WINDOWS\Installer\6b4f7f.msp
MSI (s) (40:98) [15:50:35:966]: Cleaning up uninstalled install packages, if any exist
MSI (s) (40:98) [15:50:35:966]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\6b4f7f.msp'
MSI (s) (40:98) [15:50:35:966]: MainEngineThread is returning 1603
MSI (s) (40:18) [15:50:35:966]: Destroying RemoteAPI object.
MSI (s) (40:FC) [15:50:35:982]: Custom Action Manager thread ending.
=== Logging stopped: 1/16/2009 15:50:35 ===
MSI (c) (F0:20) [15:50:35:997]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F0:20) [15:50:35:997]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/16/2009 15:50:35 ===
January 20, 2009 at 8:56 am
I know I have not replied and will later bu just so you know. Even though the SP3 installation states that it fails it's still successful as I think I mentioned in an earlier post. I did try using the local system account but it still failed. I even used a different domain account to login with but failed. However after going back to reinstall SP3 in my test the log states that all services are SP3.
SP3 works. Not pretty in some cases but does work.
Here some of the log info:
Notice after the SP3 failed and applying it again:
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.3.4035 x86
Database Services (MSSQLSERVER) ENU SP3 2005.090.4035.00 x86 STANDARD
Analysis Services (MSSQLSERVER) ENU SP3 2005.090.4035.00 x86 STANDARD
Notification Services ENU SP3 9.00.4035.00 x86 STANDARD
Integration Services ENU SP3 9.00.4035.00 x86 STANDARD
SQL Server Native Client ENU 9.00.4035.00 x86
Client Components ENU SP3 9.3.4035 x86 STANDARD
I would provide the entire bootstrap log but I don't know if that would be a breach of security and don't want to risk it. Here the part of the log that error'd.
Error from Log
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Fri Jan 16 11:10:17 2009
There was a failure during installation search up in this log file for this message:
Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (DC:70) [11:07:28:004]: Transforming table Error.
MSI (s) (DC:70) [11:07:28:004]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (DC:70) [11:07:28:020]: Transforming table Error.
MSI (s) (DC:70) [11:07:28:020]: Transforming table Error.
MSI (s) (DC:70) [11:07:28:020]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (DC:70) [11:07:28:020]: Transforming table Error.
MSI (s) (DC:70) [11:07:28:020]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (DC:70) [11:07:28:020]: Transforming table Error.
MSI (s) (DC:70) [11:07:28:020]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (DC:70) [11:07:28:020]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (DC:70) [11:07:28:020]: Machine policy value 'DisableMsi' is 1
MSI (s) (DC:70) [11:07:28:020]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (DC:70) [11:07:28:020]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (DC:70) [11:07:28:020]: Product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} is admin assigned: LocalSystem owns the publish key.
MSI (s) (DC:70) [11:07:28:020]: Product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} is managed.
MSI (s) (DC:70) [11:07:28:020]: Running product '{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}' with elevated privileges: Product is assigned.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding PATCH property. Its value is 'd:\d79ba85848f584b9cf8fee6d112d2347\HotFixSQL\Files\sqlrun_sql.msp'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding REINSTALL property. Its value is 'All'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'omus'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding SQLBUILD property. Its value is '4035'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding KBNUMBER property. Its value is 'KB955706'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'ALL'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'd:\d79ba85848f584b9cf8fee6d112d2347'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5484'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding MSIINSTANCEGUID property. Its value is '{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}'.
MSI (s) (DC:70) [11:07:28:020]: TRANSFORMS property is now: :SqlRun01.mst;:InstID01.mst;:InstName01.mst
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (DC:70) [11:07:28:020]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '150'.
PerfTime Stop: CommitSqlUpgrade : Fri Jan 16 11:10:17 2009
Gathering darwin properties for failure handling.
MSI (s) (DC!A0) [11:10:05:612]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (DC!A0) [11:10:05:612]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
'.
Service 'MSSQLSERVER' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly.
MSI (s) (DC!A0) [11:10:05:628]: PROPERTY CHANGE: Adding UpgradeInstruction property. Its value is 'Start service MSSQLSERVER with parameters -r'.
MSI (s) (DC!A0) [11:10:05:644]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER'.
MSI (s) (DC!A0) [11:10:05:644]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup '.
MSI (s) (DC!A0) [11:10:05:659]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup '. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin'.
MSI (s) (DC!A0) [11:10:05:659]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master'.
MSI (s) (DC!A0) [11:10:05:659]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql'.
MSI (s) (DC!A0) [11:10:05:675]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql'.
MSI (s) (DC!A0) [11:10:05:675]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\repl_hotfix_install.sql'.
MSI (s) (DC!A0) [11:10:05:675]: PROPERTY CHANGE: Modifying UpgradeInstruction property. Its current value is 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\repl_hotfix_install.sql'. Its new value: 'Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1
MSI (s) (DC!A0) [11:10:05:691]: PROPERTY CHANGE: Adding SqlUpgradeError property. Its value is '1067'.
Start service MSSQLSERVER with parameters -r
Stop service MSSQLSERVER
Start service MSSQLSERVER with parameters -m SqlSetup
Connect to SQL instance PCDBV601T as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\repl_hotfix_install.sql
Stop service MSSQLSERVER
PerfTime Stop: ComponentUpgradeInstall : Fri Jan 16 11:10:05 2009
MSI (s) (DC!D8) [11:10:08:769]: Note: 1: 2262 2: _sqlAction 3: -2147287038
Doing Action: SetProductNameInstance
PerfTime Start: SetProductNameInstance : Fri Jan 16 11:10:08 2009
Found a instance component ServerCore.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616
SetProductNameInstance is done successfuly.
SetProductNameInstance is done successfuly in Uninstall key.
PerfTime Stop: SetProductNameInstance : Fri Jan 16 11:10:08 2009
MSI (s) (DC:70) [11:10:08:816]: Doing action: UpgradeRestoreServiceStatus.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 11:10:08: SetProductNameInstance. Return value 1.
MSI (s) (DC:70) [11:10:08:816]: Transforming table CustomAction.
January 21, 2009 at 9:29 am
Interesting that your install continues. Mine just chokes and stops, though it does continue after the database upgrade files and installs the rest of the components successfully. We are running windows 2003 r2 if that helps anybody. Input in appreciated.
Viewing 15 posts - 1 through 15 (of 31 total)
You must be logged in to reply to this topic. Login to reply