cancel
Showing results for 
Search instead for 
Did you mean: 

AOFO: Initialization failure on: "System?State".

winbesadmin
Not applicable
Hi,

I've been getting this error message for the last 2 weeks and even though I've applied the fix recommended by MS and Symantec, the problem persist. The only workaround we have is to reboot the server before running the backup jobs.

The error is the following:

Backup- LYDMTLDTA01V-79-57344-34110 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.

Here is the system information:

Windows 2003 Standard R2 Service Pack 2
Symantec Backup Exec 12 for Windows Servers version 12.0 Rev. 1364 (Service Pack 3, Hot Fix 317974, Hot Fix 319698)
Mc Afee VirusScan Enterprise 8.5.0i
Diskeeper 2007 Server (11.0.703.0)

What I've done so far:

Applied latest VSS patch KB940349-v3.

Verified the Shadow Storage:

C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Shadow Copy Storage association
For volume: (C:)\\?\Volume{e7c3dd96-c8d0-11db-9dc1-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{e7c3dd96-c8d0-11db-9dc1-806e6f6e6963}\
Used Shadow Copy Storage space: 1.629 GB
Allocated Shadow Copy Storage space: 1.907 GB
Maximum Shadow Copy Storage space: 9.766 GB

Shadow Copy Storage association
For volume: (D:)\\?\Volume{dff7b54c-d0da-11db-82d8-0018fe898886}\
Shadow Copy Storage volume: (D:)\\?\Volume{dff7b54c-d0da-11db-82d8-0018fe898886}\
Used Shadow Copy Storage space: 6.885 GB
Allocated Shadow Copy Storage space: 7.119 GB
Maximum Shadow Copy Storage space: 9.766 GB

Please help...
1 REPLY 1

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Reapply your RAWS agent on that particular server, and restart the service.
Also make sure that the account you are using has admin rights on that server.