cancel
Showing results for 
Search instead for 
Did you mean: 

Shared String ID 11216 Not Found on installing SQL 2005 SP1

ganesh_borase2
Participant
0 Kudos

Hello everybody,

I started the SQL 2005 installation on windows 2003 64-bit.

I start the setup by using SQL4SAP file, after installing, when

it goes for installing the SP1 it gives the error, unexpected error

"*** Shared String ID 11216 Not Found ***"

when I check log i found following entries

PathSP_IA64 = ServicePack\SQLServer2005SP1-KB913090-ia64-ENU

PathSP_AMD = ServicePack\SQLServer2005SP1-KB913090-x64-ENU.exe (I have this patch)

installing SQL Server Service Pack - build 9.00.2047 ...

Log File: C:\WINDOWS\Hotfix\HotFix.log

Command: "E:\sapdump\sql\x64\ServicePack\SQLServer2005SP1-KB913090-x64-ENU.exe" /norestart /quiet /instancename=MSSQLSERVER

Return Code: 128

-


Log file C:\WINDOWS\Hotfix\HotFix.log

09/18/2030 01:03:21.328 Enumerating applicable products for this patch

09/18/2030 01:03:21.343 Found Redist 2005 product definition

09/18/2030 01:03:21.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion

09/18/2030 01:03:21.625 Successfully read registry key: CommonFilesDir, string value = C:\Program Files (x86)\Common Files

09/18/2030 01:03:21.656 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion

09/18/2030 01:03:21.687 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files (x86)

09/18/2030 01:03:22.390 Found Redist 2005 product definition

09/18/2030 01:03:22.453 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion

09/18/2030 01:03:22.484 Successfully read registry key: CommonFilesDir, string value = C:\Program Files (x86)\Common Files

09/18/2030 01:03:22.500 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion

09/18/2030 01:03:22.531 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files (x86)

09/18/2030 01:03:22.687 Found SQL 2005 product definition

09/18/2030 01:03:22.875 Found OLAP Server 2005 product definition

09/18/2030 01:05:12.281 The patch installation could not proceed due to unexpected errors

09/18/2030 01:05:13.812 The patch installation could not proceed due to unexpected errors

09/18/2030 01:05:13.828

09/18/2030 01:05:13.843 Product Status Summary:

stopping service MSSQLSERVER ...

Return Code: 3

2030-09-18 01:02:32.65 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

Message Box "Installation failed"

The unattended installation failed.

Installation Step: SQL Server Service Pack - build 9.00.2047

Return Code: 128

Log File: C:\WINDOWS\SQL4SAP.log

See SAP note 896566 for known issues

Result: vbOK

HOTFix.log file contain

09/18/2030 01:20:47.343 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe

09/18/2030 01:20:47.421 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe

09/18/2030 01:20:47.453 No GDR branch Hotfix found for product instance MSSQLSERVER

09/18/2030 01:20:49.296 Failed to find following key file for product instance : C:\Program Files\Microsoft SQL Server\90\Tools
Binn\VSShell\Common7\IDE\SQLWB.EXE

when I am trying to manually apply it gives the error

"*** Shared String ID 11216 Not Found ***"

Please suggest how to continue with the installation.

I have also tried to install SP2 but not successful.

Thanks

Ganesh

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ganesh,

What if we install SP3 directly ? Also, is it the same error you get while installing SP2 ?

Note 896566 - SQL4SAP and SAP Installation Media for SQL Server 2005

I hope you are not using Kerberos authentication.

Thanks