SQL Server Q&A

Symptoms
When you try toinstall Microsoft SQL Server 2005 Express Edition (SQL Server Express) or Microsoft SQL Server 2005 Express Edition with Advanced Services, the installation fails. Additionally, you receive the following error message:

Server SQL Server is terminating because of fatal exception c000001d.If you examine the SQL Server error log when this problem occurs, you see an error message that resembles one of the following:
Error message 1

SqlDumpExceptionHandler: Process 4 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process.
Error message 2

2006-03-02 22:40:24.79 ServerError: 17311, Severity: 16, State: 1.
2006-03-02 22:40:24.79 ServerSQL Server is terminating because of fatal exception c000001d. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.For more information about how to examine the SQL Server error log, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms187885.aspx(http://msdn2.microsoft.com/en-us/library/ms187885.aspx)
Resolution
This problem occurs because of one of the following reasons:The computer on which you try to install SQL Server Express or SQL Server Express with Advanced Services is equipped with a CPU that does not support cache prefetching.
The affected CPUs include VIA Eden CPUs and Transmeta CPUs. Typically, these CPUs are used in devices when low power consumption,low heat, or low noise is important.The media from which you try to install SQL Server Express or SQL Server Express with Advanced Services is corrupted.

Symptoms
When you try toinstall Microsoft SQL Server 2005 Express Edition (SQL Server Express) or Microsoft SQL Server 2005 Express Edition with Advanced Services, the installation fails. Additionally, you receive the following error message:

Server SQL Server is terminating because of fatal exception c000001d.If you examine the SQL Server error log when this problem occurs, you see an error message that resembles one of the following:
Error message 1

SqlDumpExceptionHandler: Process 4 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process.
Error message 2

2006-03-02 22:40:24.79 ServerError: 17311, Severity: 16, State: 1.
2006-03-02 22:40:24.79 ServerSQL Server is terminating because of fatal exception c000001d. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.For more information about how to examine the SQL Server error log, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms187885.aspx(http://msdn2.microsoft.com/en-us/library/ms187885.aspx)
Resolution
This problem occurs because of one of the following reasons:The computer on which you try to install SQL Server Express or SQL Server Express with Advanced Services is equipped with a CPU that does not support cache prefetching.
The affected CPUs include VIA Eden CPUs and Transmeta CPUs. Typically, these CPUs are used in devices when low power consumption,low heat, or low noise is important.The media from which you try to install SQL Server Express or SQL Server Express with Advanced Services is corrupted.

Symptoms
When you start SQL Server Management Studio in Microsoft SQL Server 2005, you receive the following error message in a Microsoft .NET Framework dialog box:

Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Unable to cast object of type‘Microsoft.SqlServer.Management.UI.ConnectionDlg.Personalization’ to type’Microsoft.SqlServer.Management.UI.ConnectionDlg.Personalization’.
Resolution
This problem occurs when you have Microsoft SQL Server 2005 Express Edition or SQL Server 2005 Express Edition with Advanced Services installed side-by-side with one of the following SQL Server 2005 editions:MicrosoftSQL Server 2005 Standard Edition Microsoft SQL Server 2005 Developer Edition Microsoft SQL Server 2005 Enterprise EditionIn this case, the Mru.dat file that is installed by SQL Server 2005 Express Edition or SQL Server 2005 Express Edition with Advanced Services causes this error message.

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.