Switching hard drives 1

[EchoAlertcom]

Hello,

I need a little guidance please with a SQL 2000 Server.

I have a machine in a geographically remote datacenter. This is a non-critical database so the machine is not an expensive set up. Before we sent the server off we set it up with 2 IDE Hard Drives, one off of each of the IDE channels. There is no CD_ROM device, so each is the Primary and only drive on each channel. The reason was that if we had a complete failure on one drive we could have remote hands switch the IDE cables and restart the machine and we would be back in business. We tested this in our office and it worked fine. SQLServer started and ran just fine. We attached a new db and we were working again.

Now, we have had a problem with Windows on the original drive and it is easier for us to switch the cables than to pay our datacenter to re-install Windows and SQL for us. But when the machine started and we logged in, SQL was not started and every time we try to start the service it seems to start and then stops.

I get the Event ID 17055, I have tried to locate info on the web that would help me through this but have failed to find a solution that works.

I tried to Re-run SQL SP3 but it gives the error that it can't start the service.

The SQL Error Log is posted below:

2003-06-17 11:16:10.18 server    Copyright (C) 1988-2002 Microsoft Corporation.
2003-06-17 11:16:10.18 server    All rights reserved.
2003-06-17 11:16:10.18 server    Server Process ID is 1788.
2003-06-17 11:16:10.18 server    Logging SQL Server messages in file 'x:\x\x\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2003-06-17 11:16:10.19 server    SQL Server is starting at priority class 'normal'(1 CPU detected).
2003-06-17 11:16:10.43 server    SQL Server configured for thread mode processing.
2003-06-17 11:16:10.44 server    Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-06-17 11:16:10.49 server    Attempting to initialize Distributed Transaction Coordinator.
2003-06-17 11:16:11.61 spid3     Warning ******************
2003-06-17 11:16:11.61 spid3     SQL Server started in single user mode. Updates allowed to system catalogs.
2003-06-17 11:16:11.63 spid3     Starting up database 'master'.
2003-06-17 11:16:12.58 spid3     0 transactions rolled back in database 'master' (1).
2003-06-17 11:16:12.60 spid3     Recovery is checkpointing database 'master' (1)
2003-06-17 11:16:12.80 server    Using 'SSNETLIB.DLL' version '8.0.760'.
2003-06-17 11:16:12.83 server    SQL server listening on (for security reasons)xxx.xxx.xxx.10: 1433.
2003-06-17 11:16:12.83 server    SQL server listening on xxx.xxx.xxx.11: 1433.
2003-06-17 11:16:12.83 server    SQL server listening on xxx.xxx.xxx.12: 1433.
2003-06-17 11:16:12.83 server    SQL server listening on xxx.xxx.xxx.13: 1433.
2003-06-17 11:16:12.83 server    SQL server listening on xxx.xxx.xxx.14: 1433.
2003-06-17 11:16:12.83 server    SQL server listening on 127.0.0.1: 1433.
2003-06-17 11:16:12.85 spid5     Starting up database 'model'.
2003-06-17 11:16:12.93 spid3     Server name is 'xxxxxx2'.
2003-06-17 11:16:12.93 spid7     Starting up database 'msdb'.
2003-06-17 11:16:12.93 spid8     Starting up database 'pubs'.
2003-06-17 11:16:12.93 spid9     Starting up database 'Northwind'.
2003-06-17 11:16:12.93 spid10    Starting up database 'xxxxx'.
2003-06-17 11:16:14.28 spid5     Clearing tempdb database.
2003-06-17 11:16:14.41 spid9     Starting up database 'StoryWriter'.
2003-06-17 11:16:15.10 server    SQL server listening on TCP, Shared Memory, Named Pipes.
2003-06-17 11:16:15.10 server    SQL Server is ready for client connections
2003-06-17 11:16:16.06 spid5     Starting up database 'tempdb'.
2003-06-17 11:16:16.38 spid3     Recovery complete.
2003-06-17 11:16:16.38 spid3     SQL global counter collection task is created.
2003-06-17 11:16:16.55 spid3     Warning: override, autoexec procedures skipped.
2003-06-17 11:17:28.45 spid3     SQL Server is terminating due to 'stop' request from Service Control Manager.

Any help or guidance will be greatly appreciated.

Sincerely,
Steve

 

[SQLBill]

First, has MASTER been set back to multi-user?

Second, are the databases using AUTO-CLOSE?

-SQLBill

 

[EchoAlertcom]

Thanks for your help.

I don't know on either question. How do I find out and if they are not as they should be how do I go about making them so?

Sincerely,
Steve

 

[SQLBill]

Are you using Enterprise Manager or are you entering commands via OSQL?

If Enterprise Manager:
1. Expand the server to show the databases, right click on Master, select Properties, go to the Options tab and in the top 1/3rd there's a section for ACCESS with two radio buttons. One says Single User. Neither one, nor the Restrict Access check box should be selected.

2. Same place, about 1/2 way down there's a section Settings. Check that Auto-Close is unchecked.

Check both of those items in all databases.


-SQLBill

 

[EchoAlertcom]

I can't get that far in Enterprise Manager. EM couldn't connect to the server so I deleted the connection and tried to connect again and couldn't. Is there a way to get there? Or can I use OSQL. I am inexperienced with this tool.

Thanks for your help.

Steve

 

[SQLBill]

How are you registering the server in EM? By name or IP address? If by name, give it a try with the IP address. If you can't set it up by IP address, it may be a network issue.

-SQLBill

 

[EchoAlertcom]

Hi SQLBill,

I tried to connect by IP and could not. I have verified that there are no IP Conflicts on the network. The hostname resolves to the correct IP. Any other suggestions?

While we have this thread going I have a few questions in preparation for this not working.

Are there any issues with re-installing SQL2000 over a MS Terminal Session? I do Service Packs and so on, but no sure on this.

To get back to square one. Would I run an upgrade, or un-install SQL and re-install?

I have already tried to run SP3, it wouldn't work because it couldn't start the SQL services.

Thank you so much for your help SQLBill.

Cheers,
Steve

 

[EchoAlertcom]

I just found this in the exception.log file.

06/18/03 09:05:13 spid 0 Exception 0xc000008c EXCEPTION_ARRAY_BOUNDS_EXCEEDED at 0x26730FDA

I hope it helps.

Steve