Recent Posts | - July, 2024-7,(1)
- May, 2024-5,(2)
- May, 2023-5,(1)
- February, 2023-2,(1)
- November, 2022-11,(1)
- July, 2022-7,(2)
- March, 2022-3,(1)
- November, 2021-11,(2)
- August, 2021-8,(2)
- July, 2021-7,(2)
- June, 2021-6,(1)
- May, 2021-5,(1)
- March, 2021-3,(1)
- February, 2021-2,(2)
- January, 2021-1,(7)
- December, 2020-12,(3)
- March, 2020-3,(2)
- February, 2020-2,(1)
- December, 2019-12,(2)
- November, 2019-11,(1)
- October, 2019-10,(1)
- September, 2019-9,(1)
- August, 2019-8,(1)
- May, 2019-5,(1)
- April, 2019-4,(2)
- March, 2019-3,(2)
- December, 2018-12,(1)
- November, 2018-11,(4)
- July, 2018-7,(1)
- May, 2018-5,(3)
- April, 2018-4,(2)
- February, 2018-2,(3)
- January, 2018-1,(3)
- November, 2017-11,(2)
- August, 2017-8,(1)
- June, 2017-6,(3)
- May, 2017-5,(5)
- February, 2017-2,(1)
- December, 2016-12,(1)
- October, 2016-10,(2)
- September, 2016-9,(1)
- August, 2016-8,(1)
- July, 2016-7,(1)
- March, 2016-3,(2)
- February, 2016-2,(3)
- December, 2015-12,(5)
- November, 2015-11,(5)
- September, 2015-9,(1)
- August, 2015-8,(2)
- July, 2015-7,(1)
- March, 2015-3,(2)
- February, 2015-2,(1)
- December, 2014-12,(4)
- July, 2014-7,(2)
- June, 2014-6,(2)
- May, 2014-5,(3)
- April, 2014-4,(3)
- March, 2014-3,(1)
- December, 2013-12,(2)
- November, 2013-11,(1)
- July, 2013-7,(1)
- June, 2013-6,(2)
- May, 2013-5,(1)
- March, 2013-3,(3)
- February, 2013-2,(3)
- January, 2013-1,(1)
- December, 2012-12,(3)
- November, 2012-11,(1)
- October, 2012-10,(1)
- September, 2012-9,(1)
- August, 2012-8,(1)
- July, 2012-7,(6)
- June, 2012-6,(1)
- April, 2012-4,(1)
- March, 2012-3,(3)
- February, 2012-2,(3)
- January, 2012-1,(4)
- December, 2011-12,(3)
- October, 2011-10,(3)
- September, 2011-9,(1)
- August, 2011-8,(10)
- July, 2011-7,(2)
- June, 2011-6,(7)
- March, 2011-3,(2)
- February, 2011-2,(3)
- January, 2011-1,(1)
- September, 2010-9,(1)
- August, 2010-8,(2)
- June, 2010-6,(1)
- May, 2010-5,(1)
- April, 2010-4,(3)
- March, 2010-3,(2)
- February, 2010-2,(3)
- January, 2010-1,(1)
- December, 2009-12,(3)
- November, 2009-11,(3)
- October, 2009-10,(2)
- September, 2009-9,(5)
- August, 2009-8,(3)
- July, 2009-7,(9)
- June, 2009-6,(2)
- May, 2009-5,(2)
- April, 2009-4,(9)
- March, 2009-3,(6)
- February, 2009-2,(4)
- January, 2009-1,(10)
- December, 2008-12,(5)
- November, 2008-11,(5)
- October, 2008-10,(13)
- September, 2008-9,(10)
- August, 2008-8,(7)
- July, 2008-7,(8)
- June, 2008-6,(12)
- May, 2008-5,(14)
- April, 2008-4,(12)
- March, 2008-3,(17)
- February, 2008-2,(10)
- January, 2008-1,(16)
- December, 2007-12,(6)
- November, 2007-11,(4)
|
|
|
|
Cumulative hotfix 5, 3215 install issues...
|
1/28/2008 10:36:07 PM
|
|
Oh why, why have the hotfixes become such a head ache, this one fought me quite a bit, but finally she gave in...
Also I usually extract the hotfix manually so I can review it, do this from a command prompt (remember to make the target directory).
c:\sqlserver2005-kb943656-x64-enu.exe /x:c:\sqlhotfix\
The errors seen with 3215 are (some of these we have see with other hotfixes as well).
- MSP Error: 29511 Failure creating local group IUSR_DEVPLYSQL01
- MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
- MSP Error: 29534 Service 'MSSQL$QAEAM' could not be started. Verify that you have sufficient privileges to start system services. The error code is (52) You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
- MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: f:\MSSQL\DATA\distmdl1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
- MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
1st failure was a really strange one:
MSP Error: 29511 Failure creating local group IUSR_DEVPLYSQL01
As I didn't need IIS on this machine I deleted the account as it already existed, mistake there, this lead to the 2nd failure.
2nd failure was on:
MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
This turned out to be a registry issue with deleting items, while not specifically addressing CU 5, it did fix the issue: (http://support.microsoft.com/kb/925976).
For a stand-alone installation of SQL Server 2005
1. |
Remove the following registry subkeys that store SID settings:
• |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\SQLGroup |
• |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\AGTGroup |
• |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\FTSGroup |
• |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\ASGroup | Note In these registry subkeys, MSSQL.X is a placeholder for the corresponding value on a specific system. You can determine MSSQL.X on a specific system by examining the value of the MSSQLSERVER registry entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\ |
2. |
Reinstall the SQL Server 2005 service pack or the SQL Server 2005 hotfix package. |
Finally after all that it installed, as easy as could be !
---------------------------------------
Experienced this error too:
MSP Error: 29534 Service 'MSSQL$QAEAM' could not be started. Verify that you have sufficient privileges to start system services. The error code is (52) You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
-------------
The above error is because of the tcp/ip stack being modified by polyserve, i correct this with a change in the registry networking settings. I've had some questions on what I corrected, basically under Polyserve the virtual IP "floats" to whatever node is active, if for some reason, it is moved from one node to another, and not removed from the previous node...you run into an issue where that other node will not start, you'll receive some very nice errors like these in the sql server errorlog:
2008-05-10 20:52:42.83 Server A self-generated certificate was successfully loaded for encryption. 2008-05-10 20:52:42.85 Server Error: 26024, Severity: 16, State: 1. 2008-05-10 20:52:42.85 Server Server failed to listen on 10.10.48.40 <ipv4> 40020. Error: 0x2741. To proceed, notify your system administrator. 2008-05-10 20:52:42.85 Server Error: 17182, Severity: 16, State: 1. 2008-05-10 20:52:42.85 Server TDSSNIClient initialization failed with error 0x2741, status code 0xa. 2008-05-10 20:52:42.85 Server Error: 17182, Severity: 16, State: 1. 2008-05-10 20:52:42.85 Server TDSSNIClient initialization failed with error 0x2741, status code 0x1. 2008-05-10 20:52:42.85 Server Error: 17826, Severity: 18, State: 3. 2008-05-10 20:52:42.85 Server 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. 2008-05-10 20:52:42.85 Server Error: 17120, Severity: 16, State: 1. 2008-05-10 20:52:42.85 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
This error happens because you can't have two sql server instances use the same IP Address, makes perfect sense when you think through it.
The real problem now that you have root cause, is how to fix it. Polyserve performs some complex tasks with "swapping" registry entries and moving instances, this is not an easy issue to correct and you must be careful. These errors rarely happen on version 3.6, but were pretty common on 3.4.
I'd adise to engage HP / Polyserve support to correct the issue, and then as you become familiar with the SQL Registry and how polyserve works, this can be corrected quite easily yourself.
Depending on the scope of the problem you may only need to focus on the SuperSocketNetLib IP address entries. The server that won't start will most likely contain the virtual ip, and there will be another node in your cluster already running the IP. Sometimes you can edit the IP1, IP2 and IP3 to just reflect your Public, Private and loop Back IP Address. But before starting SQL, Double check where your SQL Instances are "pointing" if they are pointing to the virtul root, than you have a bigger registry issue, and you must correct that too.
Very much fun !
-----------
|
Blog Home
|
|