09-08-2010 01:59 PM
Solved! Go to Solution.
10-20-2010 09:07 AM
Sorry for going dark on this, everyone. In my case it ended up being an external virtualization issue, and not a problem with either application at all (Backup Exec or Exchange). There were some I/O issues on the VM host causing the VSS snapshot writer to time out before a snapshot could be created.
09-08-2010 09:35 PM
09-09-2010 06:52 AM
09-09-2010 11:45 AM
10-09-2010 11:25 PM
Any news on this Mike?
10-10-2010 09:38 PM
Do the following steps to resolve this problem
1. Uninstall MAPI and CDO from exchange server.
2. Reboot exchange server
3. Download latest CDO from Microsoft site
4. Install downloaded CDO (Version 1.2.1) and reboot exchange server
This problem occurs in case of curruption in installed MAPI client.
Above procedure has resolved my exchange problem and hope it helps you as well.
For more info
10-11-2010 12:28 AM
I just facing your problem 1 month ago. I do many thing for fix it.
1. I have deleted and create new selection list to fix it.
2. this solution is restart service before backup EVERY Mon-Fri. please try it with this script. Create .bat file and copy this code to paste it.
@echo off
echo ========================================
echo Script restart backup exec
echo ========================================
net stop "Backup Exec Agent Browser"
net stop "Backup Exec Job Engine"
net stop "Backup Exec Remote Agent for Windows Systems"
net stop "Backup Exec Server"
net stop "Backup Exec Device & Media Service"
net start "Backup Exec Agent Browser"
net start "Backup Exec Job Engine"
echo Finish logon script
echo End
Hope it will help you.
10-20-2010 09:07 AM
Sorry for going dark on this, everyone. In my case it ended up being an external virtualization issue, and not a problem with either application at all (Backup Exec or Exchange). There were some I/O issues on the VM host causing the VSS snapshot writer to time out before a snapshot could be created.
10-20-2010 09:17 AM
I had nearly the exact same issue.... it was Kaspersky Antivirus on my Hyper-v host... uninstalled, and reinstalled the AV, and the problem went away. (after months of hair pulling).