OFO: Initialization failure
I get these messages when I run a backup.
OFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
OFO: Snapshot error (0xfffffed1): A failure occurred querying the Writer status.
I ran a vssadmin list writer in the command prompt and got this:
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {b4a29760-d927-4c22-a8e9-4518ce205d8d}
State: Failed
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {a8e53e84-e238-4b22-807c-693e5d0bee55}
State: Failed
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {f49b3cd8-6b61-4fdb-8e74-1d641d3567de}
State: Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {d5c1ef08-0a2f-44ec-99b5-ee294cec1e2e}
State: Failed
Last error: Retryable error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {5dc84ab1-733c-4aba-b1f6-5a6439457f40}
State: Failed
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f80f1a33-1015-4a61-89ef-7afc300b2152}
State: Failed
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {3e4515d6-99a0-41fe-9f1e-d622287ee17b}
State: Failed
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {10ecb44c-b18f-47f4-85bc-63bad5c64eed}
State: Failed
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {187990d3-733d-4375-9f70-cb3b51d91d73}
State: Failed
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {6613bb9a-876e-4971-bf1c-e3a63733424d}
State: Failed
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {5e631d15-cd9d-41cb-ad8b-56ed7a60a3bb}
State: Failed
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {16220fbf-bb8b-4037-9fb4-21991722f2dd}
State: Failed
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {3307a5cc-0b78-4435-bba3-3902ead7d62e}
State: Failed
Last error: No error
What do I do next?
Comments 6 Comments • Jump to latest comment
Please refer to the technote given below:
How to troubleshoot the error "A failure occurred querying the Writer status" (a000fed1 HEX or e000fed1 HEX) using VSSADMIN :
http://support.veritas.com/docs/261993
Microsoft has a hotfix for VSS that may fix this error message:
http://support.microsoft.com/default.aspx?scid=kb;...
Hi,
Kindly update us on the issue.
The hotfix resolved the issue I had with vssadmin. The job is still failing though. These are the errors I get now.
Backup - \\FSTRATSERVER\Microsoft Information Store\First Storage Group Error, Unable to open \ because it is currently being backed up by another process.
Database or database element is corrupt
Error, Unable to open \ because it is currently being backed up by another process.
Database or database element is corrupt
Error, Unable to open \ because it is currently being backed up by another process.
Database or database element is corrupt
Backup - Shadow?Copy?Components Shadow?Copy?ComponentsA failure occurred querying the Writer status.
The First Storage Group is not being backed up by anything else, so it must be corrupt. I have been unsuccessful in finding anything to correct this, to uncorrupt this database.
Hi,
Refer to the following technote to resolve the issue:
http://seer.support.veritas.com/docs/265159.htm
In reference to our previous reply to your post, we would request you to update us on the progress. However, if we do not receive your intimation within two business days, this post would be âassumed answeredâ and archived.
I decided to do an offline defrag of my Exchange mailboxes and was able to it successfully. I tried a backup and it failed with the reason being the drive wasn't clean. I cleaned it and haven't had the chance to run a backup since. I will start a new thread if I have any other issues. Thank you.
Would you like to reply?
Login or Register to post your comment.