<?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>CRM 3.0 Only System Admin user can run reports</title>
<link>http://blog.CustomerEffective.com/blog/2009/07/crm-30-only-system-admin-user-can-run-reports.html</link>
<guid isPermaLink="true">http://blog.CustomerEffective.com/blog/2009/07/crm-30-only-system-admin-user-can-run-reports.html</guid>
<description>Recently I had an issue with customer using CRM 3.0. The issue was that only the default system administrator could run reports. The other users in the system could not run any reports or access them. All users were already...</description>
<content:encoded>&lt;p&gt;Recently I had an issue with customer using CRM 3.0.&amp;#0160; The issue was that only the default system administrator could run reports.&amp;#0160; The other users in the system could not run any reports or access them.&amp;#0160; All users were already in the system admin security role.&amp;#0160; I then checked active directory settings and those users were in the correct AD groups and reporting groups. I also reviewed the trust for delegation settings and those were correctly in place.&amp;#0160; &lt;/p&gt;
&lt;p&gt;We were about to run the&amp;#0160;Kerberos authentication tool when we discovered that a registry setting was incorrect.&amp;#0160; The issue was resolved by adding the NTLMForSQLRSServer registry key with a value of 1 on the CRM server at HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM.&lt;/p&gt;
&lt;p&gt;I know this was a quick blog but I wanted pass this along in case someone encounters it again.&amp;#0160; It may help them to resolve this type of issue in a timely fashion.&lt;/p&gt;</content:encoded>



<dc:creator>John Whisonant</dc:creator>
<pubDate>Tue, 28 Jul 2009 15:37:28 -0400</pubDate>

</item>

</channel>
</rss>

<!-- ph=1 -->

