A reboot of an older server running Windows Server 2000 and SQL Server 2000
seems to have resulted in a cascade of issues. Obvious results include the
desktop profile and internet access being reset to default, applications set
to start with the OS no longer do and SQL Server won't start at all. Here is
a collection of error messages we are getting:
In computer management clicking Services and Applications:
Error connecting to servername:
The Service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.
Do you wish to continue to attempt to connect to it in the future?
Clicking Yes gets us to the services list.
In SQL Service Manager:
Click Start/Continue for SQL Server and it pauses for awhile, but then
nothing happens.
The application event viewer yields two new error messages:
MSSQLSERVER Category 2 Event ID 17055 "17052: Cannot recover the master
database. Exiting."
MSSQLSERVER Category 2 Event ID 17055 "18052: Error 9003, Severity: 20,
State: 1."
Other errors repeated after each reboot of the system include:
Source W3Ctrs Category None Event ID 1003 "Unabe to wquery the W3SVC (HTTP)
service performance data. The error code returned by the service is data
DWORD 0..."
Source FTPCtrs Category None Event ID 1000 "Unable to collect the FTP
performance statistics. The error code returned by the service is data DWORD
0..."
Source IISInfoCtrs Category None Event ID 1003 "Unable to query the IIS info
service performance data. The error code returned by the service is data
DWORD 0..."
Source ESENT Category Logging/Recovery Event ID 300 "RsFsa (884) The
database engine is initating recovery steps."
Source ESENT Category Logging/Recovery Event ID 302 " RsFsa (868) The
database engine has sucessfully completed recovery steps."
Rick Byham, (MSFT) - 15 Jul 2008 20:35 GMT
Given your problem description it sounds like there are lots of potential
problems. My first guess is that the account being used to start the
database engine has lost it's permissions and can't access the file folder
where the master database is stored.
Try changing the account used by the service to one that you know is an
administrator.

Signature
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.
>A reboot of an older server running Windows Server 2000 and SQL Server 2000
> seems to have resulted in a cascade of issues. Obvious results include
[quoted text clipped - 38 lines]
> Source ESENT Category Logging/Recovery Event ID 302 " RsFsa (868) The
> database engine has sucessfully completed recovery steps."