MS SQL 7.0 Installation Problem?

[Paul Massey]

Hello,

We've been trying for more than a few days to get MS SQL 7 up and running on a
dual processor. So far we've tried quite a few approaches (including uninstalling &
cleaning up the registry, changing permissions to using administator).

Our first problem was that the server refused so install (always failing with the
very helpful message - "an error occured while trying to start the service (5)".
This was we thought something to do with permissions - but we are doing
everything as administrator and have checked everywhere we can thing of.

The last thing was to try starting the server using ' net start mssqlserver'.
(following a setup /t RegistryRebuild = On which seemed to work ok).
It failed but produced the error log:

1999-01-22 19:28:12.98 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 on Windows NT 4.0 (Build 1381: Service Pack 4)

1999-01-22 19:28:12.98 kernel Copyright (C) 1988-1997 Microsoft Corporation.
1999-01-22 19:28:12.98 kernel All rights reserved.
1999-01-22 19:28:12.98 kernel Logging SQL Server messages in file 'd:mssoftsql7logERRORLOG'.
1999-01-22 19:28:12.99 kernel initconfig: Number of user connections limited to 32767.
1999-01-22 19:28:12.99 kernel SQL Server is starting at priority class 'normal'(2 CPUs detected).
1999-01-22 19:28:13.01 kernel User Mode Scheduler configured for thread processing
1999-01-22 19:28:15.01 server Directory Size: 21627
1999-01-22 19:28:15.03 spid1 Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
1999-01-22 19:28:15.03 kernel Attempting to initialize Distributed Transaction Coordinator.
1999-01-22 19:28:15.04 spid1 Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
1999-01-22 19:28:15.04 spid1 Starting up database 'master'.
1999-01-22 19:28:15.04 spid1 Opening file d:mssoftsql7datamaster.mdf.
1999-01-22 19:28:15.07 spid1 Opening file d:mssoftsql7datamastlog.ldf.
1999-01-22 19:28:15.12 spid1 Loading SQL Server's Unicode collation.
1999-01-22 19:28:15.15 spid1 Loading SQL Server's non-Unicode sort order and character set.
1999-01-22 19:28:15.23 spid1 Starting up database 'model'.
1999-01-22 19:28:15.23 spid1 Opening file c:mssql7datamodel.mdf.
1999-01-22 19:28:15.23 kernel udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device c:mssql7datamodel.mdf.
1999-01-22 19:28:15.23 kernel FCB::Open failed: Could not open device c:mssql7datamodel.mdf for virtual device number (VDN) 1.
1999-01-22 19:28:15.24 spid1 Device activation error. The physical file name 'c:mssql7datamodel.mdf' may be incorrect.
1999-01-22 19:28:15.24 spid1 Database 'model' cannot be opened because some of the files could not be activated.

which seems to indicate that it's looking on drive C: for the data files, when we
have evertime installed it on D: (our C: driver being full). The registry contains
no references that we found to C:mssql7, but some of the installed files (on D
do have this string in them ? Do we have to install in C:mssql7 ?

Any other suggestions ?

Many Thanks,

Paul Massey.

[Kevin Napier]

I have successfully installed SQL Server 7.0 on the D: drive using both NT Server 4.0 and NT Workstation 4.0. However, when prompted to change the instal directory I only changed the C: to D:, I did not change the default directory (i.e. d:MSSQL7). I notice that you have changed the instal directory to d:mssoftsql7, it's a longshot but how about reinstalling using the default directory (i.e. just edit the C: to D.

Good Luck.

Kevin

On 1/25/99 4:39:14 AM, Paul Massey wrote:
> Hello,

We've been trying for more than a few days to get MS SQL 7 up
> and running on a
dual processor. So far we've tried quite a few
> approaches (including uninstalling &
cleaning up the registry, changing
> permissions to using administator).

Our first problem was that the
> server refused so install (always failing with the
very helpful message -
> "an error occured while trying to start the service (5)".
This was
> we thought something to do with permissions - but we are doing
everything
> as administrator and have checked everywhere we can thing of.

The last
> thing was to try starting the server using ' net start
> mssqlserver'.
(following a setup /t RegistryRebuild = On which seemed
> to work ok).
It failed but produced the error log:

1999-01-22
> 19:28:12.98 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 on Windows NT 4.0 (Build 1381: Service Pack
> 4)

1999-01-22 19:28:12.98 kernel Copyright (C) 1988-1997 Microsoft
> Corporation.
1999-01-22 19:28:12.98 kernel All rights
> reserved.
1999-01-22 19:28:12.98 kernel Logging SQL Server messages in
> file 'd:mssoftsql7logERRORLOG'.
1999-01-22 19:28:12.99 kernel
> initconfig: Number of user connections limited to 32767.
1999-01-22
> 19:28:12.99 kernel SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
1999-01-22 19:28:13.01 kernel User
> Mode Scheduler configured for thread processing
1999-01-22 19:28:15.01
> server Directory Size: 21627
1999-01-22 19:28:15.03 spid1 Using
> dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner
> Blocks
1999-01-22 19:28:15.03 kernel Attempting to initialize
> Distributed Transaction Coordinator.
1999-01-22 19:28:15.04 spid1
> Failed to obtain TransactionDispenserInterface:
> XACT_E_TMNOTAVAILABLE
1999-01-22 19:28:15.04 spid1 Starting up database
> 'master'.
1999-01-22 19:28:15.04 spid1 Opening file
> d:mssoftsql7datamaster.mdf.
1999-01-22 19:28:15.07 spid1 Opening
> file d:mssoftsql7datamastlog.ldf.
1999-01-22 19:28:15.12 spid1
> Loading SQL Server's Unicode collation.
1999-01-22 19:28:15.15 spid1
> Loading SQL Server's non-Unicode sort order and character
> set.
1999-01-22 19:28:15.23 spid1 Starting up database
> 'model'.
1999-01-22 19:28:15.23 spid1 Opening file
> c:mssql7datamodel.mdf.
1999-01-22 19:28:15.23 kernel udopen:
> Operating system error 3(The system cannot find the path specified.) during
> the creation/opening of physical device
> c:mssql7datamodel.mdf.
1999-01-22 19:28:15.23 kernel FCB::Open
> failed: Could not open device c:mssql7datamodel.mdf for virtual device
> number (VDN) 1.
1999-01-22 19:28:15.24 spid1 Device activation error.
> The physical file name 'c:mssql7datamodel.mdf' may be
> incorrect.
1999-01-22 19:28:15.24 spid1 Database 'model' cannot
> be opened because some of the files could not be activated.

which seems
> to indicate that it's looking on drive C: for the data files, when we
>
have evertime installed it on D: (our C: driver being full). The registry
> contains
no references that we found to C:mssql7, but some of the
> installed files (on D
do have this string in them ? Do we have to
> install in C:mssql7 ?

Any other suggestions ?

Many Thanks,

Paul Massey.