06.04.2011 Page 1 of 4

SAP Note 896566 - SQL4SAP and SAP Installation Media forSQL Server 2005

Note Language: English Version: 11 Validity: Valid Since 10.03.2009

Summary

SymptomThis note describes the SQL Server 2005 DVDs delivered by SAP for ABAP andJAVA application servers. This note is not related to SAP Business One.

Other termsSQL4SAP.vbs _SqlAuth.vbs

Reason and PrerequisitesThe following SQL Server 2005 DVDs have been delivered by SAP:

DVD: material#: x86: x64: IA64 SP1: SP2: SP3: #1 51031491 x x x - - - #2 51031688 x x x - - - #3 51031832 x x x x - - #4 51032641 x x x - x - #5 51036539 x x x - - x

DVD #2 contains an additional PDF file containing the license agreement.There is no technical difference between these 2 DVDs.DVD #3 contains also service pack 1.DVD #4 contains also service pack 2.DVD #5 contains also service pack 3.

Only the newest DVD will be delivered by SAP. A SQL Server Service Packalso contains all changes of the older Service Packs. This means, there isno need to install SP1 before installing SP2.

SolutionKnown installation issues

SQLServer2005MSSQLUser$COMPUTERNAME$INSTANCENAME' not foundThe installation of SQL Server 2005 may fail on a 64-bit Windows Server2008, once Windows was sysprep'ed and a lower- or mixed case computer namewas choosen.To solve this issue you have to rename Windows and use an upper casecomputer name.

A similar issue occurs on Vista, even on 32-bit and without having tosysprep the machine. Vista Service Pack 1 solves this issue. For detailssee the following Microsoft KB article:

o http://support.microsoft.com/default.aspx?scid=kb;EN-US;932593

Active directory group "sa" existsThe installation of SQL Server 2005 may fail when choosing "Windows Only"

06.04.2011 Page 2 of 4

SAP Note 896566 - SQL4SAP and SAP Installation Media forSQL Server 2005

authentication mode, if there is a Windows group called "sa" either on thelocal server or in the domain (Active Directory). It may occur both duringmanually installation and during installation using SQL4SAP.VBS. In case ofthis error, a dialog box with the following message occurs:

o SQL Server Setup failed to execute a command for serverconfiguration. The error was {Microsoft}{SQL Native Client}{SQLServer}Cannot alter the login 'sa', because it does not exist oryou do not have permission.. Refer to the server error logs andSetup logs for detailed error information.

The Summary.txt log file contains the following lines:

o Product : Microsoft SQL Server 2005Product Version : 9.00.1399.06Install : FailedLog File : C:\Program Files\Microsoft SQL Server\90\SetupBootstrap\LOG\Files\SQLSetup0001_P123456_SQL.logLast Action : InstallFinalizeError String : SQL Server Setup failed to execute a command forserver configuration. The error was {Microsoft}{SQL NativeClient}{SQL Server}Cannot alter the login 'sa', because it does notexist or you do not have permission.. Refer to the server errorlogs and Setup logs for detailed error information.Error Number : 29521

The log file SQLSetup0001_P123456_SQL.log contains the following lines:

o EXEC sp_SetAutoSAPasswordAndDisableOriginial error was 80073b2f (15151)

The solution is to install with "SQL Server and Windows authentication"mode. You may use the script _SqlAuth.vbs for this. After the installationyou can change the authentication mode to "Windows Only" using the SQLServer Management Studio.

SP1 installation hangsThe manual installation of Service Pack 1 for SQL Server 2005 hangs, if theenvironment variable "DIRCMD=/P" is set. The problem does not occur whenusing SQL4SAP.VBS for the installation.

SQL Browser disabledThe SQL Browser Servive is disabled when you install a Default Instance ofSQL Server 2005. This is intended and works as designed. Once you install aNamed Instance on the same machine, the SQL Browser Service is stilldisabled. The problem does not occur when using SQL4SAP.VBS, because thescript manually enables and starts the SQL Browser once you install a SQLServer Named Instance.

06.04.2011 Page 3 of 4

SAP Note 896566 - SQL4SAP and SAP Installation Media forSQL Server 2005

Number of processors is not a power of 2The installation may fail, if the number of logical CPUs is not a power of2.

The Summary.txt log file contains the following lines:

o The SQL Server service failed to start. For more information, seethe SQL Server Books Online topics, "How to: View SQL Server 2005Setup Log Files" and "Starting SQL Server Manually."

For details check the following Microsoft knowledge base article:

o http://support.microsoft.com/kb/954835/en-us

Once you run into this issue, you should set the number of processors toone (/NUMPROC=1) as described in the Microsoft KB article above.

User Account Control (UAC) on Windows 2008 and VISTAVista and Windows Server 2008 have a new feature called User AccountControl (UAC). Once it is turned on, even an administrator does not havethe privilege to install software. An administrator can easily get thisprivilege by confirming the UAC dialog box. This will elevate theprivileges of the logged-on administrator.The UAC dialog box automatically appears once you start SQL4SAP with anon-elevated administrator. Windows performs an user context switch to getthe privileges. As a result, all mapped network drives are lost. To avoidproblems when starting SQL4SAP from a mapped network drive, the scriptSQL4SAP automatically resolves a mapped network drive to its UNC path (x:\is resolved to \\server\share\).There is one specific scenario where SQL4SAP does not work: When logged-onas a non-elevated administrator you may connect to a network share with adifferent user and password. When starting SQL4SAP from this network share,the complete share will disappear during UAC elevation. Since SQL4SAP doesnot know the user and password, the connect using the UNC path does notwork. As a workaround you should start SAL4SAP with an already elevatedadministrator or copy the whole SQL Server DVD to a local drive.

Header Data

Release Status: Released for CustomerReleased on: 10.03.2009 15:03:49Master Language: EnglishPriority: Recommendations/additional infoCategory: Documentation errorPrimary Component: BC-DB-MSS Microsoft SQL Server

The Note is release-independent

06.04.2011 Page 4 of 4

SAP Note 896566 - SQL4SAP and SAP Installation Media forSQL Server 2005

Attributes

Attribute Value

Database system MSSQLSRV