Hi

I have a SQL Server 2000 instance that has been running fine for months, but this morning it refuses to start. The event log shows error messages "Error 9004, Severity 21, State 1". I've tried starting SQL Server in minimal server mode, but this doesn't help either.

It looks to me like the master database is corrupt. Can anyone tell me if that's a fair assessment and if there is a quick recovery from this one.

Thanks

Malcolm

BTW: The error log file shows the following...

2004-06-14 10:16:24.49 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 3)

2004-06-14 10:16:24.50 server Copyright (C) 1988-2000 Microsoft Corporation.
2004-06-14 10:16:24.50 server All rights reserved.
2004-06-14 10:16:24.50 server Server Process ID is 2384.
2004-06-14 10:16:24.52 server Logging SQL Server messages in file 'e:\mssql\MSSQL\log\ERRORLOG'.
2004-06-14 10:16:24.52 server Warning: -f command line flag used...minimal server configured.
2004-06-14 10:16:24.53 server SQL Server is starting at priority class 'normal'(4 CPUs detected).
2004-06-14 10:16:24.69 server SQL Server configured for fiber mode processing.
2004-06-14 10:16:24.71 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-06-14 10:16:24.80 server MS DTC initialization skipped because of start up option.
2004-06-14 10:16:24.80 spid3 Warning ******************
2004-06-14 10:16:24.82 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-06-14 10:16:24.83 spid3 Starting up database 'master'.
2004-06-14 10:16:24.85 spid3 Error: 9004, Severity: 21, State: 1.
2004-06-14 10:16:24.86 spid3 06/14/04 10:16:24 Stack Overflow Dump not possible - Exception c00000fd E at 0x00444B1F
2004-06-14 10:16:24.86 spid3 Address=444b1f Exception Code = c00000fd
2004-06-14 10:16:24.88 spid3 eax=00000000 ebx=00000000