Re: Please Help: Exchange server will not start after W2K SP4 by Patrick
Patrick
Thu Sep 11 20:42:27 CDT 2003
Yes. But I stopped IIS before applying the SP. How do I recover?
I had bad experience in the past trying to uninstall the lockdown tool on
another SBS and it wound up not being uninstalled since the DLLs were still
in the server but the entry to uninstall disappeared from the Add/Remove
list. It left the IIS metabase in such a state that no matter what I did,
OWA would not work and I did not plan on reinstalling the entire server to
fix it. Fortunately, OWA was not used in that installation.
Also I have rebooted numerous times and manually started MSExchangeSA
without success.
Patrick
"Marina Roos" <marina@roos.nodontwantspam.nl.com> wrote in message
news:FG78b.99476$506.101639@typhoon.bart.nl...
> Was the Lockdown tool installed before applying SP4?
>
> Marina
>
> "Dave Nickason" <gwdibble@frontiernet.net> schreef in bericht
> news:#6XqSoKeDHA.1732@TK2MSFTNGP12.phx.gbl...
> > Other than the TechNet articles, I unfortunately don't have any
particular
> > knowledge of this problem. To start troubleshooting it, I would first
see
> > if any services are not running that should be (obviously other than
> > Exchange services). In particular, how about IIS?
> >
> > Any other errors logged?
> >
> > Secondly, what happens if you try to start the services manually? If
they
> > start, what happens if you reboot again? (Although you clearly need to
> > resolve this so that everything starts normally after a reboot, it would
> > take some of the pressure off if the services can be run while you're
> > troubleshooting).
> >
> > And regardless of anything else, what happens if you reboot again? I've
> had
> > instances where there was a mess on the first reboot, but everything
> cleared
> > up during that reboot, and the next one went smoothly.
> >
> >
> > "Patrick Ip" <sysop562sbs@nospam.picsinc.com> wrote in message
> > news:e5CKOfKeDHA.2304@TK2MSFTNGP10.phx.gbl...
> > > Dave,
> > >
> > > I forgot to respond in my last post that article 328646 does not apply
> > since
> > > "Manage auditing and security logs" permission for the Exchange
> Enterprise
> > > Servers group is not missing. Here is the output from POLICYTEST.EXE:
> > >
> > > ===============================================
> > > Local domain is <Domain Name>
> > > Account is "<Domain Name>\Exchange Enterprise Servers"
> > > ========================
> > > DC = "PSSB01"
> > > In site = "Default-First-Site-Name"
> > > Right found: "SeSecurityPrivilege"
> > >
> > > Patrick
> > >
> > > "Dave Nickason" <gwdibble@frontiernet.net> wrote in message
> > > news:OtJy7$JeDHA.1836@TK2MSFTNGP09.phx.gbl...
> > > > I assume you've searched TechNet for "80040a01" - a few other
articles
> > > come
> > > > up other than the one you tried. How about 328646 XADM: System
> > Attendant
> > > > Service Does Not Start After Windows 2000 Security Rollup Package 1
> > > > Installation. Maybe that would apply if you skipped the rollup and
> went
> > > > directly to the SP.
> > > >
> > > >
> > > > "Patrick Ip" <sysop562sbs@nospam.picsinc.com> wrote in message
> > > > news:%23HvZyhJeDHA.2680@TK2MSFTNGP11.phx.gbl...
> > > > > I read all the previous posts regarding W2K SP4 on SBS before I
> > > attempted
> > > > to
> > > > > apply the patch. Prior to applying the patch, I made disaster
> > recovery
> > > > > image of the boot drive so I could go back to SP3 if I wanted to.
I
> > > > stopped
> > > > > the backup program (CA ARCserve), the Exchange Server, IIS, and
> > > Antivirus
> > > > > scanner (Symantec). The server does not have SQL server. I used
> the
> > > > > network version of SP4 and it ran without an errors. After the
> server
> > > > > rebooted, the Exchange server would not start and I found the
> > following
> > > > > events:
> > > > >
> > > > > MSExchangeMU Event ID 1002
> > > > > Metabase Update agent failed to start. Error code is 80040a01.
> > > > >
> > > > > MSExchangeSA EventID 9004
> > > > > The Metabase Update service failed to start, error '80040a01'.
> > > > >
> > > > > MSExchangeSA EventID 1005
> > > > > Unexpected error An unknown error has occurred. ID no: 80040a01
> > > Microsoft
> > > > > Exchange System Attendant occurred.
> > > > >
> > > > > MSExchangeSA EventID 1004
> > > > > Microsoft Exchange System Attendant failed to start.
> > > > >
> > > > > MSExchangeDSaccess EventID 2078
> > > > > Process MAD.EXE (PID=3088). DSAccess is shutting down.
> > > > >
> > > > > Serve Control Manager logged the following 3 7001 Events:
> > > > > The Microsoft Exchange Information Store service depends on the
> > > Microsoft
> > > > > Exchange System Attendant service which failed to start because of
> the
> > > > > following error:
> > > > > %%0
> > > > >
> > > > > The Microsoft Exchange MTA Stacks service depends on the Microsoft
> > > > Exchange
> > > > > System Attendant service which failed to start because of the
> > following
> > > > > error:
> > > > > %%0
> > > > >
> > > > > The World Wide Web Publishing Service service depends on the
> Microsoft
> > > > > Exchange Information Store service which failed to start because
of
> > the
> > > > > following error:
> > > > > The dependency service or group failed to start.
> > > > >
> > > > > I searched MS knowledge base and found articles (e.g. 312859) that
> > > pertain
> > > > > to Exchange Server SP2. Mine is SP3 after SBS SP1 upgrade. I did
> add
> > > the
> > > > > TopoCreateTimeoutSecs registry entry as suggested and rebooted but
> it
> > > did
> > > > > not fix the problem.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Patrick
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>