Video Screencast Help

OFO: Initialization failure

Created: 26 Jan 2005 • Updated: 21 May 2010 | 6 comments

Getting error on Diff backups; (OFO: Initialization failure on: "shadow?copy?components". Adnvanced open file option used: Microsoft volume shardow copy service (vss). VSS snapshot error. unexpected provider error.

I do not have OFO installed on the backup server.
OS: Win 2003

Comments 6 CommentsJump to latest comment

Varsha's picture

Refer the following document :



http://support.veritas.com/docs/265927
(the technote is applicable for v10.0)

Sagar Kamat 2's picture

To troubleshoot this error, please perform the following steps immediately after a failed Shadow Copy Components backup has been identified:

1. Open a command prompt on the server in question

2. Type the following command: VSSADMIN LIST WRITERS

3. Review the output and identify the Last Error failure status for the specific VSS Application Writer that was involved in the data protection operation.

Ensure that the writers are all showing a State of " Stable" and that Last Error is showing "No error."
If Last Error states:

- Retryable Error, then retrying the data protection backup operation might resolve the VSS Application Writer's initial failure

- Non-Retryable Error, view the Event Viewer's Application Log for information regarding the cause and possible solution to this issue.

4. If the VSS Application Writer failure does not reset after a period of time then we suggest you to reboot the server being backed up and perform a backup of Volume Shadow copy components using NTbackup.



5. Subsequent backups using Backup Exec may complete successfully.



If the issue remains unresolved, please let us know.

dharden26's picture

I have received the same error and I performed vssadmin list writers and this is what I got. Only one state is Stable, the rest are all Failed. What do I do next?



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

Eric Kirscher's picture

I get the same error but I've completely uninstalled the agent, removed it all manually from the registry, restarted the server, reinstalled the client and rebooted again. I still get the same VSS error and my results of running the list writer command:


Microsoft Windows
(C) Copyright 1985-2003 Microsoft Corp.

VSSADMIN LIST WRITERs
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {624ab1fd-f1fb-42e9-9da3-860018e890db}
State: Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {ca11f258-3cac-4d8b-84b7-9e947dfd4be8}
State: Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {94899c71-aba7-4e45-9974-5def2e023d02}
State: Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {b83f2141-9e45-4daf-9c7e-77e511633fb9}
State: Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {ac52fafd-d811-4d44-bb54-c2d31b401838}
State: Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {e17b3d4c-679d-45b7-829b-d211824ade87}
State: Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {469ef86b-dbdd-46d6-8cee-e16d58821304}
State: Stable
Last error: No error

Eric Kirscher's picture

Here is the error in event viewer:

Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is supported. .