Comments for Patrick Purviance - SQL Server DBA Blog http://impactsolutionsonline.com Blogging impactful solutions for SQL Server DBAs worldwide Fri, 09 Mar 2012 21:46:52 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×800 by admin http://impactsolutionsonline.com/failed-to-initialize-the-common-language-runtime-clr-v2-0-50727-with-hresult-0x800/comment-page-1#comment-3772 admin Fri, 09 Mar 2012 21:46:52 +0000 http://impactsolutionsonline.com/?p=346#comment-3772 <strong>UPDATE 3:</strong> <br> Ok, after a couple months back and forth with Microsoft Support and testing a couple of theoretical resolutions, we finally believe we resolved the issue. <br> The first attempt that seemed to work for about a month, was to enable CLR, restart the affected server, then disable CLR and restart again. Again, this appeared to solve the issue....for a while. Then it came back seemingly all of sudden with no difference in activity. Just started exhibiting the errors again. Our heads hung low and we enabled a memory dump trace for the 6512 error condition. We then reproduced the error by executing a DDL command against a replicated article and sent off the trace to Microsoft. They replied with another solution based on what the engineers found in the dump. <br> Based on the dump that was captured we were able to determine that this problem is actually related to an issue in Server 2003 not unloading DLLs correctly. <br> <strong><em>FIX: Error messages after SQL Server has been running for some time on Windows Server 2003 or on Windows 2000: "Failed to load FileName.dll" and "Attempts to load any type of dll might fail within the SQL Server process"</em></strong> - <a href="http://support.microsoft.com/kb/941105" rel="nofollow">http://support.microsoft.com/kb/941105</a> <br> Per the KB - the problem occurs because no thread local storage (TLS) slot is available for the SQL Server process (Sqlservr.exe). And in the dump that was captured we were able to determine that the number of TLS slots was 0. <br> This hotfix should address the TLS slot problem causing these errors. <br> Hope that helps someone else out there. <BR> -Patrick UPDATE 3:

Ok, after a couple months back and forth with Microsoft Support and testing a couple of theoretical resolutions, we finally believe we resolved the issue.

The first attempt that seemed to work for about a month, was to enable CLR, restart the affected server, then disable CLR and restart again. Again, this appeared to solve the issue….for a while. Then it came back seemingly all of sudden with no difference in activity. Just started exhibiting the errors again. Our heads hung low and we enabled a memory dump trace for the 6512 error condition. We then reproduced the error by executing a DDL command against a replicated article and sent off the trace to Microsoft. They replied with another solution based on what the engineers found in the dump.

Based on the dump that was captured we were able to determine that this problem is actually related to an issue in Server 2003 not unloading DLLs correctly.

FIX: Error messages after SQL Server has been running for some time on Windows Server 2003 or on Windows 2000: “Failed to load FileName.dll” and “Attempts to load any type of dll might fail within the SQL Server process” – http://support.microsoft.com/kb/941105

Per the KB – the problem occurs because no thread local storage (TLS) slot is available for the SQL Server process (Sqlservr.exe). And in the dump that was captured we were able to determine that the number of TLS slots was 0.

This hotfix should address the TLS slot problem causing these errors.

Hope that helps someone else out there.

-Patrick

]]> Comment on Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×800 by admin http://impactsolutionsonline.com/failed-to-initialize-the-common-language-runtime-clr-v2-0-50727-with-hresult-0x800/comment-page-1#comment-3247 admin Mon, 19 Dec 2011 16:03:02 +0000 http://impactsolutionsonline.com/?p=346#comment-3247 UPDATE 2: Well, here we are again. The reinstallation of .NET 3.5 SP1 did NOT fix this error in Replication. After that attempt, we decided to take another stab at it by completely unistalling all of the .NET frameworks from the server. I uninstalled .NET 2.0, 3.0, and 3.5 SP1 via Add/Remove Programs, restarted the server, and then installed 2.0, 3.0, and 3.5 SP1 to bring it back up to date. This also included a post 3.5 SP1 patch documented here <a href="http://go.microsoft.com/fwlink/?LinkId=136730" rel="nofollow">KB959209</a>. But as soon as we attempted to regenerate a snapshot on one of the publications, the same error occurred. So to me, none of this .NET framework reinstallation has done any good whatsoever. I'm opening a case with Microsoft and will post back the results of that endeavor. -Patrick UPDATE 2:

Well, here we are again. The reinstallation of .NET 3.5 SP1 did NOT fix this error in Replication. After that attempt, we decided to take another stab at it by completely unistalling all of the .NET frameworks from the server. I uninstalled .NET 2.0, 3.0, and 3.5 SP1 via Add/Remove Programs, restarted the server, and then installed 2.0, 3.0, and 3.5 SP1 to bring it back up to date. This also included a post 3.5 SP1 patch documented here KB959209. But as soon as we attempted to regenerate a snapshot on one of the publications, the same error occurred. So to me, none of this .NET framework reinstallation has done any good whatsoever. I’m opening a case with Microsoft and will post back the results of that endeavor.

-Patrick

]]> Comment on Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×800 by admin http://impactsolutionsonline.com/failed-to-initialize-the-common-language-runtime-clr-v2-0-50727-with-hresult-0x800/comment-page-1#comment-2992 admin Sat, 19 Nov 2011 16:31:23 +0000 http://impactsolutionsonline.com/?p=346#comment-2992 UPDATE: So, quite some time later I decided, after a couple of conversations with Microsoft support and another resource on a support forum, to reinstall the .NET 3.5 SP1 framework on the server affected by this seemingly random CLR error. Only time will tell if this fix works, but I’ll update in a couple months (or sooner if the issue reappears). -Patrick UPDATE:

So, quite some time later I decided, after a couple of conversations with Microsoft support and another resource on a support forum, to reinstall the .NET 3.5 SP1 framework on the server affected by this seemingly random CLR error. Only time will tell if this fix works, but I’ll update in a couple months (or sooner if the issue reappears).

-Patrick

]]>