Very Computer

> Hello all, I have been trying to install SQL Server 7 (Eval from MS SQL
> Server 7.0 Implementation Training Kit) on our NT 4 TSE SP5 box but run
> into a snag just before completion. Prior to the install I used HandleEx
> to find and shut down all ODBC using services and then started the
> install. I've also set up a separate user account for it. It continues
> through the dialogs and starts the install process but when it gets to
> the 'Setup is installing the Microsoft Data Access Component' dialog it
> pops up with the following:

> Unable to configure ODBC driver Microsoft Excel Driver (*.xls)
> Could not load the setup or translator library

> If I click OK I get this one:

> Unable to configure ODBC driver Microsoft dBase Driver (*.dbf)
> Could not load the setup or translator library

> And again when I click OK:

> Unable to configure ODBC driver Microsoft Paradox Driver (*.db)
> Could not load the setup or translator library

> clicking OK it continues:

> Starting Service ...
> Remapping Server Databases ...
> SQL Server Database(? didn't catch all of this one)

> And then this pops up:

> Setup failed to configure the server. Refer to the server error logs and
> cnfgsvr.out for more information.

> Lovely eh? So I check the files:

> - - error.log:
> 2000-01-14 17:13:51.23 kernel   Microsoft SQL Server  7.00 - 7.00.623
> (Intel X86)
>  Nov 27 1998 22:20:07
>  Copyright (c) 1988-1998 Microsoft Corporation
>  Standard Edition Evaluation on Windows NT 4.0 (Build 1381: Service Pack
> 5)

> 2000-01-14 17:13:51.31 kernel   Copyright (C) 1988-1997 Microsoft
> Corporation.
> 2000-01-14 17:13:51.31 kernel   All rights reserved.
> 2000-01-14 17:13:51.31 kernel   Logging SQL Server messages in file
> 'C:\MSSQL7\log\ERRORLOG'.
> 2000-01-14 17:13:51.40 kernel   initconfig: Number of user connections
> limited to 32767.
> 2000-01-14 17:13:51.40 kernel   SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2000-01-14 17:13:51.46 kernel   User Mode Scheduler configured for
> thread processing
> 2000-01-14 17:13:53.64 server   Directory Size: 21627
> 2000-01-14 17:13:53.68 spid1    Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks
> 2000-01-14 17:13:53.68 kernel   Attempting to initialize Distributed
> Transaction Coordinator.
> 2000-01-14 17:13:53.73 spid1    Failed to obtain
> TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2000-01-14 17:13:53.74 spid1    Warning ******************
> 2000-01-14 17:13:53.74 spid1    SQL Server started in single user mode.
> Updates allowed to system catalogs.
> 2000-01-14 17:13:53.74 spid1    Warning ******************
> 2000-01-14 17:13:53.74 spid1    Recovering only master database
> 2000-01-14 17:13:53.74 spid1    Starting up database 'master'.
> 2000-01-14 17:13:53.74 spid1    Opening file C:\MSSQL7\data\master.mdf.
> 2000-01-14 17:13:53.76 spid1    Opening file C:\MSSQL7\data\mastlog.ldf.

> 2000-01-14 17:13:53.82 spid1    Loading SQL Server's  Unicode collation.

> 2000-01-14 17:13:53.87 spid1    Loading SQL Server's  non-Unicode sort
> order and character set.
> 2000-01-14 17:13:54.04 spid1    4 transactions rolled forward in
> database 'master' (1).
> 2000-01-14 17:13:54.06 spid1    0 transactions rolled back in database
> 'master' (1).
> 2000-01-14 17:13:54.28 spid1    Server is unnamed.
> 2000-01-14 17:13:54.28 kernel   Using 'SQLEVN70.DLL' version '7.00.623'.

> 2000-01-14 17:13:54.28 kernel   Using 'OPENDS60.DLL' version
> '7.00.00.0623'.
> 2000-01-14 17:13:54.32 ods      Using 'SSNMPN70.DLL' version '7.0.623'
> to listen on '\\.\pipe\sql\query'.
> 2000-01-14 17:13:54.32 ods      Using 'SSMSSO70.DLL' version '7.0.623'
> to listen on '1433'.
> 2000-01-14 17:13:54.32 ods      Using 'SSMSRP70.DLL' version '7.0.623'
> to listen on '<hostname>'.
> 2000-01-14 17:13:54.51 spid1    SQL Server's Unicode collation is:
> 2000-01-14 17:13:54.51 spid1            'English' (ID = 1033).
> 2000-01-14 17:13:54.51 spid1            comparison style = 196609.
> 2000-01-14 17:13:54.51 spid1    SQL Server's non-Unicode sort order is:
> 2000-01-14 17:13:54.51 spid1            'nocase_iso' (ID = 52).
> 2000-01-14 17:13:54.51 spid1    SQL Server's non-Unicode character set
> is:
> 2000-01-14 17:13:54.51 spid1            'iso_1' (ID = 1).
> 2000-01-14 17:13:54.56 kernel   Warning: override, autoexec procedures
> skipped.
> 2000-01-14 17:14:07.17 kernel   SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> - -

> - - cnfgsvr.out:
> Starting Service ...

> Connecting to Server ...

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

> Remapping Server Databases ...

> [Microsoft][ODBC Driver Manager] Driver does not support this function

> SQL Server configuration failed.
> - -

> And then I found the following in the Event Log:

> Event ID: 1001
> Source: SQLCTR70
> Type: Error
> Category: None

> The description for Event ID ( 1001 ) in Source ( SQLCTR70 ) could not
> be found. It contains the following insertion string(s): Cannot open the
> Registry Key..

> Um, WHAT registry key???  I used RegMon and grabbed the calls during
> another install attempt but I couldn't see anything that grabbed my
> attention. Not that I'm a Registry expert or anything. :P  You can grab
> an edited copy at http://drvids.dyndns.org/SQL-Install.log if you wanna
> take a look. WARNING: it's over 37000 lines and almost 4MB. I removed
> the  \Terminal Sever\Compatability  lines and any non-install program
> lines as well as the line number & time columns to try and condense it..

> Can anyone tell me what is going on here and/or what I'm missing/doing
> wrong?

> Thanx,
> David