Comments
6 comments
-
After updating the SQL Monitor server with the same CU it made no difference as far as the issue. This issue is consistent across 6 different servers (2 different windows clusters). This issue started with each server as soon as it was patched with this CU.
-
This matches, almost precisely, another case we're investigating, but haven't been able to pinpoint whats causing it.
Can you send your log files across to support@red-gate.com so we can take a look? -
Log files sent.
-
Have you been able find a solution for this?
-
We think this might be down to a Microsoft patch. We're just trying to narrow down which one now. We're not entirely sure yet if its the one you listed.
-
We identified the cause of this as a Microsoft hotfix that went out earlier in the year.
Can you update your server with the latest patches? Unfortunately we were unable to identify exactly which hotfix patched this, as we ran a number of updates on our test system. By title you might expect KB4339284 and KB4462901 but it would be best to just bring the server up to date if possible.
Add comment
Please sign in to leave a comment.
Is there a fix or setting to correct this?