Replying to a message from: mark

so for 2008 R2 would it possibly be related to  KB4338823 since it reports the same sql issue?

 

https://support.microsoft.com/en-us/help/4338823