Can't start MSSQLServer (due to a logon failure). (2nd msg)

[Edward]

Please disregard my previous post (it was sent by
accident before it was completed).
Before my MSSQLServer was working (icon on task bar able
to go green). Later I uninstalled the MSDE and when I
reinstalled it I could not get the MSSQLServer to start.
When I try to start it I get the following message:

An error 1069 - (The Service did not start due to a logon
failure.) occurred while performing this service
operation on the MSSQLServer service.

I am using Access 2000 on WindowsXP Home edition. Do you
know what might be causing this problem? Thank you and
please accept my apologies for the previous incomplete
post, Edward.

 

[BJ Freeman]

What happens when you open the Sql Server manager?

 

[Danny Nielsen]

An error 1069 - (The Service did not start due to a logon

failure.) occurred while performing this service
operation on the MSSQLServer service.

I have just had a similar error - think it happened because I changed the
administrator password in Windows2000. The problem disappeared when I
restarted the sql proces. There should be a proces manager in XP where you
can deside to start/restart processes.

Danny Nielsen

 

[Edward]

When I open the Sql Service manager I get a fairly small
square dialog that has 2 text boxes with drop down arrows
(they are labled Server and Services). My full name is in
the Server box and MSSQLServer is in the Services box.
Below the boxes there is a red square on the left side
and a Start/Continue (enabled) button on the right along
with a disabled Pause and disabled Stop button. It is
when I click on the Start/Continue button that I get the
logon failure message (error 1069). I hope this helps,
Edward.

 

[Edward]

I know of a Task Manager that has a processes tab but I
don't know about a Process Manager (in Windows XP home).
The Task Manager only seems capable of stopping
processes - it doesn't seem to be able to start processes
(no 'start task' button exists in the dialogue, in fact
stopped processes are not even listed). Too bad the error
message doesn't have a 'details' button - just an OK but-
ton). Thanks anyway - let me know if you have any other
ideas, Edward.