• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7063
  • Last Modified:

Error code 1053 for System Attendant

Hey everyone,

I have an exchange server 2000..I have a problem with my exchange server starting mailing services. When I attempt to start the Microsoft Exchange System Attendant it states

"Could not start the Microsoft Exchange System Attendant service on the Local Computer Error 1053"

It takes a long time for the service to start. Does anybody know or had this type of problem.

I also have the same problem as a previous question about unsolicted domains flooding the exchange server with virus attachments. I believe I removed all the viruses, but with the system unable to start in a timely fashion I'm not certain. Any help would be greatly appreciated.
0
Menace212
Asked:
Menace212
  • 6
  • 4
  • 3
  • +3
1 Solution
 
What90Commented:
I think that the user account you are using to start the service has the wrong password.

Check which account (look in services - Microsoft Exchange System Attendant - properties) and see what account is used to run it.

If you've recently change the Exchange system account that's problem, make sure the service is using the right password.
0
 
VahikCommented:
what90 If i read this right i think menace says that service does start finally(is this correct menace?)eventhough taking a long time.If that is the case it may not be the account but
the dependencies.check out the dependencies for that service and see if they are all
started before u start that service.
0
 
eedleeCommented:
Look for "Microsoft Exchange System Attendant is loading xxxxxx.dll" when you attempt to start the Sys Attendant to help pinpoint the error location (if it is indeed attempting to load a dependancy service).
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
What90Commented:
Hey Vahik,

Will this error message:
"Could not start the Microsoft Exchange System Attendant service on the Local Computer Error 1053"

I'd be amazed if the services have started, but then again it is Ms ;-)

0
 
VahikCommented:
Hi what90.


i know this is a bit confusing that is why i said if i read it right.But to tell u the
truth in this business i have even seen an exchange server tap dance right
infront of me.HAHAHA.
Lets see what the patient has to say about his problem.
0
 
What90Commented:

*grin* After reading 2 months worth of your replies I'm cleaning up I've very sure you have!  

0
 
VahikCommented:
I will tell u a good one.MS tells u not to promote or demote a server to DC or back
if exchange server is installed on it because it will screw up ur exchange.I was helping this person(trying to help)and guess what solved his problem.he demoted the DC with exchange on it and then promoted it back and solved his own problem.so in exchange
nothing is what it seems to be.U know how many times i have fixed servers by kicking them?
what90 a few laughs before the bed.It is good for the heart.see u later.
0
 
What90Commented:
*grin*

Vahik - kicking servers to fix them - your my hero!

I'd love to do that to a number of crappy machines we have here.

Sleep well !
0
 
Menace212Author Commented:
Peeps,

It's dependency is the eventlog, NT LM Security Support Provider, RPC, RPC Locator, Server and Workstation...All these dependencies are started..But for some reason the System attendant won't start in a timely manner. My account has been the same as before so that hasn't changed.


Somebody mentioned a loading a dll, what dll should I be looking for. .It may or may not start....Sometimes it may take a week or days which is unaccetable......Any other suggestions or solutions.
0
 
What90Commented:
Re-apply all the latest SP and patches for Exchange.

Clean out all the junk and items in the Badmail queue. This explains a bit more about it:
http://www.msexchange.org/tutorials/SMTP_Virtual_Server_Uncovered.html


Are you running Av on the Exchange box?
If you have as long as you set up the Av correctly and DON'T scan any of the exchange directories, it not a problem and should be done ASAP
0
 
Menace212Author Commented:
Thanks for the info...I'm checking it out now....I was hit by large number of spam email.....I did move my my mailbox from the the c drive to the D drive for more space...Although I can't find the emails to delete on the D drive. Maybe that could be a problem..what do ya'll think....
0
 
Menace212Author Commented:
The event viewer did give me a error message in starting the System Attendant..

"Unexpected error an unknown error has occured ID no 80040a01
Microsoft Exchange System Attendant occured"
0
 
Menace212Author Commented:
I think I might be on to something...I just checked when I attempted to log on to the Active Directory and Users on the Exchange server and error message stated that the naming information cannot be located because the active direrctory server is not opeational.... But the problem is I can ping it...What can I do to resolve this issue????


Would this be the cause of the System Attendant unable to be started....
0
 
What90Commented:
0
 
David WilhoitCommented:
Is the Exchange server pointed to internal DNS only? If not it should be...

The SA normally won't start because it needs domainprep to be run again, or DNS is configured improperly...

D
0
 
badab99Commented:
H:\>net helpmsg 1053

The service did not respond to the start or control request in a timely fashion.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 4
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now