AV 2.12 Error following latest Windows Server update - 'Sync computer "xxx || conflicted 1290" with Active Directory'

[Mark808]

I'm running the latest AppVol 2.12 with instant clone VMs and following the January Windows Server Update I see several instances of the error message above in my Pending Actions log.

The Dashboard also reports an increasing Computer Utilization count of Online Computers which no longer exist.

The specific System Messages being generated by AV are:

     Error perform_search (exception Encoding::CompatibilityError): (giving up)

     Job error: Sync Computer #<Thread:0x00000000a7cec0> incompatible character encodings: ASCII-8BIT and UTF-8

Is this a known problem?  Any recommended course of action?

-Mark

[jahegyi]

It's live and available for download.

[Mark808]

FYI - App Volumes 2.12.1 is now available for download.

The Release Notes details what is addressed in this update but among other things it is supposed to address the problems detailed in this thread.

[Lakshman]

Mark,

Could you confirm whether the 2.12.1 release fixed the issue or not please.

[doddsington]

I have not done a significant amount of testing yet, but it's looking like it is fixed so far. I was able to recompose an RDS host without issue. The conflicted entries in the database were also cleaned up.

[Mark808]

I too have done limited testing at this point.  The good news is operationally my test users are very happy since they no longer have to logon two or three times to obtain a usable VM (operational instant clone with attached writable volume and app-stacks). The problems with 2.12.0 were getting progressively worse over time in my instance.

As for cleanup, in the Activity Log I'm still seeing occasional Sync-Entity entries with "...||Conflictedxxxxx".  The other errors are gone. 

The Online Desktops count reported in the Dashboard Computer Utilization graph continues to climb without reduction and is more than 60 times greater then the sum of max count of all my pools.

I'm thinking these are all hold-over issues from 2.12.0 but am still investigating.

-Mark

[Lakshman]

Thanks Mark for testing this out.

Request to update this thead later after your investigation and how frequently are you seeing the error in activity log.