Results 1 to 6 of 6
  1. #1
    Join Date
    May 2003
    Posts
    3

    Question Unanswered: Problems installing SQL7 Desktop on WinXP

    I am having great difficulty installing SQL Server 7 Desktop Edition onto WinXP

    Pro. The installation proceeds without error until an attempt is made to
    configure and then connect to SQL Server, at which point the installation fails and all installed components are removed from the PC. I have tried to install on repeated occasions, always with the same result.

    I would be very grateful for any help in solving this problem.

    The contents of the CNFGSVR.OUT and ERRORLOG are as below:

    CNFGSVR.OUT
    ===========

    Starting Service ...

    Connecting to Server ...

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

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

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

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

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

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

    driver={sql server};server=DAVIS;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()).

    SQL Server configuration failed.


    ERRORLOG
    ========

    2003-05-25 23:32:19.09 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
    Nov 27 1998 22:20:07
    Copyright (c) 1988-1998 Microsoft Corporation
    Desktop Edition on Windows NT 5.1 (Build 2600: Service Pack 1)

    2003-05-25 23:32:19.09 kernel Copyright (C) 1988-1997 MicrosoftCorporation.
    2003-05-25 23:32:19.09 kernel All rights reserved.
    2003-05-25 23:32:19.09 kernel Logging SQL Server messages in file
    'C:\MSSQL7\log\ERRORLOG'.
    2003-05-25 23:32:19.12 kernel initconfig: Number of user connections limited to 32767.
    2003-05-25 23:32:19.12 kernel SQL Server is starting at priority class
    'normal'(1 CPU detected).
    2003-05-25 23:32:19.12 kernel User Mode Scheduler configured for thread processing
    2003-05-25 23:32:20.17 server Directory Size: 21633
    2003-05-25 23:32:20.18 spid1 Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks
    2003-05-25 23:32:20.18 spid1 Warning ******************
    2003-05-25 23:32:20.18 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
    2003-05-25 23:32:20.18 spid1 Warning ******************
    2003-05-25 23:32:20.18 spid1 Recovering only master database
    2003-05-25 23:32:20.18 spid1 Starting up database 'master'.
    2003-05-25 23:32:20.18 spid1 Opening file C:\MSSQL7\data\master.mdf.
    2003-05-25 23:32:20.20 spid1 Opening file C:\MSSQL7\data\mastlog.ldf.
    2003-05-25 23:32:20.26 spid1 Loading SQL Server's Unicode collation.
    2003-05-25 23:32:20.28 spid1 Loading SQL Server's non-Unicode sort order and character set.
    2003-05-25 23:32:20.40 spid1 4 transactions rolled forward in database 'master' (1).
    2003-05-25 23:32:20.40 spid1 0 transactions rolled back in database 'master' (1).
    2003-05-25 23:32:20.58 spid1 Server is unnamed.
    2003-05-25 23:32:20.58 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
    2003-05-25 23:32:20.58 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
    2003-05-25 23:32:20.59 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
    2003-05-25 23:32:20.59 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '1433'.
    2003-05-25 23:32:21.09 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen on 'DAVIS'.
    2003-05-25 23:32:21.19 spid1 SQL Server's Unicode collation is:
    2003-05-25 23:32:21.19 spid1 'English' (ID = 1033).
    2003-05-25 23:32:21.19 spid1 comparison style = 196609.
    2003-05-25 23:32:21.19 spid1 SQL Server's non-Unicode sort order is:
    2003-05-25 23:32:21.19 spid1 'nocase_iso' (ID = 52).
    2003-05-25 23:32:21.19 spid1 SQL Server's non-Unicode character set is:
    2003-05-25 23:32:21.19 spid1 'iso_1' (ID = 1).
    2003-05-25 23:32:21.20 kernel Warning: override, autoexec procedures skipped.
    2003-05-25 23:32:35.88 kernel SQL Server is terminating due to 'stop' request from Service Control Manager.

  2. #2
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Try downloading latest MDAC from MS Data and reinstall again.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  3. #3
    Join Date
    May 2003
    Posts
    3
    Satya,

    I have already downloaded MDAC 2.7 but the install still fails.

    It's probably not relevant but if I run Component Checker against version "2.7 SP1(WinXP)" the utility reports the following anomalies:

    HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSDASC\Default Icon
    Registry
    Field 'Value' mismatch: Expect 'C:\Program Files\Common Files\System\Ole DB\oledb32.dll^0' Got 'C:\WINDOWS\System32\migicons.exe^101'
    Error

    MSADCO.DLL
    COM
    Unknown Class ID = {9381d8f1-0288-11d0-9501-00aa00b911a5}
    Warning

    MSDATT.DLL
    COM
    Unknown Class ID = {c8b522ce-5cf3-11ce-ade5-00aa0044773d}
    Warning

  4. #4
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Refer to dasetup.log files in the windows directory that might shed some light on the problem. You can log MDAC installation by using \MDACSetup\Setup.exe /gc C:\MdacInstalllog.txt

    If no avail then make sure those 2 DLLs got registered properly on XP, try reinstall XP with all available SPs.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  5. #5
    Join Date
    May 2003
    Posts
    3
    Any ideas how I can stop the install removing all components on failure? If I could stop the components being removed I might be able to try starting and configuring the service by hand.

  6. #6
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Remove all reference registry keys and delete the directories during the installation.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •