E2K7 Exchange System Attendant service doesnt't start
Nicolas Macarez
My platform is E2K7 Enterprise Edition on W2K3 R2 SP2.
When I start the server, the Microsoft Exchange System Attendant service
doesnt't start which is kind of annoying.
I have got the event :
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 12/2/2007
Time: 6:02:34 PM
User: N/A
Computer: CLEVELAND
Description:
Unexpected error The Local Security Authority cannot be contacted ID no:
80090304 Microsoft Exchange System Attendant occurred.
Is there a simple way to solve this issue?
I went on http://support.microsoft.com/kb/940845/en-us (KB 940845) and
applied the Method number 4. But it doesn't work.
Is there a simple way to solve this issue ?
Help appreciated.
Nicolas
pgartner
> HI!
> My platform is E2K7 Enterprise Edition on W2K3 R2 SP2.
> When I start the server, the Microsoft Exchange System Attendant service
> doesnt't start which is kind of annoying.
>
> applied the Method number 4. But it doesn't work.
> Is there a simple way to solve this issue ?
>
I had the same problem. the restart service after 3 minutes NEVER
worked for me. i tried a scheduled batch file that ran net starts
every 3 minutes, It worked but was pain
Finally, i ended up using a BOOTPAUSE and a DEPENDSONSERVICE. that
worked like a charm
follow Method 3: Use the BootPause registry key to delay the startup
of Exchange Server
you should also note the following:
1) when you start (or restart your system) it will take at least 2
minutes longer for the exchange service to be up and running and
available to your users. (really, how often do you reboot your mail
server, this is a non-issue for me)
2) when you do a shutdown/restart the AD service will stop before
exchange can close properly, causing LONG delays as the exchange
services timeout. you can avoid this by manually stopping the exchange
service first, of do like i did, create a batch file
--- start
rem net stop MSExchangeES /y
net stop MSExchangeIS /y
rem net stop MSExchangeMTA /y
net stop MSExchangeSA /y
net stop WinHttpAutoProxySvc /y
net stop MSExchangeADTopology /y
net stop MSExchangeAntispamUpdate /y
net stop MSExchangeEdgeSync /y
net stop MSExchangeFDS /Y
net stop MSExchangeImap4 /y
net stop MSExchangeMailSubmission /y
net stop MSExchangeMailboxassistants /y
net stop MSExchangeMonitoring /y
net stop MSExchangePop3 /y
net stop MSExchangeRepl /y
net stop MSExchangeSearch /y
net stop MSExchangeServiceHost /y
net stop MSExchangeTransport /y
net stop MSExchangeTransportLogSearch /Y
net stop msftesql-Exchange /Y
--- end
for the life of me i can't remember why i remed out the ES and MTS
services :-(
Merry XMas
Paul
Nicolas Macarez
post!
I have been looking for this start/stop script of the Exchange services
(yes, my Exchange server sits on a DC and that's why it takes so long to
stop the machine).
I had these scripts with E2K3 and knew what are the services to stop with
E2K7, but... in which order? Now I know...
Thanks again and Merry Christmas to you as well.
Nicolas
"pgartner" <pgar...@ln-tech.com> a écrit dans le message de news:
b288024d-6e96-4de2...@b40g2000prf.googlegroups.com...
DJ
Ok I just spent all day Monday on phone with PSS over this same (and other
issues). It was after I applies SP1 for Exchange 2007. Do you have any
other errors besides this one? SA was failing because we were having other
strange issues, like the store failing, netlogon not being able to contact
the DC, etc. I messed around with the BootPause option as well, and it
worked, but we still had some weird errors.
This may not be your problem but we talked with Mike Lagase who wrote this
article:
Windows 2003 Scalable Networking pack and its possible effects on Exchange
http://msexchangeteam.com/archive/2007/07/18/446400.aspx
Check out this possibility. I never even knew about it. We updated all of
our NIC drivers (Broadcom) and things got a lot better. Most of the errors
went away.
I say most, FWIW, we were still getting some connectivity errors, like
Userenv 1053 errors, 5719 Netlogon errors, 2104 MSExchange ADAccess. And in
the end we enabled port fast on our Cisco switches, lo and behold,
everything went back to normal no errors, no delays.... nothing it all went
away.
There is some issue with spanning tree protocol and port fast, and a timeout
issue. And while the port switch is negotiating, no tcp traffic is passed
and thus services will fail looking for auth and dc info.
If your getting the 5719 error: http://support.microsoft.com/?kbid=938449
Info about the spanning tree protocol:
http://support.microsoft.com/?kbid=202840
A field notice from Cisco:
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_field_notice09186a0080851821.shtml
Kind of funny most of the "solutions" aka workaround is to just delay
everything, or make dependencies, while that may work, it definitely is not
a solution in my book, but sometimes it's whatever works.
Hope all turns out well.
Don
"Nicolas Macarez" <mac...@free.fr> wrote in message
news:Ojd3%23YkOI...@TK2MSFTNGP06.phx.gbl...
Nicolas Macarez
Just for your info - don't think it might help, but...
++ Every thing is fine for me, esp. with SA, because of the BOOTPAUSE and
DEPENDSONSERVICE tricks.
++ I didn't apply SP1 (still cautious from the Windows NT time about
applying SPs too soon).
++ My box is a Dell PowerEdge 2900 and I know that the drivers for the
Broadcom NIC really need to be updated with the very last update for 64 bits
(beware: not avalaible on the Dell Website, you need to go to the FTP site
and know exactly the name of the file you are looking for. I can help you
with that, if you wish). Solved a lot of issues as well.
++ I don't have CISCO routers (I stick to Netgear and Zyxel because of the
size (small, medium) of my clients)).
Regards
Nicolas
"DJ" <tickets4u~No~spam~@at@~cox~dot~net> a écrit dans le message de news:
eUgqvmJP...@TK2MSFTNGP02.phx.gbl...