Ask Your Question

Revision history [back]

This seems to be an issue with SQL Server - one user was able to get around this error by applying SQL Server 2012 SP3 CU 10, which includes a fix for KB4038210. Let us know is this fixes the issue for you!

This seems to be an issue with SQL Server - one user was able to get around this error by applying SQL Server 2012 SP3 CU 10, which includes a fix for KB4038210. Let us know is if this fixes the issue for you!