<?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"
	>
<channel>
	<title>Comments on: Using CRM with a SQL named instance</title>
	<atom:link href="http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/feed/" rel="self" type="application/rss+xml" />
	<link>http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/</link>
	<description>This is a blog, it goes bit bit</description>
	<pubDate>Tue, 06 Jan 2009 05:53:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Joe</title>
		<link>http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-773</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Fri, 05 Oct 2007 15:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-773</guid>
		<description>What is really odd here is that Microsoft tells you to create the named instance when installing Small Business Server and even tells you how to change the Sharepoint install to work with the new named instance. Which means everyone who installs Small Business Server and upgrades from express to SQL 2005 per Microsoft's recommendation will have this issue but there is nothing about this on their website. How frustrating...I have spent days trying to solve this and your site was the only one I found that gave me the answer. 

Thanks for taking to time to correct this stupid oversight by our friends at Microsoft.</description>
		<content:encoded><![CDATA[<p>What is really odd here is that Microsoft tells you to create the named instance when installing Small Business Server and even tells you how to change the Sharepoint install to work with the new named instance. Which means everyone who installs Small Business Server and upgrades from express to SQL 2005 per Microsoft&#8217;s recommendation will have this issue but there is nothing about this on their website. How frustrating&#8230;I have spent days trying to solve this and your site was the only one I found that gave me the answer. </p>
<p>Thanks for taking to time to correct this stupid oversight by our friends at Microsoft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jody</title>
		<link>http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-771</link>
		<dc:creator>Jody</dc:creator>
		<pubDate>Thu, 04 Oct 2007 23:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-771</guid>
		<description>Thanks a million for this post. It was extremely helpful, and saved several hours ofhold music playing at MS support. Cheers</description>
		<content:encoded><![CDATA[<p>Thanks a million for this post. It was extremely helpful, and saved several hours ofhold music playing at MS support. Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-740</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Thu, 09 Aug 2007 01:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-740</guid>
		<description>Thanks for this tip-- you've saved me a lot of hassle!</description>
		<content:encoded><![CDATA[<p>Thanks for this tip&#8211; you&#8217;ve saved me a lot of hassle!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Monsees</title>
		<link>http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-35</link>
		<dc:creator>Anthony Monsees</dc:creator>
		<pubDate>Thu, 18 Jan 2007 19:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://kaledavis.com/2006/12/30/using-crm-with-a-sql-named-instance/#comment-35</guid>
		<description>Thanks for posting this solution as it saved us time and money on a support incident.  

One addition thing to note is if you're planning to install CRM on a named instance from the beginning, you can add the key (HKEY_LOCAL_MACHINE -&#62; SOFTWARE -&#62; Microsoft -&#62; MSCRM -&#62; IgnoreChecks) before you first install and it works the same.  I've done 3 installations with named instances so far and haven't ran into any issues.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this solution as it saved us time and money on a support incident.  </p>
<p>One addition thing to note is if you&#8217;re planning to install CRM on a named instance from the beginning, you can add the key (HKEY_LOCAL_MACHINE -&gt; SOFTWARE -&gt; Microsoft -&gt; MSCRM -&gt; IgnoreChecks) before you first install and it works the same.  I&#8217;ve done 3 installations with named instances so far and haven&#8217;t ran into any issues.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.400 seconds -->
