Availability for the Always-On Enterprise
Datatekniker
Lurker
Posts: 2
Liked: never
Joined: Nov 02, 2017 7:59 am
Full Name: Flemming
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by Datatekniker » Nov 02, 2017 8:12 am

Hi,

To "MCZ", what version of SQLserver were you running before the upgrade ?

and did you get any new issues after the upgrade ?

mcz
Expert
Posts: 213
Liked: 26 times
Joined: Jul 19, 2016 8:39 am
Full Name: Michael
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by mcz » Nov 02, 2017 10:33 am

Previous version was 2012 Express Edition (so the basic setup which comes with installation of AD Connect) and now I see that I only installed SP1 for SQLServer 2016. In my case it worked and I didn't receive any other issues since then. Probably it is enough to repair the existing installation??

mcz
Expert
Posts: 213
Liked: 26 times
Joined: Jul 19, 2016 8:39 am
Full Name: Michael
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by mcz » Nov 02, 2017 3:46 pm

...ok I have to revert what I wrote some hours ago because the issue is still there...

scott_thomson
Lurker
Posts: 1
Liked: never
Joined: Nov 03, 2017 5:08 pm
Full Name: Scott Thomson
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by scott_thomson » Nov 03, 2017 5:18 pm

Hi all,

Not a Veeam user, but since this thread was what initially clued me in to the issue with the product we use for Hyper-V host-level backups of guests, I thought I'd chime in.

This definitely looks like a MS issue, but I haven't found any real acknowledgement of the problem anywhere from them. In hopes that we can raise the profile of the issue, I've posted to the AD Connect UserVoice as well as the MS Partner Support forums. Hopefully if you can add your voices to this, someone at MS will get involved:

https://feedback.azure.com/forums/16940 ... it-doesn-t
https://partnersupport.microsoft.com/en ... 9729458808

GregorS
Veeam ProPartner
Posts: 31
Liked: 10 times
Joined: Apr 10, 2013 12:11 pm
Full Name: Gregor Smerke
Location: Ljubljana, SI - Slovenija
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by GregorS » Nov 04, 2017 3:05 pm

Having the same issue, just subscribing to this thread, thanks.

mats.jansson
Service Provider
Posts: 6
Liked: 1 time
Joined: Mar 18, 2014 9:13 am
Full Name: Mats

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by mats.jansson » Nov 04, 2017 4:39 pm

The only solution that workt for us was to uninstall azure ad connect, install sql express (we used 2016 sp1) and reinstalled azure ad connect with option to use the manual installed express and a service account for sql (it's also working to use a sql on another server).
Mats

Datatekniker
Lurker
Posts: 2
Liked: never
Joined: Nov 02, 2017 7:59 am
Full Name: Flemming
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by Datatekniker » Nov 06, 2017 6:20 am

This works,

If you can accept that the AADconnect, is dead in the wather for a short period of time, a simple solution is this.

Use task scheduler:

1. Stop the AADconnect service shortly before the Veeambackup is set to run. (Powershell Stop-Service -DisplayName 'Microsoft Azure AD Sync')

---- The backup is running

2. Start the AADconnect again after a the backup has finished. (mine takes about 15min, so I start the service after 30min.) (Powershell Start-Service -DisplayName 'Microsoft Azure AD Sync')

Thats it.
My backup has been running 3 times this weekend without any further problems :-)

mcz
Expert
Posts: 213
Liked: 26 times
Joined: Jul 19, 2016 8:39 am
Full Name: Michael
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by mcz » Nov 06, 2017 8:08 am 1 person likes this post

Datatekniker wrote: 2. Start the AADconnect again after a the backup has finished. (mine takes about 15min, so I start the service after 30min.) (Powershell Start-Service -DisplayName 'Microsoft Azure AD Sync')
You should be able to start the service just after the snapshot has been taken (start it in the post-thaw script) because veeam releases vss-snapshot after vmware snapshot (if you are not indexing the filesystem).

bdufour
Enthusiast
Posts: 91
Liked: 13 times
Joined: Nov 01, 2017 8:52 pm
Full Name: blake dufour
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by bdufour » Nov 06, 2017 4:30 pm 1 person likes this post

i haven't had to restart this server since i wrote my original post about changing the login permissions to the service..

Re: Bunch of servers VSS Writer Errror 0x800423f4
Veeam Logo by bdufour » Wed Nov 01, 2017 9:01 pm

ive been experiencing this issue - i found this - https://social.technet.microsoft.com/Fo ... errecovery

typically, i have to restart the server for it to complete a backup/rep. it usually requires a restart every few day as related to Azure AD Sync updating likely and causing issues with permissions. i changed the log on account of the SQL server VSS writer service to a domain service account with proper permissions to the DB. for now that seemed to solve it. i will give an update in a week or so to confirm whether or not the issue has resurfaced.

jeradries
Lurker
Posts: 1
Liked: never
Joined: Nov 07, 2017 8:22 pm
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by jeradries » Nov 07, 2017 8:29 pm

scott_thomson wrote:This definitely looks like a MS issue, but I haven't found any real acknowledgement of the problem anywhere from them. In hopes that we can raise the profile of the issue, I've posted to the AD Connect UserVoice as well as the MS Partner Support forums. Hopefully if you can add your voices to this, someone at MS will get involved:

https://feedback.azure.com/forums/16940 ... it-doesn-t
https://partnersupport.microsoft.com/en ... 9729458808
I have been following your post on the MS Partner Support forum and when looking at the SyncEngine-AutoUpgrader-XXXXXXXX-XXXXXX.log files in C:\ProgramData\AADConnect, I am seeing the auto-upgrade process being triggered every 6 hours as well starting on 10/23. However, what caught my eye is "Upgrading AADConnect to version: 1.1.648.0".

According to the version release history at https://docs.microsoft.com/en-us/azure/ ... on-history, this isn't a valid version number. Are you seeing the same thing?

mcz
Expert
Posts: 213
Liked: 26 times
Joined: Jul 19, 2016 8:39 am
Full Name: Michael
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by mcz » Nov 08, 2017 7:47 am

Yep, I see the same version number in the logfile.

dnorth
Novice
Posts: 3
Liked: never
Joined: Nov 08, 2017 4:16 pm
Full Name: David North
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by dnorth » Nov 08, 2017 5:04 pm

bdufour wrote:i changed the log on account of the SQL server VSS writer service to a domain service account with proper permissions to the DB. for now that seemed to solve it.
Changing the service account seems to be working for me. The first Veeam job after an Auto (non-)Upgrade completed without an error anyway. Thanks, Blake.

bdufour
Enthusiast
Posts: 91
Liked: 13 times
Joined: Nov 01, 2017 8:52 pm
Full Name: blake dufour
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by bdufour » Nov 08, 2017 6:36 pm

Changing the service account seems to be working for me. The first Veeam job after an Auto (non-)Upgrade completed without an error anyway. Thanks, Blake.[/quote]

no problem, i still haven't had to restart this server and all jobs for it are still completing without any errors. at this point, i don't think it's just a coincidence and this may have fixed the issue on my end.

mcz
Expert
Posts: 213
Liked: 26 times
Joined: Jul 19, 2016 8:39 am
Full Name: Michael
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by mcz » Nov 09, 2017 7:45 am

In my case, repairing the express-db-instance has resolved the issue...

Marius_Aad
Lurker
Posts: 2
Liked: 1 time
Joined: Nov 09, 2017 8:47 am
Full Name: Marius
Contact:

Re: Bunch of servers VSS Writer Errror 0x800423f4

Post by Marius_Aad » Nov 09, 2017 8:56 am

Upgrading MSSQL Server 2012 Express LocalDB to SP4 fixed the issue for me. Multiple back up jobs finished successfully after that without restarting the vm.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 34 guests