Microsoft KB Archive/39940

From BetaArchive Wiki

SQL Setup Program Fails While Checking Network Configuration PSS ID Number: Q39940 Article last modified on 12-18-1992




Why does the SQL Server Setup program fail with a message saying that IPC$ is not shared, the server is password protected, or the SQL Server is already running?

IPC$ is shared, SQL Server is not running, the LAN Manager user ADMIN is permitted to use share name “”, and a NET LOGON for ADMIN has been issued.


The configuration check attempts to create and use a named pipe. If that attempt fails for any reason, the “This computer is not properly configured” message appears. If the versions of OS/2 and LAN Manager supplied with the NDK are used, the three reasons listed are the most common reasons. If other versions of OS/2 or LAN Manager are used, there could be many other reasons why named pipes are not working.

Do not use the ADMIN account for the SQL Server installation if LAN Manager has been set up with user-level security. Instead, use NET ADMIN to create another LAN Manager user account in the USERS* group. The USERS* group is already permitted to use “”, so it is not necessary to explicitly give permission to use “” to a user added to this group. After the user account is created, NET LOGOFF from ADMIN and NET LOGON to the newly created user account. If the user was created with a password, you must either specify userid and password on the NET LOGON command or leave both out. If you specify just the userid on the NET LOGON command, you will not be prompted for a password, and you will not be able to use named pipes.

If you still have difficulty, try turning off user-level security in LAN Manager until the installation is completed. Change the “SECURITY=USER” parameter in .INI to “SECURITY=SHARE”, do a NET STOP RDR /Y, and do a NET START SERVER. If you deactivate user-level security, you must explicitly share IPC$ every time the LAN Manager server is started: NET SHARE IPC$.

There are two programs on the first SQL Server installation disk called MAKEPIPE and READPIPE. These programs can be executed to determine why named pipes are not working.

  1. Run MAKEPIPE on the server computer.
  2. Specify a pipe name of “” (do NOT specify the server name when making a pipe). If the MAKEPIPE is successful, it will wait for a client to connect.
  3. Switch to another screen group and run READPIPE.
  4. Specify the same pipe name, but with the server’s computer name prefixed to it. i.e., “\MYSERVER”. If it connects, MAKEPIPE will prompt for data, which will be sent to READPIPE and echoed to the screen. A null line terminates MAKEPIPE and READPIPE, or they can just be canceled with CTRL+C.

Copyright Microsoft Corporation 1992.