SQLqueries

Unable to install SQL 2008 due to the remnants of a previous installation

AmruthaVarshiniJ — Wed, 03 Nov 2010 06:14:11 GMT

Sometime remnants of a previous installation/ a failed install can prevent us from reinstalling SQL server

I have documented the consequence of one such instance which rendered us to be unable to install SQL 2008 from the server

· When we launched the setup we got the following error :

SQL Server Setup failure. 1

SQL Server Setup has encountered the following error:

MsiGetProductlnfo failed to retrieve Productversion for package with Product Code = ‘{DF167CE3-60E7-44EA-99EC-2507C 5 1F37AE}’. Error code: 1605..

We got the obfuscated product code :

---------------------------

Obfuscated product code Result

---------------------------

3EC7S1FD7E06AE4499CE52705CF173EA

---------------------------

· Went into the registry (start-->run-->regedit) and took a full registry backup

· We then went to the following key HKEY_CLASSES_ROOT\Installer\UpgradeCodes

· We then used the obfuscated product code : 3EC761FD-7E06-AE44-99CE-52705CF173EA

· We searched for it within the registry key HKCR\Installer\UpgradeCodes for matches.

· We got one match and deleted its parent.

· We ran the installation which failed yet again with this error :

TITLE: SQL Server Setup failure.

------------------------------

SQL Server Setup has encountered the following error:

MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{DF167CE3-60E7-44EA-99EC-2507C51F37AE}'. Error code: 1605..

------------------------------

BUTTONS:

------------------------------

· We navigated to this key :HKEY_CLASSES_ROOT\Installer\Features\3EC761FD7E06AE4499CE52705CF173EA and saw that we were having issues (access denied ) issues with it

· We obfuscated the GUID again : DF167CE360E744EA99EC2507C51F37AE , we searched for it and found a key

· We added everyone to the root and added the full control to administrators, System and even replace permission entries to all sub-keys. Same error.

· Since we not have any special changes/permissions set, decided to reset the registry permissions(needs to be used with caution , contingent on the fact that we do not have customized permissions set on the registry)

· We used the KB : https://support.microsoft.com/kb/313222 to reset the permissions so that the setup program will have access to it

· We got this error again from the setup:

MSI error description: Could not open key: UNKNOWN\Components\00C004FEE241478418DBB8505B78CBC5\D56941F2B76595E4DABEA0C21C3EDAFD. Verify that you have sufficient access to that key, or contact your support personnel.

TITLE: Microsoft SQL Server 2008 Setup

------------------------------

The following error has occurred:

Could not open key: UNKNOWN\Components\9419DB21C522CF24897B0DF659D5B883\5B3A043535835474EB2DDDF95F733113. Verify that you have sufficient access to that key, or contact your support personnel.

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0xDF039760%25401201%25401

------------------------------

· Every time setup for giving us errors for different GUID's

· The registry permissions were altered to prevent us from running the setup

· We used this KB : https://support.microsoft.com/kb/237607 to use the Regini.exe tool to modify registry permissions from within a script.

· While trying to reset the permissions on 2 registry entries we are getting the following message.

REGINI: CreateKey (\registry\machine\SOFTWARE\Microsoft\Windows\CurrentVersion\I

nstaller\UserData\S-1-5-18\Components\9419DB21C522CF24897B0DF659D5B883\5B3A04353

5835474EB2DDDF95F733113) relative to handle (000000000) failed - 5

REGINI: Failed to load from file 'c:\Users\msm\Desktop\test.txt' (5)

· We then took the permissions on the following hive : \SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components and then replace the security permissions on the sub keys

· This time the setup of SQL server went through successfully

Regards,
Amrutha Varshini J
SE, Microsoft SQL Server

SQLSERVERAGENT service fails to start , SQLServer Error: 229

AmruthaVarshiniJ — Sun, 24 Oct 2010 09:18:28 GMT

Issue

The SQL agent services fail to start and give the following error when we try starting it from the services console :

When we attempt to start SQL agent services we get the following error :

---------------------------

Services

---------------------------

The SQLSERVERAGENT service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

---------------------------

--------------------------

Environment

Windows 2003

Service Pack 2

SQL Version: SQL2000 Enterprise Edition

SQL Service Pack: RTM

SQL Build: 8.00.2039

SQL Platform: x86

SQL Server Name: HRSERVER

SQL Instance Name: default

· We collected the SQL agent logs and saw the following errors

2010-10-24 16:51:19 - ! [298] SQLServer Error: 229, EXECUTE permission denied on object 'sp_sqlagent_has_server_access', database 'msdb', owner 'dbo'. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

2010-10-24 16:51:19 - ! [298] SQLServer Error: 229, EXECUTE permission denied on object 'sp_sqlagent_get_startup_info', database 'msdb', owner 'dbo'. [SQLSTATE 42000]

2010-10-24 16:51:19 - ? [100] Microsoft SQLServerAgent version 8.00.2039 (x86 unicode retail build) : Process ID

2010-10-24 16:51:19 - ? [100] Microsoft SQLServerAgent version 8.00.2039 (x86 unicode retail build) : Process ID 3696

2010-10-24 16:51:19 - ? [101] SQL Server version 8.00.2039 (0 connection limit)

2010-10-24 16:51:19 - ? [102] SQL Server ODBC driver version 3.86.3959

2010-10-24 16:51:19 - ? [103] NetLib being used by driver is DBMSSHRN.DLL; Local host server is

2010-10-24 16:51:19 - ? [310] 8 processor(s) and 2048 MB RAM detected

2010-10-24 16:51:19 - ? [339] Local computer is HRSERVER running Windows NT 5.2 (3790) Service Pack 2

2010-10-24 16:51:19 - ! [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role

2010-10-24 16:51:19 - ? [098] SQLServerAgent terminated (normally)

· Just a test changed the startup account from the local system to a domain account and subsequently added it to the sysadmin server role which enabled SQL agent services to start up

· SQL server services inspite of having local system account as its startup , was working fine but SQL Agent on the other hand failed to startup with local system account

· We then Checked the following permissions for the service account under secpol.msc (local security policy)

• Act as Part of the Operating System

• Bypass Traverse Checking

• Lock Pages In Memory

• Log on as a Batch Job

• Log on as a Service

• Replace a Process Level Token

· We added the "SYSTEM" account to all these permissions and we were able to start it up successfully

Regards,

Amrutha

SQL browser fails to come online after changing it to a static port

AmruthaVarshiniJ — Sun, 24 Oct 2010 07:10:00 GMT

Issue

SQL clustered service fails to come online after an attempt to change a static port

· We noticed the following error in the SQL server error logs

2010-10-24 09:10:53.92 spid6s      The resource database build version is 9.00.4230. This is an informational message only. No user action is required.
2010-10-24 09:10:54.25 spid6s      Error: 15466, Severity: 16, State: 1.
2010-10-24 09:10:54.25 spid6s     An error occurred during decryption.
2010-10-24 09:10:54.26 spid10s     Starting up database 'model'.
2010-10-24 09:10:54.26 Server      Error: 17182, Severity: 16, State: 1.
2010-10-24 09:10:54.26 Server      TDSSNIClient initialization failed with error 0xd, status code 0x10.
2010-10-24 09:10:54.26 spid6s      Server name is 'SQ02PDB\SQ02PDB'. This is an informational message only. No user action is required.
2010-10-24 09:10:54.26 Server      Error: 17182, Severity: 16, State: 1.
2010-10-24 09:10:54.26 Server      TDSSNIClient initialization failed with error 0xd, status code 0x1.
2010-10-24 09:10:54.26 spid6s      The NETBIOS name of the local node that is running the server is 'GRRAPICL21B'. This is an informational message only. No user action is required.
2010-10-24 09:10:54.26 Server      Error: 17826, Severity: 18, State: 3.
2010-10-24 09:10:54.26 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.
2010-10-24 09:10:54.26 Server      Error: 17120, Severity: 16, State: 1.
2010-10-24 09:10:54.26 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.

· We were running into a known issue: KB 907853 SQL Server 2005 does not start if the server-side TCP Port field contains trailing spaces

· We looked at this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll and there was a trailing space in the hive: TcpDynamicPorts

· Since this hive was check pointed went ahead and removed the checkpoint:

cluster res "SQL Server (instancename)" /removecheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

· We deleted the trailing spaces and re-added the checkpoint :

cluster res "SQL Server (instancename)" /addcheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

Regards,
Amrutha Varshini

SQL 2008 setup (Add node) process fails with "Value cannot be null. Parameter name: group"

AmruthaVarshiniJ — Mon, 20 Sep 2010 19:53:02 GMT

SQL Server 2008 SP1 (Add Node) process fails when we attempt to add the passive node, we get the following error :

From the Summary.txt :

Detailed results:

Feature: Database Engine Services

Status: Failed: see logs for details

MSI status: Passed

Configuration status: Failed: see details below

Configuration error code: 0x11428655

Configuration error description: Value cannot be null. Parameter name: group

Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100910_140955\Detail.txt

Feature: SQL Server Replication

Status: Failed: see logs for details

MSI status: Passed

Configuration status: Failed: see details below

Configuration error code: 0x11428655

Configuration error description: Value cannot be null. Parameter name: group

Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100910_140955\Detail.txt

Feature: Full-Text Search

Status: Failed: see logs for details

MSI status: Passed

Configuration status: Failed: see details below

Configuration error code: 0x11428655

Configuration error description: Value cannot be null. Parameter name: group

Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100910_140955\Detail.txt

· Remove the passive node from the SQL cluster (Remove Node as per https://msdn.microsoft.com/en-us/library/ms191545.aspx )

· Reboot the node

· Disable filestream by running the following command -

EXEC sp_configure filestream_access_level, 0

Reconfigure

· Install SQL Server on remote node.

· Enable filestream by running the following command -

EXEC sp_configure filestream_access_level, 2

Reconfigure

· Even after we did this add node failed with the same error :

2010-09-20 18:20:24 SQLEngine: --FilestreamConfiguration: GetFilestreamRegKeyName: IsPreRefresh = False, IsClustered = True, Filestream key is SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.ENGR\Filestream

2010-09-20 18:20:24 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine

2010-09-20 18:20:24 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.ENGR\Filestream

2010-09-20 18:20:24 Slp: Sco: Attempting to get registry value EnableLevel

2010-09-20 18:20:24 Slp: Sco: Attempting to get registry value InstanceGuid

2010-09-20 18:20:24 Slp: Sco: Attempting to get registry value ShareName

2010-09-20 18:20:24 Slp: Sco: Attempting to get registry value RsFxVersion

2010-09-20 18:20:24 SQLEngine: --FilestreamConfiguration: Filestream registry values: EnableLevel: 3 InstanceGuid: {72389ac8-d8d9-4a77-92aa-a9961ea121c5} ShareName: ENGR_FileStreams, RsFxVersion: 0103

2010-09-20 18:20:24 SQLEngine: --FilestreamConfiguration: Filestream registry values: EnableLevel: 3 ShareName: ENGR_FileStreams

2010-09-20 18:20:24 Slp: FindFileShareFromInstance: instanceName: ENGR shareName: ENGR_FileStreams

2010-09-20 18:20:24 Slp: FindFileShareFromInstance: Share resource found: SQL Server FILESTREAM share (ENGR)

2010-09-20 18:20:24 Slp: FindFileShareFromInstance: Share resource ShareName ENGR did not match passed in ShareName: ENGR_FileStreams

2010-09-20 18:20:24 SQLEngine: --FilestreamConfiguration: FILESTREAM: Clustered setup, adding File Share resource for instance: ENGR Share Name: ENGR_FileStreams

2010-09-20 18:20:24 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC.

2010-09-20 18:20:24 Slp: Value cannot be null.

Parameter name: group

2010-09-20 18:20:24 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC.

2010-09-20 18:20:24 Slp: System.ArgumentNullException: Value cannot be null.

2010-09-20 18:20:24 Slp: Parameter name: group

· This was surprising as had disabled the FILESTREAM option

· We checked the sp_configure output which had Run value =0 (Which means the file stream had indeed been disabled )

· We repeated the “Remove Node” process and removed even the shared components

· We went ahead and recycled the services (take the service offline and bring it back online). If there are multiple nodes it would be best to failover and failback between them.

· We restarted setup and this time it went through successfully

Regards,

Amrutha

Microsoft SQL support

How do we uninstall Just the replication component in SQL 2008 ?

AmruthaVarshiniJ — Wed, 15 Sep 2010 14:03:00 GMT

In order to uninstall just the Replication component in SQL 2008 we need to do the following:

Method 1

1) Go into Add/remove programs and choose the instance in question :

2) Click on the Uninstall/Change button

3) Click on Remove when the landing page is launched :

4)Select the instance again (we need to select the SQL engine and not the shared features component)

5)Select the Replication sub feature :

6)After this we can click on 'Next' till we get the complete button .

Method 2

From command prompt :

1)Browse to the setup media form the command prompt and execute this :

Setup.exe /Action=Uninstall /FEATURES=Replication /INSTANCENAME=MSSQLSERVER /INDICATEPROGRESS

The windows will come up indicating the progress, when it comes to the select features box we see that Replication comes pre-checkmarked

A quick view of the summary.txt will yield the following :

ACTION:                        Uninstall
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100915_132511\ConfigurationFile.ini
FEATURES:                      REPLICATION
HELP:                          False
INDICATEPROGRESS:              False
INSTANCEID:
INSTANCENAME:                  MSSQLSERVER
QUIET:                         False
QUIETSIMPLE:                   False
X86:                           False

Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100915_132511\ConfigurationFile.ini

Detailed results:
Feature:                       SQL Server Replication
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed

Following the above set of steps will ensure that we uninstall the SQL replication component without hampering the Main SQL instance

Regards,
Amrutha Varshini J
Microsoft SQL support