OT - Can't connect to SQL Server after power outage

[meckeard]

All,

I had a power outage at work over the weekend and now my local PC cannot access any SQL Server.

I get the usual "sql server does not exist or access is denied" error. Nothing else. This started sometime over the weekend and the only thing that comes to mind is the power outage.

I tried connecting to 2 other DB's with no luck. So I decided to move all the pages to a different server and it works fine.

Any ideas what could have caused this?

Thanks,
Mark

 

[chiph]

Are the lights on in your office?

Chip H.


____________________________________________________________________
Click here to learn Ways to help with Tsunami Relief
If you want to get the best response to a question, please read FAQ222-2244 first

 

[meckeard]

Chip,

Yeah, they are one! No problems with anything else but this one issue.

Mark

 

[chiph]

Sorry, couldn't help pulling your leg a little bit.
;-)

If you're using Integrated Security (in your connect string, or in Query Analyzer), my guess would be that something happened to the domain controller, and when the SQL Server goes to authenticate you against Active Directory, it's failing.

If you're using SQL Server authentication (passing a userid/password in the connect string), then it's something gone wacky on the SQL Server itself. I would try logging in as sa to see what happens.

Chip H.


____________________________________________________________________
Click here to learn Ways to help with Tsunami Relief
If you want to get the best response to a question, please read FAQ222-2244 first

 

[meckeard]

I figured as much

I am using SQL Server authentication.

I changed my connection string to log in as sa and it worked. But this was on my local PC where I have SQL Server and the web app. However, if I try to use the sa ID and hit the DB on another server, it doesn't work.

Any ideas?

Thanks,
Mark

 

[chiph]

One last thing to do: go to the console for that server, and start up Query Analyzer. If you can get in as sa, then there's something wonky with the networking. If not, then something has corrupted the catalog on that server.

If the catalog is corrupt, you can run a DBCC and see if that fixes it, otherwise you'll have to reload from backup.

Chip H.


____________________________________________________________________
Click here to learn Ways to help with Tsunami Relief
If you want to get the best response to a question, please read FAQ222-2244 first

 

[icrf]

You tried restarting IIS on the machine in question? I've had bad luck with the timing of server restarts bring up a situation like this before. If IIS gets running before SQL Server does and it can't make a connection on start-up, often a simple restart of the IIS service will fix matters.

Best of luck.

________________________________________
Andrew

I work for a gift card company!

 

[meckeard]

Guys,

It seems that after a few days of testing (and hair pulling), 2 reboots solved the problem on my local PC and the DEV instance of SQL Server.

Thanks for help.

Mark