The postings on this site are my own and do not represent my Employer's positions, advice or strategies.

LifeAsBob - Blog

 

Home

No Ads ever, except search!
Friday, April 26, 2024 Login
Public

Error installing Cumulative Update 8 6/24/2008 1:31:50 PM

Received the following error on installing cumulative update 8


MSI (s) (40:4C) [13:11:16:515]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Hotfix 3257 for SQL Server Database Services 2005 (64-bit) ENU (KB951217)' 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_KB951217_sqlrun_sql.msp.log.

This was on a sql server installation under polyserve, and sometimes they (the instances) get screwed up.

I tried to start the instance manually and it would not start (net start mssql$Instance).

I checked the error log and found 4 entries:


TDSSNIClient initialization failed with error 0x34, status code 0x1e.

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.


These errors usually indicate and issue with the virtual IP address under the registry settings for the instance, usually one for an IP address that is virtualized on another service, this is a legacy problem from polyserve that was corrected with version 3.6, but if your one of the unlucky few that have this problem, you'd better know your sql registry, or a simple call to HP support, as they know how to figure this out pretty quickly.

After fixing the registry, the cumulative update applied succesfully. 

Always remember on polyserve that once you go into maintenance mode, you should manually start each instance on each node, as if the instance will not start, than more than likely your patch (service pack or cumulative update) will not install correctly.  This doesn't mean there was a problem with the patch, as obviously if an instance is not starting correctly, it is quite hard to patch it.


Blog Home