allmhuran (4/16/2013)
Haha, likewise. The problem is a version incompatibility between sqlservr.exe and sqlaccess.dll. We've just been sent a link to an updated one, but we had already decided to roll back to RTM, couldn't wait any longer.RTM seems much better. I'm going to hold out for SP2.
We disabled strong name validation to work around the CLR issue; i.e.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification\*,*]
Testing thus far confirms build 3351 resolves the issue. I imagine we will see this make its way into CU4 and SP2.
Tommy
Follow @sqlscribe