<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Patrick Purviance - SQL Server DBA Blog</title>
	<atom:link href="http://impactsolutionsonline.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://impactsolutionsonline.com</link>
	<description>Blogging impactful solutions for SQL Server DBAs worldwide</description>
	<lastBuildDate>Mon, 19 Dec 2011 16:03:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×800 by admin</title>
		<link>http://impactsolutionsonline.com/failed-to-initialize-the-common-language-runtime-clr-v2-0-50727-with-hresult-0x800/comment-page-1#comment-3247</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 19 Dec 2011 16:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://impactsolutionsonline.com/?p=346#comment-3247</guid>
		<description>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 &lt;a href=&quot;http://go.microsoft.com/fwlink/?LinkId=136730&quot; rel=&quot;nofollow&quot;&gt;KB959209&lt;/a&gt;.  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&#039;m opening a case with Microsoft and will post back the results of that endeavor.


-Patrick</description>
		<content:encoded><![CDATA[<p>UPDATE 2:</p>
<p>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&#8217;m opening a case with Microsoft and will post back the results of that endeavor.</p>
<p>-Patrick</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×800 by admin</title>
		<link>http://impactsolutionsonline.com/failed-to-initialize-the-common-language-runtime-clr-v2-0-50727-with-hresult-0x800/comment-page-1#comment-2992</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 19 Nov 2011 16:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://impactsolutionsonline.com/?p=346#comment-2992</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>UPDATE:</p>
<p>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).</p>
<p>      -Patrick</p>
]]></content:encoded>
	</item>
</channel>
</rss>

