QO20824 AFTER CRASH, PREV RUNNING JOBS SHOW ACTIVE (ASCORE.DLL)
QO22840 EXCHANGE CUMULATIVE BRICK LEVEL UPDATE (Dbaxchg2.DLL)
QO19666 FIX REGISTRY KEY HANDLE LEAK (aslog.dll)
QO27941 ARCSERVE CAN NOT RECOGNIZE NEW INSERTED MEDIA (asbackup.dll)
QO23827 LOCAL BACKUP JOB HANGS savcfg.dllQO27928 CUSTOM SCHEDULED JOB CAN NOT APPEND TO TAPE (astask.dll)
QO28915 DEVICE SUPPORT
------------
Since applying above fixes we have experienced the following problems on a select handful of some 22+ servers (once a problem has returned it remains to haunt for months despite around the clock fixing & manually checking logs because the Enterprise Reporting is random at best):
Appeared to fix jobs crashing for no apparent reason (though always around 'documents&settings' - this error has now come back to haunt us.
jobs not stopping - fixed then back to haunt
blank job logs for successful backups but may or may not include bricklevel logs (Activity log is fine)
W3831 Unable to find any media & W3832 Unable to find a blank media - erasing media will allow job to run (This appears to be very new and is different from the 'Unable to recognize new media' problem in the hotfix above.)
Not backing up the Information Store with no errors or any dbaxchis activity in job log or activity log yet bricks work perfectly. Again, this is new (postSP4) problem for us but appears to be similar to preSP4 problem elsewhere in the forum (though that stated error 'unable to enumerate database)
(ARCserve)Database not backed up :E3511 Unable to begin database backup (EC=-1)
- Again, appears to be new, this happens at the very end so is not to bad but does cause the job to remain in ACTIVE state and will prevent other jobs from running without manually stopping then restarting Job (& DB engine for good measure)
Brick failed "E8601 unable to connect with client DBagentexch EC=402" - Support doc is utter tosh - A reboot of both Exchange & ARCserve boxes appears to be the only way to get rid of this much underdocumented error.
QO22840 EXCHANGE CUMULATIVE BRICK LEVEL UPDATE (Dbaxchg2.DLL)
QO19666 FIX REGISTRY KEY HANDLE LEAK (aslog.dll)
QO27941 ARCSERVE CAN NOT RECOGNIZE NEW INSERTED MEDIA (asbackup.dll)
QO23827 LOCAL BACKUP JOB HANGS savcfg.dllQO27928 CUSTOM SCHEDULED JOB CAN NOT APPEND TO TAPE (astask.dll)
QO28915 DEVICE SUPPORT
------------
Since applying above fixes we have experienced the following problems on a select handful of some 22+ servers (once a problem has returned it remains to haunt for months despite around the clock fixing & manually checking logs because the Enterprise Reporting is random at best):
Appeared to fix jobs crashing for no apparent reason (though always around 'documents&settings' - this error has now come back to haunt us.
jobs not stopping - fixed then back to haunt
blank job logs for successful backups but may or may not include bricklevel logs (Activity log is fine)
W3831 Unable to find any media & W3832 Unable to find a blank media - erasing media will allow job to run (This appears to be very new and is different from the 'Unable to recognize new media' problem in the hotfix above.)
Not backing up the Information Store with no errors or any dbaxchis activity in job log or activity log yet bricks work perfectly. Again, this is new (postSP4) problem for us but appears to be similar to preSP4 problem elsewhere in the forum (though that stated error 'unable to enumerate database)
(ARCserve)Database not backed up :E3511 Unable to begin database backup (EC=-1)
- Again, appears to be new, this happens at the very end so is not to bad but does cause the job to remain in ACTIVE state and will prevent other jobs from running without manually stopping then restarting Job (& DB engine for good measure)
Brick failed "E8601 unable to connect with client DBagentexch EC=402" - Support doc is utter tosh - A reboot of both Exchange & ARCserve boxes appears to be the only way to get rid of this much underdocumented error.