Thursday, September 29, 2011

Where is the License Key in the Crm 2011 Database?

In Crm 4, you could get the license key by executing the following SQL:

SELECT LicenseKey FROM ConfigSettings

This value is now null is Crm 2011.  The new column name is LicenseKeyV5RTM.

So the new Select statement is:

SELECT LicenseKeyV5RTM FROM ConfigSettings

Hope this saves someone some time.

--Scott

Thursday, July 28, 2011

Microsoft CRM 2011 How to Configure IFD Hosted Setup

Posting this so mainly so i don't forget about it.  Microsoft Dynamics 2011 - Setting up IFD.  This is one of the best posts on IFD i have seen.

http://www.interactivewebs.com/blog/index.php/server-tips/microsoft-crm-2011-how-to-configure-ifd-hosted-setup/


Enjoy.

Tuesday, July 12, 2011

Crm 2011–Request Error in the OrganizationData.svc


I fought this error for an hour this afternoon.  I was setting the the URL to the OrganizationData.svc like so HTTP://CRMDEV-VPC:5555/XRMSERVICES/2011/ORGANIZATIONDATA.SVC/.  This always returned “Request Error” in blue bold letters followed by
The server encountered an error processing the request. See server logs for more details.
So I enabled tracing and retrieved the following from the trace log:
[2011-02-16 16:55:35.910] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:    7 |Category: Platform.Sdk |User: 00000000-0000-0000-0000-000000000000 |Level: Error | ServiceModelTraceRedirector.TraceData
While this error may appear to be unhelpful, it really tells us  quite a bit.  Notice the Organization and the User are set to an empty GUID.  This is clearly an issue. Crm 2011’s OrganizationData.svc requires the Organization name be present in the the URL.  So the fix was quite simple, add the organization name to the URL:
Hope this saves someone some time.

Crm 2011 Enabling Tracing with PowerShell


Tired of digging through the registry to enable tracing in Crm? Well, you can use PowerShell to enable/disable tracing in Crm 2011. Most of this script is from HTTP://SUPPORT.MICROSOFT.COM/KB/907490 but I had to make a few changes to get it to work. 
THE FOLLOWING POWERSHELL ENABLES TRACING:
Add-PSSnapin Microsoft.Crm.PowerShell
Get-CrmSetting TraceSettings
$setting = Get-CrmSetting TraceSettings
$setting.Enabled=1
Set-CrmSetting $setting
Get-CrmSetting TraceSettings
IISRESET
THE FOLLOWING POWERSHELL DISABLES TRACING:
Add-PSSnapin Microsoft.Crm.PowerShell
Get-CrmSetting TraceSettings
$setting = Get-CrmSetting TraceSettings
$setting.Enabled=0
Set-CrmSetting $setting
Get-CrmSetting TraceSettings
IISRESET
I changed the “True” and “False” from the KB article to 0 and 1 because “False” did not work.  I also added an IISRESET to the end, which is required to turn tracing on or off.
Executing the scripts in Server 2008 R2 is simple, just right click execute PowerShell. 
Enjoy!

Microsoft.ReportViewer.Webforms version error


After you the report viewer you may get the following error when trying to use the ReportViewer Control:
CS0433: The type ‘Microsoft.Reporting.WebForms.ReportViewer’ exists in both ‘c:\WINDOWS\assembly\GAC_MSIL\
Microsoft.ReportViewer.WebForms\8.0.0.0__b03f5f7f11d50a3a\
Microsoft.ReportViewer.WebForms.dll’ and ‘c:\WINDOWS\assembly\GAC_MSIL\
Microsoft.ReportViewer.WebForms\9.0.0.0__b03f5f7f11d50a3a\
Microsoft.ReportViewer.WebForms.dll’
The following will force the control to always use version 9.0 of the control.  Add the following to your web.config:

   
     
                                  publicKeyToken=”b03f5f7f11d50a3a” />
                                newVersion=”9.0.0.0″/>
     

   

 
Hope this helps.