We recently migrated our mail to a new Exchange server, upgraded Exchange to 2003 SP2, moved our Exchange Remote Agent to the new machine, and updated our jobs to backup data in the new location. Since the move, Backups of the Exchange server are failing with the following errors in BackupExec.
Backup- \\SBI-SERVER1\D: New Volume
V-79-57344-34110 - AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open Fil...
Snapshot provider error (0xE0008516): Resources specified for snapshot do not have any valid data on...
Check the Windows Event Viewer for details.
V-79-57344-34110 - AOFO: Initialization failure on: "\\SBI-SERVER1\System?State". Advanced Open File...
Snapshot provider error (0xE000FE1F): The device cannot be found.
Check the Windows Event Viewer for details.
Additionally, the following events appear in the Application Log on SBI-SERVER1 at the time when BE is trying to log into Exchange and run the backup:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 2/5/2009
Time: 11:16:02 PM
User: N/A
Computer: SBI-SERVER1
Description:
Faulting application svchost.exe, version 5.2.3790.3959, faulting module unknown, version 0.0.0.0, fault address 0x013bf4b6.
Event Type: Error
Event Source: MSExchangeSA
Event Category: (2)
Event ID: 9099
Date: 2/5/2009
Time: 11:16:15 PM
User: N/A
Computer: SBI-SERVER1
Description:
The description for Event ID ( 9099 ) in Source ( MSExchangeSA ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 0x800706ba.
The ExchangeSA event is then followed by events indicating the SA has re-initialized properly, and mail continues to work, but the Automatic Updates, Computer Browser, Cryptographic Services, Logical Disk Manager, Secondary Logon, Server, Volume Shadow Copy, Windows Audio, and Workstation services on the server are all stopped.
vssadmin list writers shows some writers still running, but Exchange is not.
After rebooting, all the services come back up, and the Exchange vss writer is running, but the exact same crash happens the next night when the backup jobs run again.
I found a KB article about a similar problem with Exchange 2007, but it indicated an additional event that should be logged, which we are not receiving. I'm baffled as to what is causing these errors and any help on how to get this system running again would be much appreciated.
Message Edited by JohnSweeney on 02-06-2009 10:04 AM
