<?xml version="1.0" encoding="utf-8"?>
<rss
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 version="2.0">
<channel>
<title>Customer Effective Blog</title>
<link>http://blog.CustomerEffective.com/blog/</link>
<description>Microsoft Dynamics CRM Blog from Customer Effective, CRM Experts and a Microsoft Inner Circle partner.</description>
<language>en-US</language>
<lastBuildDate>Fri, 17 Feb 2012 08:39:00 -0500</lastBuildDate>
<generator>http://www.typepad.com/</generator>

<item>
<title>Microsoft Dynamics CRM 2011 Reporting Extension (SRS Data Connector) Installation Service Account Warning</title>
<link>http://blog.CustomerEffective.com/blog/2011/12/microsoft-dynamics-crm-2011-reporting-extension-srs-data-connector-installation-error.html</link>
<guid isPermaLink="true">http://blog.CustomerEffective.com/blog/2011/12/microsoft-dynamics-crm-2011-reporting-extension-srs-data-connector-installation-error.html</guid>
<description>The Microsoft Dynamics CRM 2011 Reporting Extensions, previously known as the SRS Data Connector, will sometimes return an error message during installation that is intended to be a warning, not an error. The message that you see is ‘A Microsoft...</description>


<content:encoded>&lt;p&gt;The Microsoft Dynamics CRM 2011 Reporting Extensions, previously known as the SRS Data Connector, will sometimes return an error message during installation that is intended to be a warning, not an error. The message that you see is ‘A Microsoft Dynamics CRM Server component is using the same account as the instance of SQL Server Reporting Services.’&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://blog.customereffective.com/.a/6a00e54fb34b6f88330162fd239426970d-pi&quot;&gt;&lt;img alt=&quot;image&quot; border=&quot;0&quot; height=&quot;174&quot; src=&quot;http://blog.customereffective.com/.a/6a00e54fb34b6f88330162fd239437970d-pi&quot; style=&quot;background-image: none; padding-left: 0px; padding-right: 0px; display: block; float: none; margin-left: auto; margin-right: auto; padding-top: 0px; border-width: 0px;&quot; title=&quot;image&quot; width=&quot;479&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There are several conditions which will provoke this message&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;· A Microsoft Dynamics CRM Server 2011 component is installed on the computer where Microsoft Dynamics CRM Connector for SQL Server Reporting Services Setup is being run.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;· The SQL Server Reporting Services account is a member of the Active Directory SQLAccessGroup security group. This can occur when the Reporting Services is running under the same account as another Microsoft Dynamics CRM component.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;· All Microsoft Dynamics CRM Server 2011 components, SQL Server, and Reporting Services are installed on a computer that is running Microsoft Windows Server Small Business Edition where Microsoft Dynamics CRM Connector for SQL Server Reporting Services Setup is being run.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;· The SQL Server Reporting Services account is set as &amp;quot;Local Service.&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;To get around this error, follow the steps below. Once this is completed, you will still see the error message however the ‘Next’ button will be available and you can continue with the installation. This does require a registry setting change, so it is recommended that the registry be backed up PRIOR to making any changes.  One thing to note before using this, if you change this key on your CRM server, any checks that are supposed to take place during the CRM installation will also be ignored.  This should only be used with great care and turned off after the Reporting Extensions installation is completed.  Failure to do so may result in checks being ignored during other installations and could have negative consequences.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;1. Close the installer window&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;2. Find the MSCRM key in the HKLM\SOFTWARE\MICROSOFT directory&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;3. If the MSCRM key does not exist, create it in the HKLM\SOFTWARE\MICROSOFT directory&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;4. Once you have the key, create a new DWORD value named &lt;strong&gt;IgnoreChecks&lt;/strong&gt; and set the value to 1&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;5. Launch the installer and follow its instructions. When you get to the environment checks the ‘Next’ button will be available.&lt;/p&gt;
&lt;/blockquote&gt;</content:encoded>



<category>Dynamics CRM 2011</category>

<category>Microsoft CRM Implementation</category>

<category>Microsoft CRM Troubleshooting</category>

<dc:creator>Heather Reynolds</dc:creator>
<pubDate>Wed, 07 Dec 2011 08:50:00 -0500</pubDate>

</item>

<item>
<title>Microsoft Dynamics CRM 2011 Email Router Throws 5.7.1 Client Could Not be Authenticated When Sending Emails</title>
<link>http://blog.CustomerEffective.com/blog/2011/12/email-router-throws-571-client-could-not-be-authenticated-when-sending-emails.html</link>
<guid isPermaLink="true">http://blog.CustomerEffective.com/blog/2011/12/email-router-throws-571-client-could-not-be-authenticated-when-sending-emails.html</guid>
<description>I was working on a 2011 upgrade and came across an issue when running the Email Router on a Windows Server 2008 R2 machine. I installed the router with no issues, but when someone sent an email it failed. The...</description>


<content:encoded>&lt;p&gt;I was working on a 2011 upgrade and came across an issue when running the Email Router on a Windows Server 2008 R2 machine. I installed the router with no issues, but when someone sent an email it failed. The following message was in the event viewer of the machine the router was installed on:&lt;/p&gt;
&lt;p&gt;‘5.7.1 – Client could not be authenticated.’&lt;/p&gt;
&lt;p&gt;During our troubleshooting, we found that the Email Router worked on a Windows Server 2008 machine with no Exchange authentication challenges. A Network Monitor trace confirmed the authentication challenge on the Windows Server 2008 R2 machine as an Exchange challenge. Research confirmed that Exchange 2007 was setup to accept anonymous users.&lt;/p&gt;
&lt;p&gt;The solution to this was to set the authentication method to ‘Anonymous’ in the email router configuration manager. On the Windows Server 2008 machine, the authentication method was set to ‘Windows Authentication,’ however there is a conflict when sending authentication from a Windows Server 2008 R2 machine to an Exchange Server 2007 environment which is configured to accept anonymous users. It is also important to note that in this particular environment the Exchange server as well as the server with the Email Router are on the same network.&lt;/p&gt;</content:encoded>



<category>Dynamics CRM 2011</category>

<category>Microsoft CRM Implementation</category>

<category>Microsoft CRM Troubleshooting</category>

<dc:creator>Heather Reynolds</dc:creator>
<pubDate>Fri, 02 Dec 2011 08:54:00 -0500</pubDate>

</item>

</channel>
</rss>

<!-- ph=1 -->

