Exchange is sick after backup/restore

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I did a backup and restore of a server to replace a failing hard drive,
during which I followed the steps from
http://www.microsoft.com/downloads/details.aspx?familyid=487736F8-F6F5-436D-A82D-0C8D66E2A634
to the letter. Since the restore, Exchange 2003 has been very poorly.

1. The POP3 connector crashes every time it tries to run, saying:

"Microsoft Visual C++ Runtime Library. Runtime error! Program: c:\program
files\microsoft... This application has requested the Runtime to
terminate it in an unusual way. Please contact the application's support
team for more information".


2. Exchange System Manager crashes when you try to start it, saying:

"Exchange detected that c:\windows\system32\mapi32.dll is not the correct
version required to run Exchange System Manager or Exchange Server 2003.
This may cause failures in Exchange System Manager, affect availability of
your server, or both. (...) see Q266418 (...)"

KB266418 is the one that talks about why it's a bad idea to install Outlook
on an Exchange box. I didn't do this - all I did was restore a full backup.


3. The Application event log is full of event ID 9097 from source:
MSExchangeSA category: Monitoring, saying:

"The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'.

When you click through to Help and Support Center to get more information on
this error, it essentially suggests you reinstall Exchange.

---

Having said all this, Outlook clients connect to the server and can send and
receive mail, outgoing messages are being sent to the ISP's smarthost
successfully; the only show-stopper was that incoming mail wasn't working
due to the lack of POP3 Connector. To work around this I set up
fetchmail+exim on a SuSE linux box that happened to be in use as an internal
webserver, so essentially we're now doing without the POP3 connector...
with the added bonus that incoming mail is now arriving every 5 minutes
instead of every 15 minutes :-)

Having said all this - what should I to do to fix Exchange?

Reinstalling Exchange isn't going to go down to well unless I do it in the
evening or at a weekend... and I've already spent plenty of my free time
doing the backup/restore, so if anyone can come up with suggestions that
don't involve extended downtime I'd be grateful :-)

Thanks in advance,

Jim


.

Relevant Pages

  • Re: Disaster Recovery with NTBackup
    ... for the apps (Exchange, ISA, Sharepoint, etc.). ... I made from the SBS onto a test server which is exact model as the ... Should I move on with the restore despite of the errors? ... FULL backup of your entire server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Restore Exchange Store
    ... The server crashed and you have a new reinstallation. ... You tried to restore Exchange from the recent backup. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Backup/Disaster Recovery!
    ... MVP for Exchange Server ... > backup server from backup files/tapes. ... >> understand Exchange backup and restore. ...
    (microsoft.public.exchange.admin)
  • Re: Restore parallel copy of Exchange DB?
    ... Your "server" can be a workstation loaded with the correct software. ... Exchange server installed, as is required for syncing BB's with the SBS ... DB files directly to a backup location, I could then restore, extract ...
    (microsoft.public.exchange.admin)
  • Re: Exchange Server Restore From Backup - Help Needed
    ... had to modify the backup so that the Exchange Server files were only ... when I come to do a restore the only option I ... get is to restore to the current machine or to another Exchange Server. ... Because the Travan Tape only holds 20GB uncompressed 40GB compressed, ...
    (microsoft.public.windows.server.sbs)