Event ID 17052 - SQL Server 2000 ver 8.0.760

[davidchardonnet]

Hello,

My SQL Server 2000 is giving me a lot of event ID 17052,

with the following message:
Error: 9001, Gravity: 21, State: 1
The 'tempdb' database log is not available.

And this message is diplayed for all the databases on the server.

On the client Side where the application is run, the ODBC driver gives a Fatal Error 9001.

Do ou know how I can correct this?

Thank you

David

 

[ptheriault]

Find where your Tempdb is on the server. Are you running out of disk space? It is possible that long running queries are causing your tempdb to grow, using up all of the disk space. Making it unavailable for other users.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[davidchardonnet]

The messages are all on the tempdb, and after a reboot it seems to have disappeared... I don't understand.

There are 30 Gb of free disk space..

I ask to my user to retry..

 

[mutley1]

I think Paul has given the answer there. The tempdb has probably run out of space (i.e. filled the disk). Basically, tempdb is rebuilt after a reboot (or stop and start of SQL Services), so if you are seeing 30GB of free space after a reboot, then it is possible it had chewed that all up before. If it happens again, check the free disk space before rebooting and that will confirm - then examine what is causing the tempdb to grow and not release any space.

HTH,

M.

 

[mrdenny]

That error isn't a free space error. It typically means that the files were deleted by someone, or if it just starts happening that the drive which hosts the log files has become unavailable. Check the SYSTEM log for before the reboot and see what it says.

You may have a larger problem than you think which will need to be addresses quickly (possible hardware failure).

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[SQLBill]

As Mutley1 and MrDenny pointed out, TEMPDB acts very different than other databases. When you reboot a server, or stop and start the MSSQLServer service, TEMPDB is rebuilt from scratch. This can solve many problems with TEMPDB, but it also 'hides' what caused the issue.

1. Someone deleted one or both of the TEMPDB files.
2. Hard drive error caused problems with the TEMPDB files.
3. The TEMPDB grew too large for the disk space.
4. Something else.

You need to check the Windows Event viewer logs and see if there are any error messages that might indicate what happened. Also, check the SQL Server Error Logs....if TEMPDB grew too large, it should show that in the Error Log. (When you restarted SQL Server, it would have created a new log, so make sure you check the one previous to the current one).

Keep an eye on the drive that TEMPDB is on and the TEMPDB itself for the next several days. Watch for the problem to repeat itself.

-SQLBill

Posting advice: FAQ481-4875