A client was restarting the server. He declares that he saw an error message
about something being corrupted, but he didn't catch much more then that.
The system came back up but it seemed like the Administrator user profile was
lost. The Desktop was back to default, opening IE brought up the old Setup
Your Internet screen, applications set to start with the OS are no longer
starting... It sounds to me like the Administrator user profile was lost.
The weird thing though is that SQL Server won't start.

There is an Administrator.bak folder in Docs and Settings. I'm not sure how
long that has been there.

There SQL error that keep coming up are
MSSQLSERVER Category 2 Event ID 17055 "18052: Error 9003, Severity: 20,
State: 1."
MSSQLSERVER Category 2 Event ID 17055 "17052: Cannot recover the master
database. Exiting."

"Steven" <(E-Mail Removed)> wrote in message
news:90A36EA2-BA58-42C4-8733-(E-Mail Removed)...
>A client was restarting the server. He declares that he saw an error
>message
> about something being corrupted, but he didn't catch much more then that.
> The system came back up but it seemed like the Administrator user profile
> was
> lost. The Desktop was back to default, opening IE brought up the old
> Setup
> Your Internet screen, applications set to start with the OS are no longer
> starting... It sounds to me like the Administrator user profile was lost.
> The weird thing though is that SQL Server won't start.
>
> There is an Administrator.bak folder in Docs and Settings. I'm not sure
> how
> long that has been there.
>
> There SQL error that keep coming up are
> MSSQLSERVER Category 2 Event ID 17055 "18052: Error 9003, Severity: 20,
> State: 1."
> MSSQLSERVER Category 2 Event ID 17055 "17052: Cannot recover the master
> database. Exiting."

Your question was?
Have you tried logging on under a different account?

We can log in as other users, but SQL still won't start.
Checking the Administrator.bak folder, all the desktop icons, startup apps,
etc. are there. For whatever reason, Windows added a .bak to the
administrator profile and created a new one. Then, why SQL won't start is an
additional mystery.

"Pegasus (MVP)" wrote:

>
> "Steven" <(E-Mail Removed)> wrote in message
> news:90A36EA2-BA58-42C4-8733-(E-Mail Removed)...
> >A client was restarting the server. He declares that he saw an error
> >message
> > about something being corrupted, but he didn't catch much more then that.
> > The system came back up but it seemed like the Administrator user profile
> > was
> > lost. The Desktop was back to default, opening IE brought up the old
> > Setup
> > Your Internet screen, applications set to start with the OS are no longer
> > starting... It sounds to me like the Administrator user profile was lost.
> > The weird thing though is that SQL Server won't start.
> >
> > There is an Administrator.bak folder in Docs and Settings. I'm not sure
> > how
> > long that has been there.
> >
> > There SQL error that keep coming up are
> > MSSQLSERVER Category 2 Event ID 17055 "18052: Error 9003, Severity: 20,
> > State: 1."
> > MSSQLSERVER Category 2 Event ID 17055 "17052: Cannot recover the master
> > database. Exiting."
>
> Your question was?
> Have you tried logging on under a different account?
>
>
>

Follow the steps in this article to replace the corrupt profile.

http://support.microsoft.com/?id=296834


Try changing the account to start the MSSQLSERVER service to a known good
account. Also;

http://support.microsoft.com/default...b;en-us;826373


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Steven" wrote:
> We can log in as other users, but SQL still won't start.
> Checking the Administrator.bak folder, all the desktop icons, startup
> apps,
> etc. are there. For whatever reason, Windows added a .bak to the
> administrator profile and created a new one. Then, why SQL won't start is
> an
> additional mystery.