1 of 1 people found this helpful
I'd suggest you open a support case please. This will be covered in article KB81763.
Note the KB article is not published yet, but should be available in the next 48 hours. (I only entered it to the KB system today !)
Sounds like it's going to be the same issue.
I submitted a new case for this. Does your KB have a fix/workaround?
Just wanted to report that the fix for KB81763 worked for my issue.