You are currently offline, waiting for your internet to reconnect

Error message when you install SQL Server 2005 SP2, SQL Server Express SP2, or SQL Server Express with Advanced Services SP2: "SQL Server Setup failed to execute a command for server configuration. CREATE DATABASE failed"

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

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 1

When 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 installation path exceeds 58 characters.

Symptom 2

When you install SQL Server Express SP2 or SQL Server Express with Advanced Services SP2 on an existing instance of SQL Server Express, the following error 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 installation path exceeds 58 characters.

Symptom 3

When you install SQL Server 2005 SP2 on an existing instance of SQL 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.
CAUSE
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.
WORKAROUND
To work around this problem, use one of the following methods:
  • Specify an installation path that is less than 58 characters long when you install SQL Server Express SP2 or SQL Server Express with Advanced Services SP2.
  • Specify an installation path that is less than 128 characters long when you install SQL Server 2005 SP2.
However, if you must use an installation path that exceeds the character limit, you can use one of the following workarounds. Use the workaround that corresponds to the symptom that you are experiencing.

Workaround for symptom 1

To work around this problem, follow these steps:
  1. In a text editor such as Notepad, open the Sysdbupg.sql file. This file is located in the following folder:
    InstallationPath\MSSQL.1\MSSQL\Install
    Note InstallationPath represents the installation path.
  2. Locate the following line of code.
    SELECT @certificate_name = QUOTENAME(@certificate_name, '''')
  3. Replace the line of code that you located in step 2 with the following line of code.
    SELECT @certificate_name = '''' + REPLACE(@certificate_name, '''', '''''') + ''''
  4. Save the change, and then exit the editor.
  5. In the error message dialog box, click Retry.
If you have canceled the installation process, follow these steps:
  1. Use Add or Remove programs to remove SQL Server Express SP2 or SQL Server Express with Advanced Services SP2.
  2. Delete the files in the installation folder.
  3. Reinstall SQL Server Express SP2 or SQL Server Express with Advanced Services SP2.
  4. When you receive the error message, follow the steps in the previous procedure.

Workaround for symptom 2

To work around this problem, reinstall SQL Server Express SP2 or SQL Server Express with Advanced Services SP2 on the existing instance of SQL Server Express.

Workaround for symptom 3

To work around this problem, update the Sysdbupg.sql file. To do this, follow steps 1 through 4 in the "Workaround for symptom 1" section. Then reinstall SQL Server 2005 SP2.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 935371 - Last Review: 05/02/2007 18:31:35 - Revision: 2.1

Microsoft SQL Server 2005 Service Pack 2, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Express Edition with Advanced Services

  • kbtshoot kbinfo kbprb KB935371
Feedback
; var varClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" spaña - Español
Paraguay - Español
Venezuela - Español
://c1.microsoft.com/c.gif?DI=4050&did=1&t="> var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" ')[0].appendChild(m);" onload="var m=document.createElement('meta');m.name='ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="http://c1.microsoft.com/c.gif?"> >>