Sunday, November 13, 2011

CRM2011 Setup/Upgrade Errors and Resolutions

This is the second part of my last blog Installing CRM2011 with Precreated AD Groups.
The following are some of the errors and their resolutions encountered during installation/upgrade

Error 1

SQLSERVERAGENT (SQLSERVERAGENT) service is not running on the server ......



· Check if SQLSERVERAGENT service is running
· Open the port 445 for SQL Server.

Error 2

During the import of the organizations the following warning was received.
"Fragmented indexes were detected in the Microsoft Dynamics CRM database",


Re-index the organisation databases
USE MyDatabase
EXEC sp_MSforeachtable @command1="print '?' DBCC DBREINDEX ('?', ' ', 80)"
EXEC sp_updatestats
Updating statistics ensures that queries compile with up-to-date statistics

Error 3

The following error message was received when testing the email router:
Type 'System.ServiceModel.Channels.ReceivedFault' in Assembly 'System.ServiceModel, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable


Add the account running the email router services to PrivUserGroup security group.

Error 4

The following error message was received when accessing the reports from any of the organizations:
Microsoft.Crm.Web.Reporting.SrsReportViewer.SetExecutionCredentials(ServerReport reportObj) Cannot create a connection to data source 'MSCRM'. (rsErrorOpeningConnection)
The reason was SSRS connector(reporting extensions) was installed using user other than deployment account. The SSRS service account was missing in privreportinggroup group.


  • · Add SSRS service account to privreporting group.
  • · Reinstall the reporting extension again using deployment account.
The process to resolve was as follows:
  1. 1. Uninstall the Reporting Extensions.
  2. 2. Go to the CONFIG DB (MSCRM_CONFIG) of CRM and update your organization's row in the Organization table to set the AreReportsPublished boolean field to FALSE.
  3. 3. Re-install the Reporting Extensions and they should publish the reports again.
Note: You will see the message about installation is republishing the reports again


The section contains information on the issues encountered that required fixing for the upgraded organisations.

Issue 1

Unknown labels in settings group as shown in the screen shot below. This had happened to all four organisations.
image clip_image006
             Before                              After


Follow the Microsoft article for resolution:

Issue 2

The main tab is closed by default as shown in the screen shot below:
It is noted that this happened on multiple different locations throughout all the organisations.


  • Open the form in customisation mode.
  • Expand the tab, save the changes and then publish the changes.
There were few other things that did not work after upgrade. One of them was, the client has custom button to “Create Phone Cal” on contact and account form. The button was using builtin javascript function “locAddActTo(4210)”. I need to change the ribbon and javascript to fix that that function does not exist in CRM 2011.

That’s all from me.

Saturday, November 5, 2011

Installing CRM2011 with precreated AD Groups

Last few weeks, I was working on CRM4.0 to CRM2011 upgrade.  I am doing few blogs to share my experience.  My upgrade involved moving the CRM sever and SQL server to a new severs. SSRS server was installed on the same as new SQL Server.  
I am not doing a step by step installation in this blog. I will be discussing the useful tips and solutions to some of the errors/problems I encounter.  Here are the main steps
1.    Install the CRM2011
2.    Install reporting extension(SSRS Connector) and Report Authoring Extension(Bids extensions)
3.    Backup 4.0 organization databases and restore them on  new SQL Server
4.    Import the organizations into CRM2011 using deployment manager
5.    Install/configure Email router
6.    Testing and fixing the issues.

The installation involved deploying the CRM Server on procreated AD groups.

Install the CRM2011

Installation Account Permissions

The user who is installing Microsoft Dynamics CRM should be a part of Local Administrator group on Microsoft Dynamics CRM server and on SQL Server. For more detail have a look at
The deployment user should also have sysadmin permission on the SQL Server Instance to import the organization (otherwise you will get error message)

Create the AD Groups

Create the following security groups in Active Directory:
•    PrivUserGroup
•    PrivReportingGroup
•    ReportingGroup
•    SQLAccessGroup

Important•    You don’t need to create UserGroup for CRM2011.
•    Use naming conventions for creating the groups for e.g.  OrgEnvironmentNameOfTheGroup (ABCDevPrivUserGroup).
•    Need to know more about permissions on these group, click here

Create configuration xml file for precreated groups

Here is sample of the config file

        <Groups AutoGroupManagementOff="true">
               <PrivUserGroup>CN=PrivUserGroup,OU=Company Name,OU=Company Name,DC=<domain>,DC=<domain_extension></PrivUserGroup>
             <SQLAccessGroup>CN=SQLAccessGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></SQLAccessGroup>
                    <ReportingGroup>CN=ReportingGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></ReportingGroup>
    <PrivReportingGroup>CN=PrivReportingGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></PrivReportingGroup>

Now you need to change highlighted parts of the file to suit your system. If you like to know more about the structure chek the Microsoft article mentioned above in the post.

The easiest way to get the proper CN,OUs,DCs without making any mistakes use the dsquery command. Open the command prompt and Run
            dsquery group -name adgroupprefix* Change adgroupprefix with starting characters of your group
For e.g dsquery group -name ABCDev*


It will display all the information you need to fill the config file.
Just copy that and replace highlighted area in the config file above.
Save the file as config.xml.

Run CRM2011 Install

  • Open the cmd prompt and navigate the crm media  to folder containing ServerSetup.exe.
  • Run ServerSetup.exe /config C:\config.xml
  • Follow the installation wizard instructions.

Install reporting extension (SSRS Connector) and Report Authoring Extension (Bids extensions)

Reporting extension (SSRS Connector)

The deployment needs local administrator permissions to install reporting extension (SSRS Connector). The installation adds the Microsoft SQL Server Reporting Services “service account” for the associated instance of SQL Server to the PrivReportingGroup security group.
Important Reporting extensions must be installed to publish the reports and to import the organization.

Report Authoring Extension

(Bids extensions) is required to write fetchxml based reports.

Second part is coming soon........