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
>sql

Can't register SQL-DMO

Hi, this is an old issue and i've searched for days. I have a vb6 app thats
worked for years on a NT4/SQL7 server using the SQL7 client. We are finally
moving out of mixed mode and upgraded the server to NT2003/SQL 2000.
I upgraded and re-compiled the vb program and installed it on the users PC,
along with the sql2000 client. I would get an error connecting to the sql
2000 server. [Microsoft][ODBC SQL Server Drver][SQL Server]You must upgrade
your SQL Enterprise Manager and SQL-DMO(SQL OLE) to SQL 2000 (SQLDMO) to
connect to this server. Error Code -2147220990
After much research I found that I needed to install/register the SQL-DMO
and found a article (326613) from Microsoft on how to create a distribution
package.
I followed the instructions and the sql-dmo package worked fine, ON some
machines (XP), but I've found that many NT2000 PC's it simply won't install
and register on. It will come back with a HResult -2147024770 failed to
register sqldmo.dll
I've got all the files in the right place, with the .rll files where they
need to be. I can't even manually register the sqldmo.dll file on these
PC's.. The really strange part is if I install the full sql2000 server onto
the PC then the program runs fine. BUT, as soon as I uninstall the server
portion it fails again. I've tried installing both the SQL-2000 client and
client tools but nothing works short of a full SQL server install, Which is
not an option!
The PC's in question are all Compaq/HP EVO's running NT2000, standard fair
stuff, nothing strange on the desktop. All have the lastest updates, patches
and hotfixes.
I know this is an old issue, But does anybody have a clue? I'd hate to
tell my boss that those folks can't run the program unless they upgrade there
PC.
Im not sure if my dev system has service pack 4 or not, I'll have to check.
As far as being compiled with the newest MSVc++ runtime linked
lib,"msvcr71.dll I am using .net 2002 so I guess not. Strange that the
microsoft article (326613) says nothing about this. as far as the rest of
your statement all those files are included and in their correct directory
structure, Per the article I used to create the distribution package.
"Andrea Montanari" wrote:

> hi,
> jcw wrote:
> what files are you "redistributing" in order to install SQL-DMO 2000?
> In my experience, I never failed providing
> ;SQL Server service pack 4 SQL-DMO object has been compiled with the newest
> Microsoft Visual C++ runtime linked library, msvcr71.dll that must be
> redistributed as well;
> ...\WINDOWS\SYSTEM\msvcr71.dll DestDir: WinSys ; sharedfile
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\WINDOWS\SYSTEM\odbcbcp.dll; DestDir: WinSys ; sharedfile
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\WINDOWS\SYSTEM\sqlwoa.dll ; DestDir: WinSys
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\WINDOWS\SYSTEM\sqlwid.dll ; DestDir: WinSys
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\w95scm.dll; DestDir:
> DestinationFolder\Binn
> ...\WINDOWS\SYSTEM\sqlunirl.dll ; DestDir: WinSys
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlresld.dll; DestDir:
> DestinationFolder\Binn
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlsvc.dll; DestDir:
> DestinationFolder\Binn
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\sqlsvc.RLL;
> DestDir: DestinationFolder\Binn\Resources\1033
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\Sqldmo.rll;
> DestDir: DestinationFolder\Binn\Resources\1033
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll; DestDir:
> DestinationFolder\Binn ; file to be registered via regserver
> DestinationFolder can either be the installation directory of one instance
> of Microsoft SQLServer 2000, like ..\Program Files\Microsoft SQL
> Server\80\Tools, even if no istance of SQL Server has been installed, or the
> installation directory of your application, but the first one is preferred.
> Please do respect the hierarchy \Binn\Resources\1033 (where 1033 specifies
> the language), where needed, in order to grant correct functionality of
> Ole-Automation objects.
> In order to install SQL-DMO components for MSDE 2000, Microsoft Internet
> Explorer 5.5 or higher is required.
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||checked and I did install the SP4.

Cant modify or delete an existing job

Folks, i have rebuilt my old server machine and i've restored the MSDB over the new machine. Now when i try to edit or delete any of the jobs that come from the RESTORE; i get the following error message:

I never setup multiserver administration.
However i can create and delete new jobs.
How do i remove these older jobs.

Howdy!This happened to me once, when a machine was renamed. I think it is as simple as updating the sysjobs table to reflect the new server name (originating_server column). Make sure you have a good backup, before you do this, however.|||sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.

Thanx, MCrowley. I would try this when the users are off the machine.

Howdy.|||My experience was the exact same as MCrowley's; I think I went in and hand-edited the jobs in the msdb database (through EM; it was a long time ago). You may need to set the switch to allow updating of system tables, but I don't recall that I had to do that.

Regards,

hmscott

sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.

Thanx, MCrowley. I would try this when the users are off the machine.

Howdy.|||i am squared. thanx.

USE MASTER
GO
sp_configure 'allow updates' ,1
GO
RECONFIGURE WITH OVERRIDE
GO
USE MSDB
go
update sysjobs set originating_server='myserver'
GO
USE MASTER
GO
sp_configure 'allow updates' ,0
GO
RECONFIGURE WITH OVERRIDE

--HOWDY!|||Just had the same problem on a rebuilt server - the above script sorted it out.

thanks,
Paul.

Cant Keep Primary Key Columns when moving db to SQL 2005 from 2000

there are some primary key columns which are autoincrement in some tables.
for exampl page_id, now we have deleted many pages in old server so there
are many gaps between the page_id
even the it doest start with 1 because during the testing many initial pages
were deleted.

but when we move it to the new server with sql2005 it gives them numbers from 1,2,3 and
so on.

I need to keep existing 2000 keys. How can I acomplish this?

it would have worked if it also updates this number in other tables which
refer to this column
for example page_id is autoincreement in tbl_category_pages ( this table
contains the page information)
and it also appears in tbl_page_content ( this table contains the page's
content)

because it changes this number at one place and not the other place it makes
the database incorrect.

i tried many things ( there is even an option to keep the values of such
columns but doesnt seem to work)

Thanks,

WessTo maintain existing relationships, simply select all tables and copy them to a notepad. From there you just copy and paste them in the query anlyzer.|||If you want tables with relationships and data, take a complete back up of the database. Use that backup file and restore in sql 2005.|||ramasp,

Thanks, I appreciate your help.

I have given this information to the developer I have working on this. He tells me he tried this and that it can not work because the two versions are different.

Please let me know if this should work and the proccess to do so.

Thanks,

Wess

Can't install Express June CTP?!

Hey all, I'm trying to install SQL Server 2005 Express June CTP on a windows 2003 Web Edition Server (With SP1).

I've had an old version of the .NET 2.0 Framework installed, so I downloaded the one mentioned next to the SQL Express download (this one: http://go.microsoft.com/fwlink/?linkid=48448).

Each and every time I run the setup I encounter this error:
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
There is not even any sort of SQL Server service in the list of services, what should I do?
Regards,

Hendrik BehrensI've also tried the same on Windows XP Professional SP2. I had to uninstall a previous version of .NET 2.0 and VWD Express/VB Express Beta 2 are installed.

I get the same error message?! - The service is not there and the setup just fails with that message.

I've had SQL Express April CTP installed on a windows 2003 Enterprise *trial*, which worked, the update to Junce CTP... right, fails with the same message.
Any proposals?|||Did you look for the log files?

-Euan|||Yes I did, and I found the problem: My windows XP Professional and Windows Server 2003 Web Edition are both german - the setup fails on non-english langauge versions with default settings, this german article describes the problem and how to solve it (for everyone else who encounters this):

http://www.microsoft.com/germany/msdn/vs2005/installvs2005beta.mspx
(basically, remove the tick "Hide advanced configuration Options" and select "Local System" as the service account, instead of "Network Service", which is the default.)