SQL Server Q&A

Symptoms
When the Configuring Server portion of a SQL Server 7.0 installation is in progress, this series of error messages may appear:

{acmsetup.EXE – Application Error
The application failed to initialize properly (0xc0000006).Click on OK to terminate the application.}Followed by:

sqlservr.exe – Unable To Locate DLL
The dynamic link library MSWSTR10.DLL could not be found in the specified path:
d:\MSSQL7\binn;C:\WINNT;C:\WINNT\system32Followed by:

Setup
Setup failed to configure the server.Refer to the server error logs and cnfgsvr.out for more information.If you run just the Mdac_typ.exe executable file that is located in the x86\Other folder of the SQL Server 7.0 CD, you may see:This error message:

acmsetup.EXE – Application Error
The application failed to initialize properly (0xc0000006).Click on OK to terminate the application.An entry similar to this in the Cnfgsvr.out file:

Starting Service…An error occurred while attempting to start the service (1053)SQL Server Configuration failed. An entry similar to this in the Sqlstp.log file:

08:56:46 Path successfully updated. 08:56:46 %SystemRoot%\system32;%SystemRoot%;D:\MSSQL7\BINN 08:56:46 D:\MSSQL7\binn\cnfgsvr.exe-Silent 2 -NoSampleDB 0 -SQLPath”D:\MSSQL7\” -SQLDataPath “E:\MSSQL7\” -SortID 52 -LCIDCompStyle “1033-196609″ -HWND 27001094 -User sa -Pwd 08:58:58 Process Exit Code: (-1)08:59:00 Setup failed to configure the server.Refer to the server error logs and cnfgsvr.out for more information. 08:59:00 Action CleanUpInstall: 08:59:00 C:\TEMP\_ISTMP10.DIR\scm.exe-Silent 1 -Action 4 -Service SQLServerAgent 08:59:00 Process Exit Code: (1060) The specified service does not exist as an installed service. 08:59:00 C:\TEMP\_ISTMP10.DIR\scm.exe-Silent 1 -Action 4 -Service MSSQLServer 08:59:05 Process Exit Code: (0)08:59:05 Installation Failed.
Resolution
An 0xc000006 exception error occurs when the system attempts to retrieve a swapped-out page and fails.

Symptoms
If the Certificate Server is installed on a Microsoft Windows 2000 computer and the Certificate Authority (CA) name is the same as or starts with the machine host name, an attempt to connect to SQL Server 2000 fails.
The following error message appears when you try to connect from SQL Server Query Analyzer:

Unable to connect to server. Server msg 18, level 16, state 1. [Microsoft] [ODBC SQL Server Driver} [Shared Memory] SSL security error The following error message appears when you try to connect from SQL Enterprise Manager:

Unable to connect to server. Reason: SSL security error. ConnectionOpen (SECDoClientHandShake())… The SQLServerAgent service also fails with the following error message:

Could not start SQLserverAgent Service on local computer. The service did not return an error. This could be an internal Windows error or an internal service error. If this error persists, contact your system administrator. Due to the same connectivity errors indicated previously, an attempt to install Microsoft SQL Server 2000 may also fail.
If you attempt the Microsoft SQL Server installation on a computer on which the Certificate Server and the Certificate Authority(CA) name is the same name as or starts with the machine host name, the SQL Server installation on that computer may fail at the configuration stage. During the configuration stage of the installation process, the setup program makes a connection to SQL Server.
This problem applies to any edition of Microsoft SQL Server, including the Microsoft Desktop Engine (MSDE) installation.
The Microsoft SQL Server installation may fail with the following error message:

Setup failed to configure the server. Refer to the server error logs and C:\WINNT\sqlstp.log for more information. If the error message occurs, SQL Server writes the following information in the Cnfgsvr.out file located in the SQL Server Install subfolder:

###############################################################################Starting Service …SQL_Latin1_General_CP1_CI_AS-m -Q -T4022 -T3659Connecting to Server …driver={sql server};server=Instance_Name;UID=<username>;PWD=<strong password>;database=master[Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (SECDoClientHandshake()).driver={sql server};server=ORLANDO;UID=<username>;PWD=<strong password>;database=master[Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (SECDoClientHandshake()).driver={sql server};server=ORLANDO;UID=<username>;PWD=<strong password>;database=master[Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (SECDoClientHandshake()).SQL Server configuration failed.###############################################################################
By default, the Microsoft SQL Server Desktop Engine setup does not generate a Cnfgsvr.out file. The setup program may fail to configure SQL Server and the following error message may appear:

Setup failed to configure the server. Refer to the server error logs and setup error logs for more information. However, note that a configuration failure can occur due to reasons other than the one described in this article.
Resolution
The Certificate Authority (CA) name of the Certificate Server is critical when you have SQL Server 2000 on the same host. When SQL Server 2000 starts and finds a certificate with the same machine name as the subject, SQL Server tries to use it for encryption, even though it is not a valid SQL Server encryption certificate. Therefore, any attempt to connect to that SQL Server computer fails with the error shown in the “Symptoms” section.
The removal of the Certificate Server from the Microsoft Windows 2000 server does not remove the Certification Authority keys. The previously installed keys still affect the computer that is running SQL Server.

Symptoms
When you install Microsoft SQL Server 2005 Service Pack 2 (SP2), SQL Server 2005 Express Edition (SQL Server Express) SP2, or SQL Server Express with Advanced Services SP2, you receive the following error message:

SQL Server Setup failed to execute a command for server configuration.The error was [Microsoft] [SQL Native Client] [SQL Server] CREATE DATABASE failed. Some File names listed could not be created. Check related errorrs.. Refer to the server error logs and Setup logs for detailed error information.Note In this error message, “errorrs” is a misspelling of the word “errors.” Also, the sentence “Check related errorrs..” has two period (.) characters.
Additionally, you experience one of the following symptoms.
Symptom 1When you perform a new installation of SQL Server Express SP2 or of SQL Server Express with Advanced Services SP2, the following error message is logged in the SQLSetup0001_ComputerName_SQL.log file:

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft] [SQL Native Client] [SQL Server]Incorrect syntax near ‘=’.
[SQL Server]Cannot dump ##MS_AgentSigningCertificate##. SYSDBUPG.SQL terminating.This problem occurs if the length of the installationpath exceeds 58 characters.
Symptom 2When you install SQL Server Express SP2 or SQL Server Express with Advanced Services SP2 on an existing instance of SQL Server Express, the followingerror messages is logged in the SQLSetup0001_ComputerName_SQL.log file:

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. Refer to the server error logs and Setup logs for detailed error information.Note In this error message, the sentence “Check related errors..” has two period characters.
This problem occurs if the length of the installationpath exceeds 58 characters.
Symptom 3When you install SQL Server 2005 SP2 on an existing instance ofSQL Server 2005 Service Pack 1 (SP1) or on an existing instance of the original release version of SQL Server 2005, the following error message is logged in the SQL9_Hotfix_KB921896_Sqlrun_Sql.msp.log file:

[SQL Server]Incorrect syntax near ‘=’.
[SQL Server]Cannot dump ##MS_AgentSigningCertificate##. SYSDBUPG.SQL terminating.This problem occurs if the length of the installation path exceeds 128 characters.
Resolution
This problem occurs because the script in the Sysdbupg.sql file contains the following code to escape quotations in a file name.

SELECT @certificate_name = QUOTENAME(@certificate_name, ””)The QUOTENAME function returns null if the length of the input value exceeds 128 characters. The longer path name triggers an error in the script.

Symptoms
When you try to install Microsoft SQL Server 2005 Express Edition Service Pack 1 (SP1) on a computer that is running Windows Vista, you receive the following error message:

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group ‘COMPUTERNAME\SQLServer2005MSSQLUser$COMPUTERNAME$MSSQLSERVER’ not found. Check the name again.. Refer to the server error logs for detailed error information.
Resolution
This problem occurs if the following conditions are true:The Windows Vista-based computer has a name thatconsists oflowercase characters or that consists of a mixture of lowercase characters and uppercase characters. For example, the computer name resembles Workstation-1.You specify a case-sensitive collation setting for the SQL Server service when you install SQL Server 2005 Express Edition SP1.Windows Vista uses the following two methods to return the computer name in response to a request for the computer name:Windows Vista can return the computer name in uppercase characters.Windows Vista can return the computer name in the actual mixed case characters that appear in the System Properties dialog box.During one part of the installation of SQL Server 2005 Express Edition, theSetup programrequests the computer name as mixed characters. However, Windows Vista returns the computer name in uppercase characters instead. The Setup program also requests the computer name in other parts of the installation of SQL Server 2005 Express Edition. Windows Vista may then return the computer name in mixed case characters.
The SQL Server 2005 Express Edition Setup program compares the received computer names. Generally, this does not cause a problem because computer names are not case sensitive in Windows Vista. However, if a case-sensitive collating sequence is specified when you install SQL Server 2005 Express Edition, the result of the name comparison between the computer name in uppercase characters and the computer name in mixed case characters fails. Therefore, the installation of SQL Server 2005 Express Edition SP1 is unsuccessful.