December 22, 2002 at 7:39 am
Guys, I've got a really nasty problem with TempDB.
My MSSQLSERVER service won't start (SQL 2000) because it can't find TempDB.
I opened up notepad and copied the path from the error message in the event logs, and copied the path of TempDB from windows explorer. EXACTLY the same.
I thought that TempDB got recreated every time that SQL Server got restarted, so what's the problem?
The problem started after I installed Office2000 SP3 on the machine. Is it possible that there is something to do with MSDE in the service pack and this has wrecked my SQL Server installation?
Is there a way of fixing my TempDB problem without resorting to uninstalling then re-installing my entire SQL Server?
December 22, 2002 at 9:45 am
Could be however I don't believe so as it should have looked for MSDE only and I am pretty sure no MSDE updates are included in the Office SP as there is one specific to the MSDE and it does detect installed version first.
I also find no information and need more details. Can you post the error message please?
A few things to try.
Rename tempdb and restart the server then start SQL and see if builds a new copy.
Login as the account SQL server is running under if not the local system account and make sure it is not a permissions problem.
Try reinstalling the SQL SP either latest or the last one installed and see if problem goes away.
Edited by - antares686 on 12/22/2002 09:46:09 AM
January 6, 2003 at 7:51 am
The error in the event log is
quote:
17204 :FCB::Open failed: Could not open device F:\SQLServer2000\SQL_SystemLog\TempLog.ldf for virtual device number (VDN) 2
If I rename the files and restart SQL I get an additional message saying that the file does not exist.
I wiped the installation of SQL2000 and re-installed everything. I then proceeded to move the master (following a complete backup of course). Hey Presto, SQL Server gives the quoted error message, but for the master database!
There must be something funny about the box it is running on because I have followed my standard install procedure to the letter, and I have done this many times, i.e. moving system databases and logs to seperate locations.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply