Microsoft KB Archive/932593

From BetaArchive Wiki

Article ID: 932593

Article Last Modified on 11/20/2007



APPLIES TO

  • Windows Vista Ultimate
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Express Edition with Advanced Services
  • Microsoft SQL Server 2005 Service Pack 1



Bug #: 487992 (SQLBUDT)

SYMPTOMS

When you try to install the original release version of Microsoft SQL Server 2005 or Microsoft SQL Server 2005 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 $INSTANCENAME' not found. Check the name again. Refer to the server error logs for detailed error information.

This problem occurs if the following conditions are true:

  • The name of the computer that is running Windows Vista consists of lowercase characters or of a mixture of lowercase characters and uppercase characters. For example, the name of the computer resembles the following name:

    Workstation-1

  • You specify a case-sensitive collation setting for the SQL Server service when you install SQL Server 2005.

Note In some cases, this problem may occur if the name of the computer contains some special characters. For example, this problem may occur if the name of the computer contains some characters in Turkish.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions
File name File version File size Date Time Platform
Update.mum Not Applicable 3,195 20-Mar-2007 01:24 Not Applicable
X86_70ff42da86d723f67a3f3a1411ddf687_31bf3856ad364e35_6.0.6000.20560_none_e17f2a45666acde1.manifest Not Applicable 725 20-Mar-2007 01:24 Not Applicable
X86_7e706e7fa6f9cb7ac9e0efb16a9500db_31bf3856ad364e35_6.0.6000.20560_none_afaa4884915dfbea.manifest Not Applicable 725 20-Mar-2007 01:24 Not Applicable
X86_91f11115ca1bbc0ccb9db5ad2b9e733e_31bf3856ad364e35_6.0.6000.20560_none_669c115aeb3b43e8.manifest Not Applicable 725 20-Mar-2007 01:24 Not Applicable
X86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.0.6000.20560_none_0a84b2fb0e7427fe.manifest Not Applicable 4,537 20-Mar-2007 01:27 Not Applicable
X86_microsoft-windows-a..ence-mitigations-c2_31bf3856ad364e35_6.0.6000.20560_none_0a85b3450e734155.manifest Not Applicable 3,540 20-Mar-2007 01:27 Not Applicable
X86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_6.0.6000.20560_none_0a87b3d90e717403.manifest Not Applicable 9,999 20-Mar-2007 01:27 Not Applicable
Acres.dll 6.0.6000.20560 2,560 18-Mar-2007 20:55 x86
Sysmain.sdb Not Applicable 3,203,652 18-Mar-2007 20:07 Not Applicable
Msimain.sdb Not Applicable 1,545,328 18-Mar-2007 20:07 Not Applicable
Acspecfc.dll 6.0.6000.20560 449,536 18-Mar-2007 23:26 x86
Windows Vista, 64-bit versions
File name File version File size Date Time Platform
Amd64_2140efa18e94f1269e0ad3a59f4becac_31bf3856ad364e35_6.0.6000.20560_none_49030b48e61a592a.manifest Not Applicable 1,100 20-Mar-2007 01:24 Not Applicable
Amd64_60e64020e67d0c34a5ac2bd955ab1682_31bf3856ad364e35_6.0.6000.20560_none_de1de1020fe7553c.manifest Not Applicable 1,098 20-Mar-2007 01:24 Not Applicable
Amd64_c74321cbbee835f448ea76ca0b3a6482_31bf3856ad364e35_6.0.6000.20560_none_f913af93c7080ecc.manifest Not Applicable 729 20-Mar-2007 01:24 Not Applicable
Amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.0.6000.20560_none_66a34e7ec6d19934.manifest Not Applicable 3,557 20-Mar-2007 01:31 Not Applicable
Amd64_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_6.0.6000.20560_none_66a64f5cc6cee539.manifest Not Applicable 4,684 20-Mar-2007 01:31 Not Applicable
Update.mum Not Applicable 3,701 20-Mar-2007 01:24 Not Applicable
Wow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.0.6000.20560_none_70f7f8d0fb325b2f.manifest Not Applicable 4,460 20-Mar-2007 01:31 Not Applicable
Wow64_microsoft-windows-a..ence-mitigations-c2_31bf3856ad364e35_6.0.6000.20560_none_70f8f91afb317486.manifest Not Applicable 3,463 20-Mar-2007 01:31 Not Applicable
X86_microsoft-windows-a..ence-mitigations-c4_31bf3856ad364e35_6.0.6000.20560_none_0a87b3d90e717403.manifest Not Applicable 9,999 20-Mar-2007 01:31 Not Applicable
Sysmain.sdb Not Applicable 41,730 18-Mar-2007 20:08 Not Applicable
Acspecfc.dll 6.0.6000.20560 88,064 19-Mar-2007 00:41 x64
Acres.dll 6.0.6000.20560 2,560 18-Mar-2007 20:55 x86
Sysmain.sdb Not Applicable 3,203,652 18-Mar-2007 20:07 Not Applicable
Msimain.sdb Not Applicable 1,545,328 18-Mar-2007 20:07 Not Applicable
Acspecfc.dll 6.0.6000.20560 449,536 18-Mar-2007 23:26 x86


WORKAROUND

To work around this problem, use one of the following techniques:

  • Change the name of the computer to consist of only uppercase characters.
  • Specify a case-insensitive collation setting for the SQL Server service when you install SQL Server 2005. For more information about how to change the default collation setting for the SQL Server service, visit the following Microsoft Developer Network (MSDN) Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

929105 Error message when you install SQL Server 2005 Express Edition Service Pack 1 in Windows Vista: "Windows NT user or group '<COMPUTERNAME>\SQLServer2005MSSQLUser$ <COMPUTERNAME> $MSSQLSERVER' not found"


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005setup KB932593