SQL Server express Installation Problems

From http://download.microsoft.com/download/e/5/3/e53a74e2-9f13-4736-b263-df72af00a8f0/ReadmeSQLEXP2005Advanced.htm#_3462_setup_issues_238p

3.0 Installation Problems

This section describes how to install SP1. SQL Server 2005 express edition with advanced services contains all updates contained in SQL Server 2005 Service Pack 1.

Note:
Unless otherwise stated, these issues only apply to the installation of a new SQL Server express instance.

3.1 installation of the existing SQL native client may fail

The installation may fail and be rolled back. The following error message is displayed: "The installation package of the product Microsoft SQL native client cannot be found. Please try to reinstall it using the valid copy of the installation package "sqlncli. MSI ." To solve this problem, use "add or delete"Program"Uninstall the SQL native client.

3.2 The System Configuration checker fails and the message "Performance Monitor Counter Check failed" is displayed

Before you start installing SQL Server, the System Configuration Checker (SCC) verifies the value of the performance monitor counter registry entry. If SCC cannot verify the existing registry key, or SCC cannot run the lodctr.exe system program, the SCC check fails and the installer is blocked. To complete the installation, you must manually add the registry key.

Note:
Improper registry editing may cause serious problems and may require you to reinstall the operating system. Microsoft does not guarantee that it can solve problems caused by improper registry editing. Back up all important data before editing the registry. For information about how to back up, restore, and edit the registry, see the Microsoft Knowledge Base.Article 256986 .

 

To manually add a counter registry entry, perform the following operations:

1. In the taskbar, click Start"And "run"In "running"TypeRegedit.exeAnd then click OK".

2. Navigate to the following registry key: [HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Perflib]. Search for the following items:

3. • "Last counter" = DWORD: 00000ed4 (5276)

     
     

   • "Last help" = DWORD: 00000ed5 (5277)

   
   

4. Verification value. The value of last counter in the previous step (5276) must be the same as the maximum value of counter in Perflib \ 009 in the following registry items) the value of last help in must be the same as the maximum value of help in Perflib \ 009 in the following registry: [HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Perflib \ 009].

5. Note:
   "" Is used in English (USA.

    

   
   

   
   

6. If necessary, modify the value of last counter and last help in \ Perflib. In the right pane, right-clickLast counterOrLast help, Select "modify", ClickBase = decimal, In the "value"Set the value in the data field, and then click "OK". If necessary, repeat this operation on other items and close the registry editor.

7. Run the SQL Server express installer again.

3.3 If the encryption service of Windows Server 2003 is disabled, the installation fails and the Windows logo requirements dialog box appears.

The Windows encryption service provider (CSP) performs authentication, encoding, and encryption services.CodeWindows-based applications access these services through the CryptoAPI in Windows Server 2003. If the CSP service is stopped or disabled, the SQL Server installer fails and the message "Windows logo requirements" is displayed.

Note:
Before running the SQL Server installer in a Windows Server 2003 failover group, you must start the CSP service on all cluster nodes.

 

To enable the Windows CSP service in Windows Server 2003, perform the following operations:

1. In control panel, Open Administrative Tools"And double-click "service".

   
   

2. In "name"Column, right-click "data encryption service"And then click Start".

   
   

3. Disable "service".

   
   

4. Run the installer.

   
   

3.4 MSDTC is not fully enabled for Windows

Because Microsoft Distributed Transaction Coordinator (ms dtc) is not fully configured in windows, applications may not be able to register SQL Server express resources in distributed transactions. This problem affects the connection server, distributed query, and remote stored procedures that use distributed transactions. To avoid this issue, you must fully enable the ms dtc service on the server where SQL Server Express is installed.

To fully enable ms dtc, do the following:

1. In control panel, Open Administrative Tools"And double-click "component service".

2. In the "console root directory" in the left pane", Click "Component Service"And then expand "computer".

3. Right-click my computer"And then click "properties".

4. InMSDTCTab, click Security Configuration".

5. In "Security Settings"Select All check boxes.

6. Verify that "DTC Login Account" has been set"Set the nameNt authority \ NetworkService.

3.5 "forced encryption" configuration may cause SQL Server express installation failure

If the "Force encryption" option is enabled for the existing SQL Server Client installation configuration, the installation program may fail. To solve this problem, disable this option on all SQL server clients. For the Microsoft Data Access Component (MDAC) client in SQL Server 2000, use the SQL Server 2000 client network utility. For SQL native client, use "add or delete programs"Uninstall SQL native client.

3.6 installing the default instance of SQL Server 2000 may disable SQL Server Express

If you have installed the SQL Server 2000 management tool and the default instance of SQL Server Express on your computer, you can use the SQL Server installer to install the default instance of SQL Server 2000. However, this will disable the installed SQL Server express instance. Therefore, if you have installed the SQL Server 2000 management tool and the default instance of SQL Server Express on your computer, do not install the default instance of SQL Server 2000.

3.7 Install SQL Server Express on Windows Domain Controller

Security description:
We do not recommend that you run SQL Server express in the domain controller.

 

You can install SQL Server express in the Windows Domain Controller. However, SQL Server express cannot run as a local service or network service in the Windows Server 2003 domain controller. The SQL Server service account should run as a Windows domain user account. You can also install the SQL Server service account to run as a local system, but this option is not recommended.

Do not change the server role after installing SQL Server Express. For example, if you have installed SQL Server Express on a Member Server, do not use the dcpromo tool to promote the server to a domain controller. Alternatively, if you have installed SQL Server express in the domain controller, do not use dcpromo to downgrade the server to a Member Server. If you change the role of the server after installing SQL Server Express, the function will be lost. This is not supported.

3.8 The maintenance mode prompts the path of setup.exe.

If you install the new SQL Server Express component in maintenance mode, the system will prompt the location of setup.exe on the SQL Server express installation media. When setting the file location, the parameter must include "setup.exe ". For example, the path "D: \" will fail, and "D: \ setup.exe" will succeed.

3.9 troubleshoot shell script installation failure

When the PATH variable contains parentheses, the setup command shell script can generate Windows Script errors. The cause of this error is that the shell script does not support brackets in PATH variables. This error may occur when you install the 32-bit component on Windows (wow64) 32-bit Windows server. For example, the following script with the PATH value "C: \ Program Files (x86) \" will generate an error, the shell script interpreter incorrectly interprets the brackets in the extended PATH variable as part of the IF/else statement:

IF "%SOME_PATH%" == "" ( SET PATH=%PATH%;%PATH_A% ) ELSE ( SET PATH=%PATH%;%PATH_B% )

To solve this problem, change the script to delete the brackets. For example:

IF "%SOME_PATH%" == "" set PATH=%PATH%;%PATH_A% IF NOT "%SOME_PATH%" == "" set PATH=%PATH%;%PATH_B%

You can also delete SQL items that contain parentheses from the path.

3.10 The installation may fail due to the existing Report Server database file

When you use the savesysdb parameter to run the installer from a command prompt to uninstall an SQL Server express instance (the instance carries the Report Server database of the Reporting Services instance, the Report Server database files are retained together with other system database files. By default, these files are named reportserver $ InstanceName and reportserver $ instancenametempdb. If you use the usesysdb installation parameters to reinstall SQL Server express and specify the instance to host the Report Server database, the installer will not be able to re-create because these database files already exist.

To avoid this problem, Perform one of the following operations:

• Use savesysdb to delete the database on the Report Server before uninstalling it.

  
  

• When you use savesysdb to install parameters, do not install reporting services with SQL Server.
• When installing reporting services, use the rsdatabasename installation parameter to specify a new name for the Report Server data.

3.11 set the database compatibility level when upgrading from MSDE 2000

This issue applies only when you upgrade an MSDE 2000 instance to SQL Server express with advanced services.

When you upgrade an MSDE 2000 instance to SQL Server express with advanced services, the database compatibility level remains at 80 to be backward compatible with existing MSDE 2000 applications. This backward compatibility level disables some new functions of SQL Server express with advanced services. For more information, see the "sp_dbcmptlevel" Reference topic in SQL Server 2005 books online.

3.12 installation may fail if the system database directory contains single quotes

This issue is only applicable when upgrading an SQL Server express instance to an SQL Server express instance with advanced services.

When upgrading an SQL Server express instance to SQL Server express with advanced services, installation may fail if the name of the installation system database contains single quotes. If the installation fails, you must move the system database to a directory with no single quotation marks in the name. For more information about mobile system databases, see "mobile system databases" in SQL Server 2005 books online ".

3.13 restrictions on alter database may cause the upgrade to fail

This issue is only applicable when upgrading an SQL Server express instance to an SQL Server express instance with advanced services.

When you upgrade an SQL Server express instance to SQL Server express with advanced services, the installer will upgrade the system database. If you have imposed restrictions on the alter database syntax, the upgrade may fail. Restrictions on alter database may include the following:

• The alter database statement is explicitly rejected.

  
  

• The Data Definition Language (DDL) trigger for alter database rolls back transactions that contain the alter database statement.

If the alter database restriction exists, the installer cannot upgrade the system database. You must disable these restrictions and then re-run the installer.

3.14 cannot be upgraded to the final release version of SQL Server express with advanced services

The prerelease version of SQL Server express with advanced services cannot be upgraded to the final release version. Before installing the final release version, you must uninstall the pre-release version of SQL Server express with advanced services.

Note:
If Visual Studio 2005 is installed on a computer, you must repair the Windows registry before using the Visual Studio Dataset Designer when uninstalling SQL Server express with advanced services on this computer. For more information, see the Knowledge Base Article 917635 .

3.15 SQL Server express cannot be upgraded when your instance is running.

When your instance is running, multiple database files in the temporary data folder will be locked and cannot be upgraded. To upgrade SQL Server Express, you must manually close the running user instance.

Manually close a user instance:

1. connect to the SQL Server express parent instance and disable the user instance by running the following statement:

2. 
   

   EXEC sp_configure ‘user instances enabled’,0 RECONFIGURE

   
   

3. Run the following statement to determine the MPs queue name for all active user instances:

4. 
   

   Select owning_principal_name, instance_pipe_name from SYS. dm_ OS _child_instances where heart_beat = 'alive'

   
   

   
   

5. UseInstance_pipe_nameConnect to each user instance and run the following statement to manually close the instance:

6. 
   

   Shutdown with Nowait

   
   

   
   

7. Application updates.

8. Run the following statement to re-enable the user instance:

9. 
   

   EXEC sp_configure ‘user instances enabled’, 1 RECONFIGURE

   
   

   
   

3.16 The upgrade may fail when using SQL Server Authentication with user instances

This issue is only applicable when upgrading an SQL Server express instance to an SQL Server express instance with advanced services.

If you have installed an advanced SQL Server express instance to upgrade the SQL Server express instance that has enabled the user instance, you must use Windows authentication. If SQL Server authentication is specified, the upgrade may fail.