VSS Error Event id 8193 - 0x80070539

I keep getting VSS Error with event id 8193 for several weeks now:
ConvertStringSidToSid
0x80070539
Operation: OnIdentify event Gathering Writer Data Context:
Execution Context: Shadow Copy Optimization Writer Writer Class Id:
{4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Name: Shadow Copy Optimization Writer Writer Instance ID:
{bd32726a-3d40-4c27-9282-2af7d5cff0a5}
Any ideas?

Noting much just hoping somebody with the right knowledge is going to give me a light ...
All public VSS resolutions relate to Server 2003 and hence do not work here.
Also I have reformulated the issue slightly:
Vista SP1 - VSSadmin List Writers reveals one writer missing:
Shadow Copy Optimization Writer is not listed.
Creating a restore point causes VSS Error with event id 8193
>> ConvertStringSidToSid
>> 0x80070539
>> Operation: OnIdentify event Gathering Writer Data Context:
>> Execution Context: Shadow Copy Optimization Writer Writer Class Id:
>> {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
>> Writer Name: Shadow Copy Optimization Writer Writer Instance ID:
>> {bd32726a-3d40-4c27-9282-2af7d5cff0a5}
However, restore point creation is succesful.
There must be another way but reinstalling the entire OS and everything else on top from scratch ...

Similar Messages

VSS error 8193 and 22 by backup task (Windows server 2012)

Hello,
On the WinServer 2012 Std , I am facing VSS error when it starts "system state backup".
The user account of this task is a member of "local Backup operators".
how can I correct this error ?
In the forum, I found a topic that had mentioned regsvr32.
But Microsoft said it does not recommended/ supported for 2008 or later.
http://social.technet.microsoft.com/Forums/office/en-US/2b1f44e0-725a-4fc5-bc1d-69437871fe90/wierd-volume-shadow-copy-service-errors?forum=winserverfiles
-Quote [start]-
Reregistering files was a common way to fix VSS issues back in Windows 2003. However, due to the changes in Windows 2008 and 2008R2 servicing, reregistering files will either not work or actually damage Windows.
Please discontinue using
regsvr32.
Robert Mitchell Senior Support Escalation Engineer Microsoft Corp.
-Quote [End]-
the detail of event logs are ;
Log Name:      Application
Source:        VSS
Event ID:      22
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:
Description:
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance
on class with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered ].
Log Name:      Application
Source:        VSS
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
hr = 0x80040154, Class not registered .
Thank you for your support.

Dear Sophia,
Thank you for your instruction, the below is result of vssadmin.
I am using CA Arcserve 16.5 for backing up system state.
Writers
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
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: {540ecfcf-7f41-43cc-9521-d73d1881b85f}
    State: [1] Stable
    Last error: No error
Writer name: 'SqlServerWriter'
    Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
    Writer Instance Id: {1fe1e4af-26ab-4113-8079-2c853e1a32fc}
    State: [1] Stable
    Last error: No error
Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {8094a9a6-29e1-4276-a8b0-7f9bd34e7ad5}
    State: [1] Stable
    Last error: No error
Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {3812a483-5e46-4c06-a64d-4caa1184705e}
    State: [1] Stable
    Last error: No error
Writer name: 'IIS Config Writer'
    Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
    Writer Instance Id: {094ddb56-3e9a-452f-951a-22da278d7666}
    State: [1] Stable
    Last error: No error
Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {4f57f2af-4a0e-443d-ac27-c9b858c50744}
    State: [1] Stable
    Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {54fb8f5c-2dff-479d-8ed1-b7de3c7495c3}
    State: [1] Stable
    Last error: No error
Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {901cd0a6-895a-4942-ac60-c8a6a7796583}
    State: [1] Stable
    Last error: No error
Providers
C:\Windows\system32>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Provider name: 'SmVssProvider'
    Provider type: Hardware
    Provider Id: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
    Version: 10.84.02
Provider name: 'Microsoft File Share Shadow Copy provider'
    Provider type: Fileshare
    Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
    Version: 1.0.0.1
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
    Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
    Version: 1.0.0.7
Shadows
C:\Windows\system32>vssadmin list shadows vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
^C
Since command prompt has no output for 5mins, I pressed CTRL+C
Shadowstorage
C:\Windows\system32>vssadmin list shadowstorage vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
No items found that satisfy the query.
Volumes
C:\Windows\system32>vssadmin list volumes vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Volume path:
\\?\Volume{d2760d78-5868-11e3-93e7-806e6f6e6963}\
     Volume name:
\\?\Volume{d2760d78-5868-11e3-93e7-806e6f6e6963}\
Volume path: D:\
     Volume name:
\\?\Volume{88a134c9-020e-4020-8697-dc44c8a3c89a}\
Volume path: C:\
     Volume name:
\\?\Volume{d2760d79-5868-11e3-93e7-806e6f6e6963}\
C:\Windows\system32>

VSS errors 8193, 22, and 12292

We have a Windows 2012 standard server, and once we renamed the server, we started getting the following VSS errors - 8193, 22, and 12292. How can I fix this? The errors are listed below. Thanks in advance!
Error 8193 - Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154, Class not registered
Error 22 - Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned
from CoCreateInstance on class with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered

Hi,
Please run "vssadmin list writers" to see if you can find System Writer?
If no system writer, try to run the command in command prompt:
SC.EXE SDSHOW EVENTSYETEM
• If the output is like below, that means it is missing the Service Logon User (missing the entry (A;;CCLCSWLOCRRC;;;SU) )
D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
• Then you can reset the eventsystem permission:
Sc.exe sdset eventsystem D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
• Restart both the COM+ Event System and Cryptographic Services
• Run VSSADMIN LIST WRITERS again and see if system writer is back.
NOTEs:If the problem on your side is indeed related to service permission, you can check the GPO setting on your side to see if there is any change on the COM+ Event System Service.
If you have any feedback on our support, please send to [email protected]

Large number VSS errors "The specified network resource or device is no longer available."

I have a 2 node Hyper V Cluster backed up via Veeam Off-Host Proxy. I've already logged, without answer, a thread about the Off-Host Proxy server randomly (I guess) creating new duplicate iSCSI connections.
Today I have a single VM that won't backup. On inspection through the hosting servers Application Log I see a high amount of VSS errors being logged which I believe is possibly related to the iSCSI issue being logged by the SAN.
I'm not sure how to "show" the issue without a giant wall of the events but there is like half a dozen different events being logged when whatever this is is happening. For instance as well last night 60/61 VMs backed up find, but these errors
were logged constantly while the backup ran...
The question as well is is this a Windows/VSS issue, a Veeam issue or a Equallogic issue?
Also how do I find what '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'. actually is?
In order of how they come I guess:
Log Name: Application
Source: VSS
Date: 6/01/2015 7:28:19 AM
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: HOST02.domain.private
Description:
A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {881f5207-f769-4b40-986a-c6bd56d8aa1e}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 3268
Log Name: Application
Source: VSS
Date: 6/01/2015 7:29:31 AM
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOST02.domain.private
Description:
Volume Shadow Copy Service error: Unexpected error calling routine Error calling CreateFile on volume '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'. hr = 0x80070037, The specified network resource or device is no longer available.
Operation:
Check If Volume Is Supported by Provider
Context:
Execution Context: Coordinator
Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\
Log Name: Application
Source: EqualLogic
Date: 6/01/2015 7:29:43 AM
Event ID: 4001
Task Category: VSS
Level: Error
Keywords: Classic
User: N/A
Computer: HOST02.domain.private
Description:
iSCSI logout error 0xEFFF0040 from target NULL.
Log Name: Application
Source: VSS
Date: 6/01/2015 7:29:43 AM
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOST02.domain.private
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details OnLunStateChange(\\?\mpio#disk&ven_eqlogic&prod_100e-00&rev_7.0_#1&7f6ac24&0&363846433631363644434545463233334146344141353632363038303136#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})
failed with error 0xefff0040 [hr = 0xefff0040].
Operation:
Notifying hardware provider to free a drive
Break with LUN mask
Delete Shadow Copies
Processing PostFinalCommitSnapshots
Executing Asynchronous Operation
Context:
Volume Name: \\?\mpio#disk&ven_eqlogic&prod_100e-00&rev_7.0_#1&7f6ac24&0&363846433631363644434545463233334146344141353632363038303136#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}
Snapshot ID: {3091377b-2e26-43ed-a11b-f31adbde0b1f}
Execution Context: Provider
Provider Name: Dell EqualLogic VSS HW Provider
Provider Version: 4.7.1
Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Snapshot Context: 4194336
Provider Name: Dell EqualLogic VSS HW Provider
Provider Version: 4.7.1
Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Current State: DoSnapshotSet
Log Name: Application
Source: VSS
Date: 6/01/2015 7:29:43 AM
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOST02.domain.private
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details could not free LUN [hr = 0x8004230f, The shadow copy provider had an unexpected error while trying to process the
specified operation.
Operation:
Break with LUN mask
Delete Shadow Copies
Processing PostFinalCommitSnapshots
Executing Asynchronous Operation
Context:
Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}
Snapshot ID: {3091377b-2e26-43ed-a11b-f31adbde0b1f}
Execution Context: Provider
Provider Name: Dell EqualLogic VSS HW Provider
Provider Version: 4.7.1
Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Snapshot Context: 4194336
Provider Name: Dell EqualLogic VSS HW Provider
Provider Version: 4.7.1
Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Current State: DoSnapshotSet
(Below logged 3 times)
Log Name: Application
Source: VSS
Date: 6/01/2015 7:29:49 AM
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOST02.domain.private
Description:
Volume Shadow Copy Service error: Unexpected error calling routine Error calling CreateFile on volume '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'. hr = 0x80070037, The specified network resource or device is no longer available.
Operation:
Check If Volume Is Supported by Provider
Context:
Execution Context: Coordinator
Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\

This is the issue having with redundant iSCSI connections being created:
Not sure this is a Veeam issue, just that it's occurring with Veeam backup process.
We have a server configured as an Off-Host Proxy with Veeam; it connects to the SAN storage via iSCSI same as the other hosts but accesses the storage as read only.
Randomly we will get alerts from the SAN as below:
iSCSI login to target '172.16.0.50:3260, iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1-2015-01-03-14:13:37.2774.1' from initiator '172.16.0.44:64108, iqn.1991-05.com.microsoft:arcbackproxy.domain.local' failed for the following reason:
Requested target not found.
On inspection of the Off-Host Proxy's iSCSI configuration additional iSCSI connections are present as inactive, with an existing connections name amended with the date at the end. For instance (and in the example error above) there will be:
iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1
and
iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1-2015-01-03-14:13:37.2774.1
Not really causing an issue, the backups are running OK, or any issues we have aren't related. But getting annoying getting the alerts from the SAN of the Off-Host Proxy trying to connect to an incorrect iSCSI target.
Any ideas why this is occurring?
Obvious is we delete the extra connection, which stops the alert, but the issue will reoccur within a day or two usually.
Today I found twice the alert as above and sure enough the iSCSI on the Off-Host Proxy is as below:
Maybe these redunandant connections being created is related? Maybe that's the where the "The specified network resource or device is no longer available." is coming from or something?

VSS Error: "An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes."

Hi all,
at a customer’s site I’ve a problem with a fresh installation of Backup Exec 2014. Every backup (full or incremental) always reports the following
error: “An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes.”.
It’s not a Backup Exec problem itself, also backups using “Windows Server Backup” failing with the same error.
On this site I have three servers; the error is only generated for one of them. Here’s a short overview:
Server1: Windows Server 2012 R2, latest patchlevel, physical machine, Domain Controller and Fileserver. Backup Exec is installed on this machine,
backup is written directly to SAS tape loader. There error is generated on this server.
Server2: Windows Server 2008 R2, latest patchlevel, virtual machine, running on Citrix Xen Server 6.2. Used for remote desktop services, no errors
on this server.
Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server.
As I said, error is reported only on server1, no matter if it is a full or an incremental backup. During the backup I found the following errors
is the event log (translated from a german system):
Event ID: 12293
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider. "{89300202-3cec-4981-9171-19f59559e0f2}" an error occured. Routinedetails Error calling Query(). [0x80042302] [hr = 0x80042302, unexpected component error of
the Volume Shadow Copy Service.
Process:
Volume Shadow Copy polling
Volume Shadow Copy delete
Context:
   Executioncontext: Coordinator
   Executionkontext: Coordinator
And
Event ID: 8193
Volume Shadow Copy Service error: Unexpected error calling Routine "IVssCoordinator::Query" hr = 0x8004230f, Unexpected error Volume Shadow Copy Service Provider
Process:
Volume Shadow Copy delete
Context:
   Executioncontext: Coordinator
There are some articles about this error in the knowledge base or web which does not help or do not apply to my environment for example:
http://www.symantec.com/business/support/index?page=content&id=TECH38338&actp=search&viewlocale=en_US&searchid=1423724381707
What I already have tried:
Disabled Antivirus during the whole backup
Installed latest Service Pack for Backup Exec
Rebooted the server
vssadmin list writers do not show any errors
consult eventid.net for other possible solutions
no limits set for vaa
Anymore ideas from you guys?
Best regards,

Hi Shaon,
vssadmin list providers gave the following output:
vssadmin list providers
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.
Anbietername: "Microsoft File Share Shadow Copy provider"
   Anbietertyp: Dateifreigabe
   Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1
Anbietername: "Microsoft Software Shadow Copy provider 1.0"
   Anbietertyp: System
   Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
Unfortunately theres not Symantec VSS Provider listed.
Best regards,
Christoph

VSS Errors

Hi Guys,
I got a problem with DPM. It should backup a fileserver, but on the server it's giving several VSS errors which I can't seem to resolve. I'm hoping to find so help here.
Errors:
Event 12293
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({bda01413-9eb7-4573-a8fd-4390e9f92016}) [hr = 0x80070015, The device is not ready.
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
And:
Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-912261192-111631960-675849044-500.bak). hr = 0x80070539, The security ID structure is invalid.
Operation:
OnIdentify event
Gathering Writer Data
Context:
Execution Context: Shadow Copy Optimization Writer
Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Name: Shadow Copy Optimization Writer
Writer Instance ID: {ff342f52-88ab-4716-bf21-d281d6fb4b75}
Showing up several times in the event viewer.
As far as I know, i've tried every single solution on the internet. Registering VSS, changing MBR ID (Which makes the server unbootable).
If you guys can help me out that would be great!
Thanks.

Hi,
Have you ever tried this solution?
http://technet.microsoft.com/en-us/library/cc734302(v=ws.10).aspx
Hope it helps.
Thanks and Regards
Scorpio_Milo
MVP (File System Storage)
HP Enterprise Services: Solution Architect
Microsoft Storage Team - File Cabinet Blog
View my MCP Certifications
My Blog
Contact me

VSS Error in writer Hyper-V

I have a cluster with CSV 5 and DPM can't perform backup on only a few machines in the cluster, it apesenta VSS the following error:
The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\Máquina on MAQUINA.CLOUD04.dominio.local is inconsistent with the protected data source.
All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency
check on the farm. (ID 3106)
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
(0x800423F3))
Well investigating deeper into the Hyper-V server virtualization encounter the following errors:
Eventvwr:
SOURCE: VSS ID: 8229
A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PostSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {52a247b1-bd8e-499c-915d-314f9080e993}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 2460
SOURCE: HYPER-V-VMMS ID: 10143
Failed to delete the shadow copy (VSS snapshot) set with id '3ED86740-3BFC-4FD5-B6B6-5ADD63E87DB0' in the running virtual machine 'MAQUINA': This operation returned because the timeout period expired. (0x800705B4). (Virtual machine ID E130C3C7-D2BC-4234-BD2A-766054A163F9)
List Writers
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {52a247b1-bd8e-499c-915d-314f9080e993}
State: [11] Failed
Last error: Retryable error
Well, how did not get any results in searches, then checked the versions of the IC on client machines as clusters migrated from 2008 to 2012 some were outdated, updated them, even just to leave everything compliance.
So I decided to clear the "Backup (volume snapshot)" and now he backs up but does the same linux machines, saving the machine and causing downtime of it, and even if you are a linux machine with this option it can not perform the backup this because
it tries utilizr VSS method (I think).
Please, anyone help-me?
thanks!

Hi ,
Please refer to following similar thread :
http://social.technet.microsoft.com/Forums/en-US/be7fd80f-d2bc-4e1b-9bc2-a60af6e89e2a/dpm-faild-to-backup-hyperv-gest-vm-code-0x800423f3-id-30112?forum=dpmhypervbackup
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Server 2003 R2 VSS error.

I inherited a Windows Server 2003 R2 standard edition x86. After doing a bit of checking on it, I see it has not been backed up for some time. Drive C is handled by an Adaptec controller card and has 2 drives in Raid 1 configuration with total space of 68.2GB
with 33GB free and fragmentation of 1%. Drive D is handled by a 3Ware controller card and has 9 drives in Raid 5 configuration (8 active, 1 spare) with total space of 7.27TB with 4.65TB free and fragmentation of 1%.
When looking at either drive thru Windows explorer, properties, Shadow Copies tab it shows "Failed to retrieve volumes that are eligible for shadow copies. Error 0x8004230f: The shadow copy provider had an unexpected error while trying to process the
specified operation."
If I check thru command prompt and run vssadmin commands I get the following.
C:\Documents and Settings\Administrator>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'Symantec Software VSS Provider'
   Provider type: Software
   Provider Id: {262b716e-bb23-41b5-aaef-e2c15e767167}
   Version: 1.0
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
C:\Documents and Settings\Administrator>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: {0a076449-61f7-459b-8288-9684c8a6b860}
   State: [1] Stable
   Last error: No error
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {1f5f638e-3bc0-430b-849e-17bf69b42b64}
   State: [1] Stable
   Last error: No error
Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {1ee21ac2-2dd2-450b-87f9-e425b4ee599e}
   State: [1] Stable
   Last error: No error
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {c8b96527-9328-4ce3-92ac-6efc995dbef5}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c6e9592a-3a8a-4873-9589-4fb9072f045b}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {0c50faba-aec4-4f76-96ad-d25c0b5066ca}
   State: [1] Stable
   Last error: No error
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {76fcde0f-d18b-4936-a3f6-1dd399630101}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {5ea9ac74-036c-44f3-bf52-684784c03131}
   State: [1] Stable
   Last error: No error
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {f02d80c6-e208-4e9e-9076-3032677fe594}
   State: [1] Stable
   Last error: No error
C:\Documents and Settings\Administrator>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No items found that satisfy the query.
C:\Documents and Settings\Administrator>vssadmin list volumes
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Error: The shadow copy provider had an unexpected error while trying to process
the specified command.
Now if I look in the event log under Applications I see 2 errors showing.
Error 1
Source VSS. Event ID 12302. Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
Error 2
Source VSS. Event ID 12293. Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::QueryVolumesSupportedForSnapshots(ProviderId,29,...) [hr = 0x8000ffff].
Checking error 1 event id 12302 is says to make sure COM + is set to Automatic. It is set to automatic and is running. It also says to command prompt vssadmin list writers and verify none are reporting errors. None are reporting an error. It also
says to check volume shadow copy in services. Start up set to manual, which it is and it will run with no problems.
Checking error 2 event id 12293 it says to use vssadmin create shadow for each provider. If I do that I get the same errors.
I have done a lot of research on this and found 3 hot fixes from Microsoft. None of the 3 apply to the error messages that I am getting. But to give it a good try, I have applied all 3 hot fixes and none made it better, and none made it worse (different
error messages). I have also tried the following
cd /d %windir%\\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
regsvr32 Vssapi.dll
regsvr32 Vssui.dll
net start vss
net start swprv
The only errors I get when doing this is the following.
"msxml4.dll not found" I understand this as my system now has msxml6 and in doing some research msxml6 and msxml4 are not compatible and msxml6 replaced msxml4, so I can live with that, I guess.
"Vssapi.dll was loaded, but the DllRegisterServer entry point was not found. The file cannot be registered."
I am at a loss. Does anyone have any suggestions

Hi,
Do you install Symantec on your server? If so, please try to remove the entries of Symantec from system to check the result.
In the meantime, please try the steps listed in the following article to see if it can help:
Error message when you run the "vssadmin list writers" command on a Windows Server 2003-based computer: "Error: 0x8000FFFF"
http://support.microsoft.com/kb/940184
Please note, you need to backup the registry before making any changes to it.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DPM 2012 VSS Errors

We have our DPM 2012 R2 installation on Windows 2008 R2 servers. We encounter failures some of the time on our Full Express Backups on Friday evenings where we get VSS errors in the event logs.
Event 12298
Event 12289
We haven't encountered these issues until recently. Is there any idea on how to remedy these. I just installed DPM 2012 R2 this week so I am hoping it helps. But does anyone know if there is a hotfix or something for this in case it does not. I read about
these events having a hotfix for Windows 2003 servers but not Win2K8?

Event 12289
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{XXXXXXX]). hr = 0x80070057, The parameter is incorrect.
Operation:
Processing EndPrepareSnapshots
Context:
Execution Context: System Provider
Event 12298
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{XXXXXXXXX}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000, The operation completed successfully.
], Flush[0x00000000, The operation completed successfully.
], Release[0x00000000, The operation completed successfully.
], OnRun[0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.

SBS 2003 SP2: VSS errors; unable to create system state backup (NTBACKUP)

NTBACKUP system state on W2k3 server fails after "thinking" for ~10 mins and "creating" shadow copy; almost no disk activity, almost no CPU load. Errors in the Application
log:
Source: SQLVDI EventID: 1
Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3392. Thread=29348. Client. Instance=. VD=Global\{9B35142B-C687-4766-9707-BC387534BA38}1_SQLVDIMemoryName_0.
Several of them.
Then:
EventID: 8019
Source: NTBackup
End Operation: Warnings or errors were encountered.
Consult the backup report for more details.
Then:
Source: VSS
EventID: 12305
Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9,0xc0000000,0x00000003,...).
And finally:
EventID: 12293
Source: VSS
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PostFinalCommitSnapshots({de0d580b-68ce-4eae-a046-b5b5b7a80235}, 1) [hr = 0x80042308].
When creating shadow copy on the system volume, the operation may take ~40-90 mins. On the data volume -- <1 min.
"vssadmin list writers" shows:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'SqlServerWriter'
State: [10] Failed
Last error: Retryable error
Writer name: 'MSDEWriter'
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'NTDS'
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Event Log Writer'
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Certificate Authority'
State: [10] Failed
Last error: Retryable error
Writer name: 'WINS Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Registry Writer'
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
State: [10] Failed
Last error: Retryable error
Writer name: 'WMI Writer'
State: [10] Failed
Last error: Retryable error
Here is what I tried to do:
1. Restarted that thing.
2. Cleaned the security log.
3. Installed Windows Server 2003 Hotfix rollup KB940349-v3.
4. Stopped both SBSMONITORING and SHAREPOINT instances of MSDE, SQL 2005, SQL 2005 VSS and tried to perform the system state backup then. Stopped Exchange 2003 before launching NTBACKUP as well.
5. "regsvr32 sqlvdi.dll" in MSDE directory.
6. Renamed "System Volume Information" on all volumes and VSS has re-created them.
7. chkdsk /f was fun on all volumes, no major issues found.
8. Installed Hotfixes KB967551, KB975928-v2 (someone recommended).
9. Disabled SQL Server VSS Writer (SQLVDI errors disappeared from the application event log, VSS and NTBACKUP errors stayed).
10. Re-registered the DLLs as per Shaon Shan's post at http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/346fa42c-a476-457f-bcf3-59f87e444b55
The above had no effect on the issue whatsoever, except a little change at item 9 as mentioned.

Hi there.
I just had that problem. I saw friday my backup from my sbs 2003, was not completing becasuse it said it couldn´t creat a shadow copy in the external drive... It kept giving me errors os VSS and Volsnap... But strange thing is, i have VSS turned off in all
drives, and from months no problems with backups... So i went in Event viewer and look at it with attention, i saw a error that keep coming up from time to time (because we change the external drive form week to week). And i realize that there's a disk error
event...
Couldn´t run checkdisk from server, dont now why.. So i disconnected the drive, connected to my laptop, and ran a CheckDisk /F /X. ... It had BAD SECTORS! So i ran check disk... waited like 10-20 minutes. And then i ran it again just in case, and the 2nd
time was much more faster, like 3-6 minutes.
I disconnected from laptop, and connected to server. I went to the Backup wizard (in server managment), and press Backup now...
It hang 5-10 second in Creating Shadow copy..... And it started making the Backup :_D
I've seen all errors that were reported exactly as mine. I ran the Hotfix, all stayed the same, i followed all manual steps and still the same... and the problem was always in the external drive, which had bad sectors.
Hope it will help the next person that needs this info!

CrystalReportViewer: "Missing parameter values with implemented error event

I'm using the CrystalReportViewer in APS.net (C#), and try to display a report in it.
I've implemented the error event of the viewer to show the user a different error message than the viewer itself does.
         this.CrystalReportViewer.Error += new CrystalDecisions.Web.ErrorEventHandler(CrystalReportViewer_Error);
      protected void CrystalReportViewer_Error(object source, CrystalDecisions.Web.ErrorEventArgs e)
         var msg = "Error in CrystalReportViewer\r\n{0}".FormatInvariant(e.ErrorMessage);
         throw new InvalidOperationException(msg);
But.... Now if I want to show a report that has parameters in it, the parameter page does not appear before the report itself. How can I make my code work (without removing the implementation of the error event), so the viewer first shows the parameter page, before showing the actual report?

And in the Page_Load method:
this.CrystalReportViewer.Error += new CrystalDecisions.Web.ErrorEventHandler(CrystalReportViewer_Error);
I've done this so i can show my own error page to the user of the website. Otherwise the CRViewer shows his own error, and I do not want the user of the website to see this 'technical' error.
So i've implemented the CrystalReportViewer.Error method:
protected void CrystalReportViewer_Error(object source, CrystalDecisions.Web.ErrorEventArgs e)
   // Missing parameter values.
   var discardToShowParameterPrompt = (e.ErrorMessage.ToUpperInvariant() == "Missing parameter values.".ToUpperInvariant())
     || (e.ErrorMessage.ToUpperInvariant() == "Ontbrekende parameterwaarden.".ToUpperInvariant());
   if (discardToShowParameterPrompt)
      _Log.Debug("The parameter screen should be displayed now.");
   else
      var msg = "Error in CrystalReportViewer: {0}".FormatInvariant(e.ErrorMessage);
      throw new InvalidOperationException(msg);
If I load a report with no params in the report, the page shows immediately the report.
If I load a report with params in the report, the params page is shown, the user can enter the param values, and after pressing OK, the report is shown.
If an error occurs (for example the report cannot connect to the database), the viewer does NOT show the error (because i've implemented the _error event) but my code throws an InvalidOperationException, and this is handled by code so the error is logged to a file, and the user gets a user friendly message on the website.
If i do not implement the _error event, the user will see the technical error in the crystal reports viewer.
If I comment out the code where I'm looking for the string "Missing parameter values." (or "Ontbrekende parameterwaarden") the parameter page will not be shown, and an error will be thrown by the Crystal Reports viewer.
If I put e.handled = true in the _error event, and there is an error (for example the database cannot be found), no error will be thrown, and there is nothing to see in the viewer.
So for now the only way to get the params page is to implement the _error event the way i've done in the above code, checking the error message on a string value.

Adobe Acrobat 8 Pro Application Error Event ID 1000

Version: Adobe Acrobat 8 Pro (Updated)
Operating System: Windows XP (Sp2)
Launch Adobe Acrobat 8 Pro
Select File and open a PDF file
Popup appears: Reading Untagged Document
Then and error appears ... Adobe Acrobat 8.1 has encountered a problem and needs to close
Also receive same error when I select Edit\Preferences
Application Event log contains the following:
Application Error Event ID 1000
Faulting application acrobat.exe, version 8.1.0.137, faulting module admplugin.apl, version 3.16.128.32, fault address 0x000a7bf1.
Have uninstalled and reinstalled application...no change
Any help would be apprciated

No, I have not.
Had another laptop and used it.
Re-imaged laptop exhibiting the issue and moved on
Edward Bailey | Network Administrator | Pizza Inn, Inc
t. 469.384.5231 [email protected]

Quorum/Witness Disk Offline every 15 minutes error - Event ID 1069 - Event ID 1558

2 node active passive, 2008 failover cluster. I keep getting the following error events:
The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data. Event ID 1558
Cluster resource 'Cluster Disk 1' in clustered service or application 'Cluster Group' failed. Event ID 1069
However my quorum disk is online from what I can see. One thing I did notice is, the Quorum disk no longer has any files in it. It is just a empty drive.
I also noticed these errors are being entered every 15 minutes exactly.
I monitored the Quorum disk and it is going offline momentarily every 15 minutes.
Experts Exchange Posts indicate this is known issue and waiting for microsoft to deliver SP2? Really?
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_24751092.html
Any thoughts

support.microsoft.com/kb/2750820 - This does not resolved your issue because it applies only to the Quorum model Node and File share majority.
The issue is because of the cluster configuration corruption and cluster I checking after every 15 minute and is seeing the cluster quorum disk in failed state (actually it is not failed) but is not able to update the current state of the quorum disk.
Check for below logs in the cluster logs:
00000d84.00000f58::2014/11/18-19:04:06.805 INFO [QUORUM] Node 1: Witness Failed Gum Handler [QUORUM] Node 1
00000d84.00000f58::2014/11/18-19:04:06.805 INFO [QUORUM] Node 1: witness attach failed. next restart will happen at 2014/11/18-13:19:06.797
00000d84.00000ef8::2014/11/18-19:04:06.805 INFO [QUORUM] Node 1: quorum is not owned by anyone
Try reforming the cluster, it will resolve the issue.
Change the quorum model to Node majority and back to node and disk majority.
Stop cluster service on all the nodes and then start them back when it is stopped on all the nodes.
Thanks
Himanshu Swarnkar (MSFT)

Event Source: Application Error Event ID: 1000 (F1Server.exe)

Hi.
We regulary have an Application Error with "faulting module ntdll.dll" (see below).
And we can't find what is the problem.
Can you help us?
Windows Server 2003 R2 Eneterprise Edition Service Pack 2
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=AlwaysOff /fastdetect /PAE /3Gb
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1/11/2014
Time: 10:33:47 PM
User: N/A
Computer: MS-GARANT001
Description:
Faulting application F1Server.exe, version 7.9.0.0, faulting module ntdll.dll, version 5.2.3790.4937, fault address 0x00060c17.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 46 31 53 ure F1S
0018: 65 72 76 65 72 2e 65 78 erver.ex
0020: 65 20 37 2e 39 2e 30 2e e 7.9.0.
0028: 30 20 69 6e 20 6e 74 64 0 in ntd
0030: 6c 6c 2e 64 6c 6c 20 35 ll.dll 5
0038: 2e 32 2e 33 37 39 30 2e .2.3790.
0040: 34 39 33 37 20 61 74 20 4937 at
0048: 6f 66 66 73 65 74 20 30 offset 0
0050: 30 30 36 30 63 31 37 0060c17

Hi,
This issue may be caused by corrupted files or application conflicts. I recommend you to run "sfc /scannow" at the command prompt to check the system files. In addition, you can perform a clean boot to see if any service is causing the issue.
If the above cannot solve it, maybe you can find if there is any hotfix for the application or uninstall the application.
Best regards,
Susie

Error "Event Queue Overflowed" with the "Write file to Citadel Server"

Hello,
I can import data from a file and I can see the data
in the historical database without troubling.
But I always have this error "Event Queue Overflowed", that don't perturb my data and my application (I have just this boring message).
I have tried many things :
- increasing the size of my input buffer (-> 1.000.000, no change) : I don't think so that it's important because I've tried with a value of 100 and anyway sometimes my application works with this small value of 100.
- increasing the File_location tag size (-> 260). No change.
- My write to Citadel.cfg is in the LabVIEW folder.
Can you help me ?
Thank you.

Hi,
What version of LabVIEW DSC are you using? if it is 6.1, have you applied fixes linked below.
http://digital.ni.com/softlib.nsf/websearch/513AA4A0BB60D10086256B48006D44B5?opendocument
I have seen a similar issue at the link below.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=5065000000080000008C640000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control
Please let me know if you have read it through?
Best Regards,
Remzi A.

VSS Error Event id 8193 - 0x80070539

Similar Messages

Maybe you are looking for