Fixed issue, caused by misconfiguration in AD LDS instance.
thank you all.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi every One,
I have this issue when I launch the script to backup AD LDS instance with cmd line dsdbutil:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to 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: {dd846aaa-a1b6-42a8-aaf8-03dcb6114bfd}
Writer Name: ADAM (GED085) Writer
Writer Instance ID: {bbac10fb-5c90-49d2-821b-b71c5a00db11}
Command Line: C:\Windows\System32\dsamain.exe -sn:GED085
Process ID: 15784
I chked the VSS and I found ins't stable:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Provider name: 'Hyper-V IC Software Shadow Copy Provider'
Provider type: Software
Provider Id: {74600e39-7dc5-4567-a03b-f091d6c7b092}
Version: 1.0.0.0
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
C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 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: {b698091f-8055-4825-953d-c53fc8c7674d}
State: [5] Waiting for completion
Last error: No error
Writer name: 'ADAM (GED077) Writer'
Writer Id: {dd846aaa-a1b6-42a8-aaf8-03dcb6114bfd}
Writer Instance Id: {1f70ae5c-67e8-426f-9eaa-3ecc392014d7}
State: [11] Failed
Last error: Non-retryable error
please help!!!
Fixed issue, caused by misconfiguration in AD LDS instance.
thank you all.
Hi,
Do you mean it failed when you use dsdbutil to backup AD LDS instance? If there is any misunderstanding, please feel free to let me know.
Please change the "Log On" account for the service from "Local System account" to a domain administrator account.
Please make sure that your server is fully patched.
If you use WSB to backup the AD LDS, will it work?
Thanks for your time!
Best Regards,
Mico Mi
-----------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.