FIX: Installation fails when Windows computer name is mixed or lowercase (285100)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
  • Microsoft SQL Server 2000 Desktop Engine (MSDE)
This article was previously published under Q285100
BUG #: 351711(SQL2000)

SYMPTOMS

Connection attempts over the shared memory network library fail on a server where GetComputerName returns a lower or mixed case server name.

When the shared memory connection attempt fails the SQL Server 2000 network library attempts to connect over an alternate protocol.

When you install any edition of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) on a computer whose name is all lowercase or mixed case, Setup may fail, and you receive one of the following messages:

For MSDE 2000:
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
For SQL Server 2000:
Setup failed to configure the server. Refer to the server error logs and sqlstp.log for more information.

CAUSE

GetComputerName is used to obtain the local computer name. The client network library component (DBMSLPCn.dll) converts the name to all upper case. The server network library component (SSMSLPCn.dll) leaves the name as returned.

RESOLUTION

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

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later: 
   File name     Platform
   ----------------------

   SSMSLPCn.dll   Intel
   SSMSLPCn.pdb   Intel
The following file is available for download from the Microsoft Download Center:

SSMSLPCn323.exe


Release Date: JAN-22-2001

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How To Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

The SSMSLPCn323.exe file contains the following files:

File nameSize
EULA.txt2 KB
Readme.txt1 KB
SSmsLPCn.dll29 KB
SSmsLPCn.pdb73 KB

Note If this is a new installation of SQL Server, you do not have a C:\Program Files\Microsoft SQL Server\MSSQL\Binn folder where you can copy this file.To apply this hotfix, copy the contents of the SQL Server installation CD to your hard drive, and then replace the existing version of the file on your hard disk drive with the new hotfixed version of the file. After you do this, install the hotfix from the hard disk drive.

For more information, see the Readme.txt file that is included with the hotfix.
Note Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

WORKAROUND

To work around this problem, change the computer name to all uppercase characters.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

The failure is prohibitive to a SQL Server 2000 setup. A SQL Server 2000 setup prevents external connections by only allowing the shared network library connections.

If a shared memory connection can not be established, the setup fails when it attempts to configure the SQL Server server.

For SQL Server 2000:

The Sqlstp.log file contains an error message similar to:
2:44:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -dbdebug -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 262404 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=master [Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
In the same Sqlstp.log file you can verify the naming failure by locating the following at the top of the log file: 
   12:30:08 Name = MYSERVER, Type = 0x1
   12:30:08 ComputerName: MyServer
For MSDE 2000:

Run the following command so the installation does not roll back upon failure: 
setup.exe /DISABLEROLLBACK=1 /L*v C:\temp\msdesetup.log
You must run this code so that the Cnfgsvr.out file can be collected. Using the /L*v switch enables verbose logging for MSDE 2000 Setup.

After the MSDE 2000 installation fails, when you review the contents of the Cnfgsvr.out file, you see an error message similar to the following:
Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=MyServer;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
The naming failure can be located from the server parameter. The Msdesetup.log file has an entry similar to the following: 
ComputerName =MyServer
Modification Type:MinorLast Reviewed:10/7/2005
Keywords:kbHotfixServer kbQFE kbdownload kbdownload kbBug kbfix kbQFE KB285100 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.