Tivoli Storage Manager system state backups cause the client to crash with exception code: 0xc0000409. A dsmcrash.dmp file may not be generated and the dsmcrash.log file may not be updated. References to the crash can be seen in the Windows Application event log.
Windows Application Event log:
Error,MM/DD/YYYY HH:MM:SS AM,Application Error,1000,(100),"Faulting application name: dsmc.exe, version: 6.X.X.X, time stamp: 0x4f6eefda
Faulting module name: dsmc.exe, version: 18.104.22.168, time stamp: 0x4f6eefda
Exception code: 0xc0000409
Fault offset: 0x0000000000367a40
Faulting process id: 0x1614
Faulting application start time: 0x01cdbe86c17aef6d
Faulting application path: C:\Program Files\Tivoli\TSM\baclient\dsmc.exe
Faulting module path: C:\Program Files\Tivoli\TSM\baclient\dsmc.exe
Report Id: 1cc9ddc9-2a7a-11e2-b430-1cc1de24d95e"
This could be cause by the following APAR: http://www-01.ibm.com/support/docview.wss?uid=swg1IC79621
If the path does not appear long enough to be caused by the APAR it could be caused by a problem in the c:\adsm.sys staging folder.
Resolving the problem
If Tivoli Data Protection products are not installed then delete the entire 'adsm.sys' folder and retry the backup. Otherwise, only entries related to the Tivoli Storage Manager client node should be removed.
***Note: It is not recommended to delete the entire adsm.sys folder due to its requirement for Tivoli Data Protection client VSS backups. If a TDP client is not installed on the machine it will be safe to delete the folder.
TSM baclient adsm