{"id":2924,"date":"2017-10-27T00:35:24","date_gmt":"2017-10-27T00:35:24","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=2924"},"modified":"2017-11-17T19:37:23","modified_gmt":"2017-11-17T19:37:23","slug":"veeam-writers-state-vss_ws_failed_at_prepare_snapshot-error-code-0x800423f4","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/fixes\/veeam-writers-state-vss_ws_failed_at_prepare_snapshot-error-code-0x800423f4","title":{"rendered":"Veeam Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]"},"content":{"rendered":"

A Server 2012 R2 started getting VSS Writer Errors randomly in Veeam backup job. The server is running AADconnect which is set to autoupdate<\/p>

A restart of the VSS SQL Writer which usually fixes this did not resolve the issue.<\/p>

A look in the event log shows<\/p>

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,<\/strong>
the error is likely to reoccur.<\/strong>
. 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.<\/strong><\/p>

Operation:<\/strong>
PrepareForSnapshot Event<\/strong><\/p>

Context:<\/strong>
Execution Context: Writer<\/strong>
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}<\/strong>
Writer Name: SqlServerWriter<\/strong>
Writer Instance Name: SQL Server Code-Named ‘Denali’ CTP2:SQLWriter<\/strong>
Writer Instance ID: {6c73bfe9-f82f-4854-bec4-4382c314a583}<\/strong>
Command Line: “C:\\Program Files\\Microsoft SQL Server\\90\\Shared\\sqlwriter.exe”<\/strong>
Process ID: 4292<\/strong><\/p>

With some<\/p>

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=4292. Thread=3940. Client. Instance=LOCALDB#SHDA41B2. VD=Global\\{9C831400-DE4D-4364-BA22-A8299CF545FC}4_SQLVDIMemoryName_0.<\/strong><\/p>

Looks like you need to download the SQL Fix from here :\u00a0https:\/\/support.microsoft.com\/en-us\/help\/2983175\/cumulative-update-package-2-for-sql-server-2012-sp2<\/a><\/p>

Mirror Here :\u00a0https:\/\/mega.nz\/#!3AZ3gK7I!kDPhnAlur4XtslKxGXwmbnLitJiwN9R6rK-z4Rh0N-s<\/a><\/p>

 <\/p>

**Update , fix does not seem to work<\/p>

A repair on the SQL database and then run the below script<\/p>

Looks like this might be an issue with AADcoonect<\/p>

https:\/\/github.com\/pariswells\/pariswells.com\/blob\/master\/fixaadconnectvsswriter.ps1<\/a><\/p>

 <\/p>

**Update<\/p>

\u00a0ADSync launches an SQL Server Local DB under it\u2019s own user account
\u2013 The User Profile Service thinks ADSync is no longer logged on, and unloads the registry
\u2013 SQL Server though still has handles to the registry, but they\u2019re invalid now<\/p>

Detailed explanation:
https:\/\/support.microsoft.com\/en-us\/help\/2287297\/a-com-application-may-stop-working-on-windows-server-2008-when-a-user<\/a><\/p>

In short: Computer Configuration->Administrative Templates->System->User Profiles->Do not forcefully unload the user registry at user logoff<\/p>","protected":false},"excerpt":{"rendered":"

A Server 2012 R2 started getting VSS Writer Errors randomly in Veeam backup job. The server is running AADconnect which is set to autoupdateA restart of the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[2192,2193,1886,2198,591,739],"class_list":["post-2924","post","type-post","status-publish","format-standard","hentry","category-fixes","tag-0x800423f4","tag-2193","tag-2012-r2","tag-aadconnect","tag-sql","tag-veeam"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t