| Previous | Next |
| VSS_E_WRITER_INFRASTRUCTURE | VSS_E_WRITER_ALREADY_SUBSCRIBED |
VSS_E_WRITER_NOT_RESPONDING
VSS_E_WRITER_NOT_RESPONDING means that a writer did not answer a GatherWriterStatus request. The writer may have stopped, become stuck, or be unable to communicate with VSS.
How to investigate for VSS_E_WRITER_NOT_RESPONDING
- Use
vssadmin list writersto identify the writer name, state, and last error. - Check the related application service, process health, and Application or System events.
- Restart or repair the affected writer's application component according to vendor guidance, then rerun the VSS workflow.
Diagnostic interpretation
This result has the HRESULT value 0x80042319. AllStat records the condition as “A writer did not respond to a GatherWriterStatus call. The writer may either have terminated or it may be stuck. Check the System and Application event logs for more information.”.
Evidence to capture
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions this result or the vss / writer / responding operation.
- Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original vss / writer / responding condition.
Retry and recovery
Retry this result only when the owning API documents a transient state or after the condition described as “A writer did not respond to a GatherWriterStatus call. ” has changed.
Looking for a different code? Search another status or error code.