This error keeps surfacing. Can we get a root cause so we can globally correct this? is is a Microsoft patch that breaks this or maybe a programming error?
Thank You