Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 318
  • Last Modified:

SQL Server 2000 and VMWARE

Recently i was testing MSSQL on Vmware, and turns out it works for a time, but after rebooting the HOST server , MSSQL never started again, someone know how to work arround that ?
Or should i forget MSSQL 2000 and VMWARE ?
  • 4
  • 2
  • 2
1 Solution
For minor to medium SQL Server Instances, VMWare is not really a problem.
It's when your IO-transfers are very high that you need to consider :
- To go physical
- To add a dedicated RAID-Controller ( directly in the OS, not managed by VMWare ) with a dedicated IO-subsystem.

For you problem of starting the service, anything in the eventviewer and/or sql server log?
We got about 40 SQL2000 servers running on VMware so that is not the problem.
I need some more information to give you an advise what to do.
Are there any error messages in the eventlog. Could be for instance be that the sql service is running under a account with not enough rights to start a local service.
netwhwAuthor Commented:
Could be this account issue , i have no access to event log, because sql server does not starts , if you provide me the folder where it does stores the logs, i can check for further messages.
I am running VMware on Bridged Mode Network, and right after i install it works, but after rebooting, it never starts again !
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

netwhwAuthor Commented:
Here is the LOG

2009-04-20 20:00:52.57 server    Copyright (C) 1988-2002 Microsoft Corporation.
2009-04-20 20:00:52.57 server    All rights reserved.
2009-04-20 20:00:52.57 server    Server Process ID is 3460.
2009-04-20 20:00:52.57 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2009-04-20 20:00:52.59 server    SQL Server is starting at priority class 'normal'(2 CPUs detected).
2009-04-20 20:00:52.68 server    SQL Server configured for thread mode processing.
2009-04-20 20:00:52.70 server    Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2009-04-20 20:00:52.79 server    Attempting to initialize Distributed Transaction Coordinator.
2009-04-20 20:00:53.85 spid4     Starting up database 'master'.
2009-04-20 20:00:54.26 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
2009-04-20 20:00:54.26 spid5     Starting up database 'model'.
2009-04-20 20:00:54.28 server    SQL server listening on WANIP: 1433.
2009-04-20 20:00:54.28 server    SQL server listening on 1433.
2009-04-20 20:00:54.28 server    SQL server listening on TCP, Shared Memory, Named Pipes.
2009-04-20 20:00:54.28 server    SQL Server is ready for client connections
2009-04-20 20:00:54.29 spid4     Server name is 'xxxx'.
2009-04-20 20:00:54.29 spid8     Starting up database 'msdb'.
2009-04-20 20:00:54.29 spid9     Starting up database 'pubs'.
2009-04-20 20:00:54.31 spid10    Starting up database 'Northwind'.
2009-04-20 20:00:55.25 spid5     Clearing tempdb database.
2009-04-20 20:00:55.76 spid5     Starting up database 'tempdb'.
2009-04-20 20:00:55.87 spid4     Recovery complete.
2009-04-20 20:00:55.87 spid4     SQL global counter collection task is created.
2009-04-20 20:00:55.95 spid4     Warning: override, autoexec procedures skipped.

Log ends here !

That's quite strange that it stops there.
Can you check in the Eventviewer of Windows what error-code is returned from the service.

Does it take a long time to try to start the service or does it fail immediatly ?
I found this information on the internet, more people had this problem after SQL install:

1. Delete the folder: C:\Program Files\Microsoft SQL Server
2. go into the regedit application by entering "regedit" into the prompt after selecting "run" from your start menu.
3. Look in HKEY_LOCAL_MACHINE | SOFTWARE | MICROSOFT | and delete the folder "Microsoft SQL Server" as well as the folder MSSQLServer and SQL Redist.
4. run the sql installation exe file. The installation will complete without any notice, but sql will not be running. Restart the machine and you will see the sql service will start.
netwhwAuthor Commented:
OK, I Will try, give me just a momment ! I will post results back here
netwhwAuthor Commented:
Thanks it worked out, but perfomance is not the best thought !

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now