Can't start the MSSQLServer Service

I just got a new laptop for work, and our local IT/Hardware guy used
PCMover from Laplink to migrate the apps and settings from my old
machine to this new one. I was skeptical, but it's actually worked
quite well, the biggest issue that I'm having is getting SQL Server to
run on the new machine.
Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
After the migration, I did have to recreate the services for the
server and agent (those services weren't migrated):
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlservr.exe"
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
\MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
If I don't include the SQL Server dependency on the SQL Agent, then
the Agent starts just fine. When I try to start the SQL Server
service, it displays a dialog error:
The MSSQLServer service on Local Computer started and then stopped.
Some Services stop automatically if they have no work to do, for
example, the Performance Logs and Alerts service.
Here's the contents of the server log:
2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-08 10:38:58.14 server All rights reserved.
2007-02-08 10:38:58.14 server Server Process ID is 5860.
2007-02-08 10:38:58.14 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-08 10:38:58.17 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-02-08 10:38:58.84 server SQL Server configured for thread mode
processing.
2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000] Lock Owner Blocks.
2007-02-08 10:38:58.87 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-08 10:38:58.89 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
shutting down.
2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
The failure to obtain TransactionDispenserInterface message was
occurring on the old machine, so I conclude that isn't part of the
issue.
The Server Network Utility does show TCP/IP as the only protocol
enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
listed and that dll is residing in the expected location (C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
The service properties page page Log On tab shows the Local System
Account to be used for logon.
So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
and re-installing SQL Server, how can I get my SQL Server back up and
running?
Thanks in advance
Mark>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical,
And you should have been. The errorlog clearly states that SQL Server cannot
load any netlibs, so it
refuses to start. I.e., the installation isn't OK...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mark.a.lemoine@.gmail.com> wrote in message
news:1170950095.972400.293760@.s48g2000cws.googlegroups.com...
>I just got a new laptop for work, and our local IT/Hardware guy used
> PCMover from Laplink to migrate the apps and settings from my old
> machine to this new one. I was skeptical, but it's actually worked
> quite well, the biggest issue that I'm having is getting SQL Server to
> run on the new machine.
> Using SQL Server 2000. Both laptops are Windows XP Pro SP2.
> After the migration, I did have to recreate the services for the
> server and agent (those services weren't migrated):
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service MSSQLServer -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlservr.exe"
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\scm.exe -action 5 -
> service SQLSERVERAGENT -exepath "c:\Program Files\Microsoft SQL Server
> \MSSQL\Binn\sqlagent.exe" -dependencies MSSQLServer
> If I don't include the SQL Server dependency on the SQL Agent, then
> the Agent starts just fine. When I try to start the SQL Server
> service, it displays a dialog error:
> The MSSQLServer service on Local Computer started and then stopped.
> Some Services stop automatically if they have no work to do, for
> example, the Performance Logs and Alerts service.
> Here's the contents of the server log:
> 2007-02-08 10:38:58.14 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
> 2007-02-08 10:38:58.14 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-08 10:38:58.14 server All rights reserved.
> 2007-02-08 10:38:58.14 server Server Process ID is 5860.
> 2007-02-08 10:38:58.14 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-08 10:38:58.17 server SQL Server is starting at priority
> class 'normal'(2 CPUs detected).
> 2007-02-08 10:38:58.84 server SQL Server configured for thread mode
> processing.
> 2007-02-08 10:38:58.84 server Using dynamic lock allocation. [2500]
> Lock Blocks, [5000] Lock Owner Blocks.
> 2007-02-08 10:38:58.87 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-08 10:38:58.89 server Failed to obtain
> TransactionDispenserInterface: Result Code = 0x8004d01b
> 2007-02-08 10:38:58.89 server Unable to load any NETLIBs. Server
> shutting down.
> 2007-02-08 10:38:58.89 spid4 Starting up database 'master'.
> The failure to obtain TransactionDispenserInterface message was
> occurring on the old machine, so I conclude that isn't part of the
> issue.
> The Server Network Utility does show TCP/IP as the only protocol
> enabled. The Network Libraries tab does show the TCP/IP SSNETLIB.DLL
> listed and that dll is residing in the expected location (C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> The service properties page page Log On tab shows the Local System
> Account to be used for logon.
> So, I'm figuring it can't find ssnetlib.dll. Short of uninstalling
> and re-installing SQL Server, how can I get my SQL Server back up and
> running?
> Thanks in advance
> Mark
>