Installing SQL 2000 - Stuck in the mud!

  • I am installing SQL 2000 as named instance on a box that is already running 7.0. The install seems to run fine until the very end when it restarts the service, then I get an error (posted below).

    Thanks. -Matt


    Connecting to Server ...

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

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

    [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionRead (recv()).

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

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

    [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionRead (recv()).

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

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

    [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionRead (recv()).

    SQL Server configuration failed.


    13:45:22 Process Exit Code: (-1)

    13:58:53 Setup failed to configure the server. Refer to the server error logs and C:\WINNT\sqlstp.log for more information.

    13:58:56 Action CleanUpInstall:

    13:58:56 C:\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service SQLAgent$SQL2000

    13:58:56 Process Exit Code: (1060) The specified service does not exist as an installed service.

    13:58:56 C:\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service MSSQL$SQL2000

    13:58:56 Process Exit Code: (0)

    13:58:56 StatsGenerate returned: 2

    13:58:56 StatsGenerate (0x227,0x1,0xf0000000,0x600,1033,303,0x0,0x1,0,0,0

    13:58:56 StatsGenerate -1,SQL2000_dev)

    13:58:56 Installation Failed.

  • Do you have a service names MSSQL$SQL2000?

    Might try re-running setup, also, I hate names like this because there might be something reserved. Can you makeup some other instance name?

    Steve Jones

  • no new SQL services were installed. It looks setup removed them when the install went bad. I'll try a different instance name, but I have used this convention on another box without issue.

    Thanks again.

  • Let us know if it works and the outcome.

    Steve Jones

  • I have to bounce the server before it will let me run setup again. That will have to wait until tonight... I'll give you an update.

  • I had the same problem, still do as a matter of fact. I rec'd the same error and MS Support returned the following. Did not fix my problem. Maybe you'll have better luck

    "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."

    More info on Microsoft support Doc Q285100


  • Karen - thanks for the info... did you apply the fix? If so, what was the result?

    File name Size

    EULA.txt 2 KB

    Readme.txt 1 KB

    SSmsLPCn.dll 29 KB

    SSmsLPCn.pdb 73 KB

  • I did apply the fix but it did not help me. I thought it would because my computer name has small and upper case letters along with a dash - I still haven't been able to install SQL 2000 to my home system. I will be watching this thread to see how your problem gets solved.

    The other night I found an article by one of our forum hosts, sorry not sure which one of you bright gentlemen wrote it, that I am going to try tonight.

    Good Luck!

  • Can you post the entire contents of C:\WINNT\sqlstp.log?

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • Here's Microsoft's FAQ on SQL Server 2000 setup.;en-us;Q257716

    One thing that stood out is the possiblity of an issue of MDAC install failure. If MDAC 2.6 didn't install clean, it might explain the issue since MDAC 2.5 doesn't support named instances. I'm reaching here, but the article does indicate a file to look at to see if there was an error.

    Also, if all else fails and it won't let you install the second time around, here's the one on how to manually uninstall. I've had to use it once myself.;en-us;Q290991

    K. Brian Kelley

    K. Brian Kelley

  • Karen - I'll keep you updated

    Brian - The MDAC thing sounds like a possibilty. I'll follow the links and hope for the best.

    Antares686 - Here is all of the sqlstp.log

    14:42:22 Begin Setup

    14:42:22 8.00.194

    14:42:22 Mode = Normal

    14:42:22 ModeType = NORMAL

    14:42:22 GetDefinitionEx returned: 0, Extended: 0xf00000

    14:42:22 ValueFTS returned: 1

    14:42:22 ValuePID returned: 1

    14:42:22 ValueLic returned: 0

    14:42:22 System: Windows NT Server

    14:42:22 SQL Server ProductType: Developer Edition [0x3]

    14:42:22 Begin Action: SetupInitialize

    14:42:22 End Action SetupInitialize

    14:42:22 Begin Action: SetupInstall

    14:42:22 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ...

    14:42:22 CommonFilesDir=C:\Program Files\Common Files

    14:42:22 Windows Directory=C:\WINNT14:42:22 Program Files=C:\Program Files14:42:22 TEMPDIR=C:\TEMP14:42:22 Begin Action: SetupInstall

    14:42:22 Begin Action: CheckFixedRequirements

    14:42:22 Platform ID: 0xf0000000

    14:42:22 Version: 4.0.1381

    14:42:22 NT4 Service Pack: 1536

    14:42:22 File Version - C:\WINNT\System32\shdocvw.dll: 6.0.2712.300

    14:42:22 End Action: CheckFixedRequirements

    14:42:23 Begin Action: ShowDialogs

    14:42:23 Initial Dialog Mask: 0x83000f7, Disable Back=0x1

    14:42:23 Begin Action ShowDialogsHlpr: 0x1

    14:42:23 Begin Action: DialogShowSdWelcome

    14:42:25 End Action DialogShowSdWelcome

    14:42:25 Dialog 0x1 returned: 1

    14:42:25 End Action ShowDialogsHlpr

    14:42:25 ShowDialogsGetDialog returned: nCurrent=0x2,index=1

    14:42:25 Begin Action ShowDialogsHlpr: 0x2

    14:42:25 Begin Action: DialogShowSdMachineName

    14:42:39 ShowDlgMachine returned: -1

    14:42:39 ShowDlgMachine: GetLastError returned: 1223

    14:42:39 The operation was cancelled by the user.

    14:42:39 End Action DialogShowSdMachineName

    14:42:39 End Action ShowDialogs

    14:42:39 Action CleanUpInstall:

    14:42:39 StatsGenerate returned: 2

    14:42:39 StatsGenerate (0x0,0x0,0xf0000000,0x0,1033,0,0x0,0x0,0,0,0

    14:42:39 StatsGenerate -1,)

    14:42:39 Installation Failed.

  • ok... here's the deal. I spoke with MS support today and we were able to solve the issue.

    1. Run SQL2000 setup from the cmd line using 'setupsql.exe k=dbg' (debug mode)

    2. The install will run each step then prompt you to continue or skip the next step.

    3. When setup reaches the point where it says that it will "now configure the server", you need to replace SSmsLPCn.dll in your binn folder.

    4. Once you have copied the new SSmsLPCn.dll, complete the remaining setup steps.

  • Hi,Matt

    I was reading this discussion.. I have a q for U.

    Where do U need to get this SSmsLPCn.dll file?

    Does setup ask U to replace into Ur BINN folder or U need to replace mannually copy from CD or other place(where?) into Ur BINN folder?

    Thx in advance


  • Jay - you can get the files here -;EN-US;q285100.

    There are 2 files, a .dll and .pdb. They need to go into your binn directory after the files have been copied from the CD and prior to setup configuring the server.

    "setupsql.exe k=dbg" will allow you to step through setup.

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply