VSS Fails during SystemState Backup and Open File Support

I am running a Windows 2008 x64 R2 standard server.  This server has 2 x 1TB drives that are setup as Raid 1 (mirror) using Window's software raid via Disk Management. Both Disk 0 and Disk 1 are setup as dynamic disks. We are using Tivoli Storage Manager to backup the server.  Everytime we try to do a systemstate backup or backup the indivdual drives with open file support, VSS fails and spits out the following errors in TSM's dsmerror.log file:

06/14/2012 05:59:12 ANS5250E An unexpected error was encountered.
   TSM function name : StartSnapshotSet()
   TSM function      : 'StartSnapshotSet() failed with error VSS_E_SNAPSHOT_SET_IN_PROGRESS. -2147212522'
   TSM return code   : -2147212522
   TSM file          : asrutil.cpp (1918) 
06/14/2012 05:59:12 ANS1468E Backing up Automated System Recovery (ASR) files failed.  No files will be backed up.

06/14/2012 05:59:14 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
06/14/2012 05:59:44 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
06/14/2012 06:00:14 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
06/14/2012 06:00:44 ANS1327W The snapshot operation for 'D:' failed with error code: 653.
06/14/2012 06:00:44 Return code 653 unknown
06/14/2012 06:00:44 Unknown system error
Please check the TSM Error Log for any additional information
06/14/2012 06:00:44 Return code 653 unknown
06/14/2012 06:00:44 Unknown system error
Please check the TSM Error Log for any additional information
06/14/2012 06:00:44 ANS1377W The client was unable to obtain a snapshot of '\\u16247921\d$'. The operation will continue without snapshot support.

After going through IBM's support channels, it was discovered that this was a Microsoft issue, as even running a systemstate backup using the Windows Server Backup tool fails with the following errors showing up in the event log:

The backup operation that started at '‎2012‎-‎06‎-‎15T23:10:50.465000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348075'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({e6ad9a3c-706a-4c97-9354-65be87f4e187}) [hr = 0x800706be, The remote procedure call failed.
]. 

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet

When I run a "vssadmin list writers" command I get the following output:

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {6c358ef9-c975-4fe6-96ba-a28710a1eaf6}
   State: [7] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {a7a3b9fe-3a1d-454e-95b5-076142d70a2c}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {5e225f9c-af8e-4cb5-b04f-5630d4906057}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {ac277156-d435-490c-9c1b-1357dd7455b5}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {def41fc8-83f8-417f-af7f-ad80ca440dd4}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {c2614332-716d-4734-8c36-bdfbb61748b2}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {bb2fd48c-967a-476d-a2ab-5fad1d238ece}
   State: [7] Failed
   Last error: Timed out

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {612a30b0-6d2c-4652-b933-10bf32635e70}
   State: [7] Failed
   Last error: Timed out

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {fee5672a-7b21-4da7-934a-84cc336c0605}
   State: [7] Failed
   Last error: Timed out

I've tried re-registering the writers as suggested in other posts, as well rebooting, but the problem persists. Any help would be most appreciated as I've exhausted most suggestions I've found in the forums.