CRM2011IG OpandMaint

Microsoft Dynamics CRM 2011 Operating and
Maintaining Guide
Version 5.7.0
This document is provided "as-is". Information and views expressed in this document, including
URL and other Internet Web site references, may change without notice. You bear the risk of
using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real
association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any
Microsoft product. You may copy and use this document for your internal, reference purposes.
© 2012 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, ActiveX, Azure, BizTalk, JScript, Microsoft Dynamics, Outlook,
SharePoint, SQL Server, Visual Basic, Visual Studio, Windows, Windows Server, and Windows
Vista are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.
Contents
Microsoft Dynamics CRM 2011 Operating and Maintaining Guide.................................................6
In This Section............................................................................................................................. 6
Send us your comments about this document (Op and Maintain Guide)........................................6
Operating Microsoft Dynamics CRM............................................................................................... 7

Using Windows PowerShell to perform Microsoft Dynamics CRM deployment and
administration tasks................................................................................................................. 7
Setting Microsoft Dynamics CRM properties manually............................................................7
In This Section......................................................................................................................... 8
See Also...................................................................................................................................... 8
Move the Microsoft Dynamics CRM 2011 deployment....................................................................8

In This Topic................................................................................................................................ 8
Move the Microsoft Dynamics CRM databases to another SQL Server and SQL Server
Reporting Services server in the same domain, and leave the Microsoft Dynamics CRM
Server 2011 on the existing server........................................................................................... 8
Redeploy the Microsoft Dynamics CRM deployment that includes the Microsoft Dynamics CRM
Server 2011 within the same domain or to another domain...................................................10
Move the Microsoft Dynamics CRM Server or one of the Microsoft Dynamics CRM server roles.
However, leave the SQL Server and the SQL Server Reporting Services server intact.........12
See Also.................................................................................................................................... 13
Change a Microsoft Dynamics CRM service account...................................................................13

Change a Microsoft Dynamics CRM service account by running a repair.................................13
Manually change the CRMAppPool service account.................................................................13
Determine the groups to update............................................................................................. 14
See Also.................................................................................................................................... 15
Enable Windows Error Reporting.................................................................................................. 15

See Also.................................................................................................................................... 16
Limit the number of asynchronous jobs picked up for each organization......................................16

To configure the number of asynchronous jobs picked up for each organization...................17
See Also.................................................................................................................................... 17
Monitoring and troubleshooting Microsoft Dynamics CRM...........................................................17

In This Section........................................................................................................................... 17
Tracing overview....................................................................................................................... 18
Microsoft Dynamics CRM deployment-level tracing...............................................................18
Microsoft Dynamics CRM server-level tracing........................................................................19
Enable tracing for Microsoft Dynamics CRM Reporting Extensions for SQL Server Reporting
Services.............................................................................................................................. 21
Enable tracing for Microsoft Dynamics CRM for Outlook.......................................................22
System Center Monitoring Pack for Microsoft Dynamics CRM 2011.........................................23
Microsoft Dynamics CRM 2011 performance counters..............................................................23
See Also.................................................................................................................................... 24
Updating Microsoft Dynamics CRM 2011.....................................................................................24

In This Topic.............................................................................................................................. 24
Microsoft Dynamics CRM 2011 Setup update...........................................................................25
Microsoft Dynamics CRM 2011 application update rollup..........................................................25
Distribution and application of Microsoft Dynamics CRM updates.........................................25
Removing an update rollup.................................................................................................... 26
Update rollup requirements....................................................................................................... 26
Frequently asked questions about update rollups for Microsoft Dynamics CRM 2011..............27
How are update rollups packaged?........................................................................................ 27
What is the latest Microsoft Dynamics CRM 2011 update rollup?..........................................27
Should I apply the latest update rollup to my deployment?....................................................27
Does an update rollup require additional configuration after I install it?.................................28
Are the update rollups cumulative?........................................................................................28
Do I have to apply the previous update rollup before I can apply a later one?.......................28
How frequently can I expect a new update rollup to be released?.........................................28
How can I be notified when an update is released?...............................................................28
In what order should I apply an update rollup?.......................................................................29
How can I check my computer to see if an update rollup is applied?.....................................29
See Also.................................................................................................................................... 29
Improving performance and optimizing Microsoft Dynamics CRM 2011.......................................30

IIS compression......................................................................................................................... 30
Antivirus scans and Microsoft Dynamics CRM..........................................................................30
Performance and optimization resources for Microsoft Dynamics CRM....................................31
See Also.................................................................................................................................... 31
Microsoft Dynamics CRM Server 2011 Known Issues..................................................................31

In This Topic.............................................................................................................................. 31
An "A failure was encountered while launching the process serving application pool
'CRMAppPool'" message is logged in the Application log......................................................32
A "Server Error in '/' Application" error message appears when you try to run a report in a multi-
tenant deployment.................................................................................................................. 32
"Failure: The SQL Server '{0}' is unavailable" error message when you try to create an
organization............................................................................................................................ 32
“External Error – No such object on server” error message when you try to enable a user.......33
Microsoft Dynamics CRM mobile issues when you use AD FS 2.0...........................................34
You cannot sign out of Microsoft Dynamics CRM when you use a mobile device..................34
Some application pages do not display completely when viewed by mobile users................34
The computer that is running SQL Server 2008 R2 indicates 100% CPU utilization.................34
See Also.................................................................................................................................... 34
Backing Up the Microsoft Dynamics CRM System.......................................................................35

In This Topic.............................................................................................................................. 35
Backup requirements summary................................................................................................. 35
Selecting a backup type............................................................................................................ 36
Backing up Windows Server...................................................................................................... 36
Backing up Active Directory....................................................................................................... 37
Backing up SQL Server, including Reporting Services..............................................................38
Backing up Microsoft Dynamics CRM Server 2011...................................................................39
Exporting customizations and solutions.....................................................................................40
See Also.................................................................................................................................... 40
Failure Recovery........................................................................................................................... 40
See Also.................................................................................................................................... 40
Scenario A: SQL Server failure..................................................................................................... 40

Scenario-A recovery.................................................................................................................. 41
See Also.................................................................................................................................... 41
Scenario B: Microsoft Dynamics CRM Server 2011 failure...........................................................42

Scenario-B recovery.................................................................................................................. 42
See Also.................................................................................................................................... 42
Scenario C: Exchange Server failure............................................................................................ 42

Scenario-C recovery.................................................................................................................. 43
See Also.................................................................................................................................... 43
Scenario D: Active Directory failure.............................................................................................. 43

Scenario-D recovery.................................................................................................................. 43
See Also.................................................................................................................................... 44
Microsoft Dynamics CRM for Outlook failure recovery..................................................................44

See Also.................................................................................................................................... 45
Microsoft Dynamics CRM 2011 Operating and
Maintaining Guide
This guide is part of the Microsoft Dynamics CRM 2011 Implementation Guide, which consists of
the following three documents:
 Microsoft Dynamics CRM 2011 Planning Guide: Use this guide to determine what you
have to plan for Microsoft Dynamics CRM. This guide focuses on supported topologies,
system requirements, and technical considerations to address before installation.
 Microsoft Dynamics CRM 2011 Installing Guide: Use this guide to learn about how you
install Microsoft Dynamics CRM applications. This guide includes step-by-step instructions for
running Setup, command-line installation instructions, and guidance about how to remove
Microsoft Dynamics CRM.
 Microsoft Dynamics CRM 2011 Operating and Maintaining Guide: You can read this
guide to learn how to back up, restore, and perform system recovery for Microsoft
Dynamics CRM data. Also, this guide has troubleshooting steps for known issues.
The Microsoft Dynamics CRM 2011 Operating and Maintaining Guide contains resources and
topics designed to help you operate and maintain your on-premises deployment of Microsoft
Dynamics CRM 2011.
In This Section
Operating Microsoft Dynamics CRM
Monitoring and troubleshooting Microsoft Dynamics CRM
Updating Microsoft Dynamics CRM 2011
Microsoft Dynamics CRM Server 2011 Known Issues
Backing Up the Microsoft Dynamics CRM System
Failure Recovery
Send us your comments about this

document (Op and Maintain Guide)
If you have a question or comment about this document, click to send an e-mail message to the
Microsoft Dynamics CRM content team.
If your question is about Microsoft Dynamics CRM products, and not about the content of this
book, search the Microsoft Help and Support Center or the Microsoft Knowledge Base.
6
Operating Microsoft Dynamics CRM includes guaranteeing availability by monitoring server status
and performance, making backups, planning for recovery from disasters, and ongoing
troubleshooting.
Using Windows PowerShell to perform Microsoft

Dynamics CRM deployment and administration
tasks
You can use Windows PowerShell cmdlets and the Deployment Manager to perform deployment
and administration tasks. You can also use the methods that are described in the Microsoft
Dynamics CRM SDK to perform these tasks. The cmdlets are installed on the computer when you
install a Full Server role or where you install the Deployment Tools server role, if you are installing
individual server roles.
Important
You must register the Microsoft Dynamics CRM Windows PowerShell commands,
otherwise you will receive the following message when you try to run a cmdlet.
The term ‘Microsoft Dynamics CRM Windows PowerShell command' is not recognized as
the name of a cmdlet, function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try again.
To register the Microsoft Dynamics CRM Windows PowerShell commands, follow these steps.
1. Log into the administrator account on your Microsoft Dynamics CRM server.
2. Open a Windows PowerShell prompt.
3. At the Windows PowerShell prompt, add the Microsoft Dynamics CRM Windows PowerShell
snap-in:
Add-PSSnapin Microsoft.Crm.PowerShell
This command adds the Microsoft Dynamics CRM Windows PowerShell snap-in to the current
session. The snap-in is registered during installation and Setup of Microsoft Dynamics CRM
Server.
For a list of supported Microsoft Dynamics CRM Windows PowerShell cmdlets, see User
PowerShell to Call the Deployment Web Service.
Setting Microsoft Dynamics CRM properties manually

Some properties are not unique to a single entity in Microsoft Dynamics CRM. Therefore, we
recommend that you specify the GUID ID of the specific entity when you want to change a
property. For example, you should use the organization ID when you change an organization
property by using Windows PowerShell or the Deployment Web Service.
7
For more information about the Windows PowerShell cmdlets for Microsoft Dynamics CRM see,
the Microsoft Dynamics CRM Deployment Manager Help.
For more information about Windows PowerShell, see Scripting with Windows PowerShell.
For a list of supported Microsoft Dynamics CRM Windows PowerShell cmdlets, see User
PowerShell to Call the Deployment Web Service.
For more information about the Deployment Web Service see Deployment Web Service in
Microsoft Dynamics CRM.
In This Section
Move the Microsoft Dynamics CRM 2011 deployment
Change a Microsoft Dynamics CRM service account
Enable Windows Error Reporting
Limit the number of asynchronous jobs picked up for each organization
See Also
Microsoft Dynamics CRM 2011 Operating and Maintaining Guide
Move the Microsoft Dynamics CRM 2011

deployment
This topic describes how to move server components in a Microsoft Dynamics CRM 2011
deployment.
In This Topic
Move the Microsoft Dynamics CRM databases to another SQL Server and SQL Server Reporting
Services server in the same domain, and leave the Microsoft Dynamics CRM Server 2011 on the
existing server
Redeploy the Microsoft Dynamics CRM deployment that includes the Microsoft Dynamics CRM
Server 2011 within the same domain or to another domain
Move the Microsoft Dynamics CRM Server or one of the Microsoft Dynamics CRM server roles.
However, leave the SQL Server and the SQL Server Reporting Services server intact
8
Note
Move the Microsoft Dynamics CRM databases to
another SQL Server and SQL Server Reporting
Services server in the same domain, and leave the
Microsoft Dynamics CRM Server 2011 on the
existing server
1. Back up the OrganizationName_MSCRM database and the MSCRM_CONFIG database. To
do this, follow these steps:
a. On the computer that is running Microsoft SQL Server, click Start, point to All Programs,
point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
b. In the Connect to Server window, type the name of the server that is running Microsoft
SQL Server 2008 in the Server name box and then click Connect.
c. Expand Databases, right-click the OrganizationName_MSCRM database, point to
Tasks, and then click Back Up.
d. Under Destination, add the location to save the backup file, and then click OK.
e. Repeat steps 1b and 1c for the MSCRM_CONFIG database.
If you must move more than one organization, repeat steps 1a-1d for each
organization database.
2. Restore the OrganizationName_MSCRM database and the MSCRM_CONFIG database on
the new computer that is running SQL Server. To do this, follow these steps:
a. On the new computer, click Start, point to All Programs , point to Microsoft SQL Server
2008, and then click SQL Server Management Studio.
b. In the Connect to Server window, type the name of the server that is running Microsoft
SQL Server 2008 in the Server name box and then click Connect.
c. Right-click Databases, and then click Restore Database.
d. Under Destination to restore, type the name of the OrganizationName_MSCRM
database in the To database box.
e. Under Source for restore, click From device, click the ellipsis button ( ... ), add the
OrganizationName_MSCRM database, and then click OK.
f. Click to select the Restore check box, and then click OK.
g. Repeat steps 2b-2e for the MSCRM_CONFIG database.
If you must move more than one organization, repeat steps 2a-2f for each
organization database.
3. Update the configdb registry subkey on the computer that is running Microsoft Dynamics
CRM Server 2011. To do this, follow these steps:
a. On the computer that is running Microsoft Dynamics CRM Server 2011, click Start, click
Run, type regedit in the Open box, and then click OK.
b. Locate registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM.
9
Note
c. Right-click configdb, and then click Modify.
d. In the Value data box, change the data source to the name of the new SQL Server, and
then click OK. For example, the string value in the Value data box should resemble the
following:
Data Source= <NewSQLServeName>r ;Initial Catalog=MSCRM_CONFIG;Integrated
Security=SSPI
If multiple Microsoft Dynamics CRM roles are in your deployment, you must update
the configdb registry key for all the server roles.
If you use the Microsoft Dynamics CRM Reporting Extensions and if you are not
moving the Microsoft SQL Server Reporting Services server, you must update the
configdb subkey on the computer on which the Microsoft Dynamics CRM Reporting
Extensions are installed.
4. Configure the Microsoft Dynamics CRM application to point to the new SQL Server and
Microsoft SQL Server Reporting Services. To do this, follow these steps:
a. On the computer that is running Microsoft Dynamics CRM Server 2011, click Start, point
to All Programs, point to Microsoft Dynamics CRM 2011 , and then click Deployment
Manager.
b. Click Organizations.
c. Right-click the organization that you moved to the new computer that is running SQL
Server, and then click Disable.
d. Right-click the organization that you disabled, and then click Edit Organization.
e. Type the new name of the SQL Server and the new URL for the Microsoft SQL Server
Reporting Services server.
f. Click Next two times, and then click Apply.
g. Right-click the organization that you disabled in step 4c, click Enable, and then click Yes.
5. If you are using the Microsoft Dynamics CRM Reporting Extensions and if you are moving to
a new Microsoft SQL Server Reporting Services server, you must install the Microsoft
Dynamics CRM Reporting Extensions on the new server that is running Microsoft SQL Server
Reporting Services.
Redeploy the Microsoft Dynamics CRM

deployment that includes the Microsoft Dynamics
CRM Server 2011 within the same domain or to
another domain
1. Back up the OrganizationName_MSCRM databases. To do this, follow these steps:
a. On the computer that is running SQL Server, click Start, point to All Programs, point to
Microsoft SQL Server 2008, and then click SQL Server Management Studio.
10
Important
Note
b. Expand Databases, right-click the OrganizationName_MSCRM database, point to
Tasks, and then click Back Up.
c. Under Destination, add the location to save the backup file, and then click OK.
d. Repeat steps 1b and 1c for any other OrganizationName_MSCRM database that must be
moved.
2. Install Microsoft Dynamics CRM 2011 on the new computer that will run Microsoft Dynamics
CRM Server 2011.
3. Install the Microsoft Dynamics CRM Reporting Extensions.
You will not be able to import an organization until the Microsoft Dynamics CRM
Reporting Extensions are installed.
4. Restore the OrganizationName_MSCRM databases on the new computer that is running
SQL Server. To do this, follow these steps:
a. On the new computer that is running SQL Server, click Start, point to All Programs,
point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
b. Right-click Databases, and then click Restore Database.
c. Under Destination to restore, type the name of the OrganizationName_MSCRM
database in the To database box.
d. Under Source for restore, click From device, click the ellipsis button ( ... ), add the
OrganizationName_MSCRM database, and then click OK.
e. Click to select the Restore check box, and then click OK.
f. Repeat steps 3b-3e for any additional OrganizationName_MSCRM databases.
5. Import the organization into the new deployment of Microsoft Dynamics CRM 2011. To do
this, follow these steps:
a. On the new computer that is running Microsoft Dynamics CRM Server 2011, click Start,
point to All Programs, point to Microsoft Dynamics CRM 2011, and then click
Deployment Manager.
b. Right-click Organizations, and then click Import Organization.
c. If you are using the Workgroup edition of Microsoft Dynamics CRM, you are prompted to
delete the existing organization. Click OK to delete the organization that was created
during the installation.
This action does not delete the actual OrganizationName_MSCRM database
from the server that is running SQL Server.
d. In the SQL Server box, click the computer to which you restored the
OrganizationName_MSCRM database, click the organization database in the
Organization database box, and then click Next.
e. Type the display name and the name for the organization, and then click Next.
f. Type the URL in the SQL Server Reporting Services URL box, and then click Next.
g. Select the method in the Method for the Mapping of the Users list, and then click Next.
h. Map the users, and then click Next.
11
Note
Note
i. In the System Requirements dialog box, click Next, and then click Import.
If you plan to use the same Microsoft Dynamics CRM E-mail Router, you must run the
Configuration Wizard to configure the router for the new environment.
You must run the Configuration Wizard for the Microsoft Dynamics CRM for Outlook to
connect to the new Microsoft Dynamics CRM Server 2011.
Move the Microsoft Dynamics CRM Server or one

of the Microsoft Dynamics CRM server roles.
However, leave the SQL Server and the SQL
Server Reporting Services server intact
1. Install the Microsoft Dynamics CRM Server 2011 or server role on a new server. To do this,
follow these steps:
a. On the new computer, install Microsoft Dynamics CRM Server 2011.
b. During the installation process, type the name of the SQL Server on which the
MSCRM_CONFIG database exists in the Select Deployment Options dialog box, and
then click Connect to, and if necessary, upgrade an existing deployment.
c. Complete the installation.
2. Uninstall the Microsoft Dynamics CRM Server 2011 or the server role from the old Microsoft
Dynamics CRM Server 2011. To do this, follow these steps:
a. In Control Panel, open the Programs and Features item.
b. Right-click Microsoft Dynamics CRM 2011 Server, and then click Uninstall/Change.
c. Complete the removal wizard to remove Microsoft Dynamics CRM Server 2011 or server
role on the old server.
If you cannot uninstall the old Microsoft Dynamics CRM Server 2011 or server role in
step 2 because of a hardware failure, go to step 3.
3. Remove the server from Deployment Manager. To do this, follow these steps:
a. On the computer that is running Microsoft Dynamics CRM Server 2011, click Start, point
to All Programs, point to Microsoft Dynamics CRM 2011, and then click Deployment
Manager.
b. Click Servers. A list of the servers in the Microsoft Dynamics CRM deployment appears.
If no servers appear, right-click Servers, and then click Refresh.
c. Right-click the server that is not in the deployment, click Delete, and then click Yes. The
server is removed from the MSCRM_CONFIG database.
Depending on the Microsoft Dynamics CRM roles that you move, you may have to
run the Configuration Wizard for the E-mail Router to update the configuration. You
may also have to run the Configuration Wizard for the Microsoft Dynamics CRM for
Outlook to connect to the new Microsoft Dynamics CRM Server 2011.
12
See Also
Change a Microsoft Dynamics CRM service account
Change a Microsoft Dynamics CRM service

account
There are situations in which you may need to change the account that is used to run a Microsoft
Dynamics CRM service.
Change a Microsoft Dynamics CRM service

account by running a repair
The simplest way to change a service account is to run a repair operation and then specify the
new service account during the repair. There may be a short downtime as the services are
stopped and files are verified and possibly refreshed as part of the repair. For more information,
see Uninstall, change, or repair Microsoft Dynamics CRM Server 2011 in the Installing Guide.
To change the CRMAppPool service account, the appropriate permissions must be granted or the
CRMAppPool application pool will not start. Additionally, if you are using claims-based
authentication the CRMAppPool service account must have permission to access the claims-
based authentication token-signing certificate.
Manually change the CRMAppPool service

account
To manually change the CRMAppPool service account, include the domain account user in the
following groups in Active Directory:
 Domain Users Active Directory
 PrivUserGroup
 SQLAccessGroup
To do this, follow these steps:
1. Log on to a server as a user who has the domain administrator rights or the rights to update
these groups.
2. Right-click the Domain Users group in Active Directory, and then click Properties.
3. In the Group name box, type the name of the user who is running the Microsoft
Dynamics CRM application pool, and then click OK two times.
13
Important
Note
Direct user account membership to the Microsoft Dynamics CRM privusergroup
security group is required and group membership nesting under privusergroup
currently is not supported. For example, if you add a security group named
mycrmprivgroupusers to privusergroup, members of mycrmprivgroupusers will not
resolve as privusergroup members. This includes the CRMAppPool or the SQL
Server Reporting Services service identities, which if granted membership to
privusergroup through another security group, can cause system-wide failures in the
Microsoft Dynamics CRM web application and reporting features.
4. Repeat steps 2 and 3 for the PrivUserGroup group and for the SQLAccessGroup group.
If you have more than one Microsoft Dynamics CRM deployment installed, multiple groups exist
in Active Directory. Use the following steps to determine the groups that you want to update.
Determine the groups to update

1. Run the following SQL statement against the MSCRM_CONFIG database:
select id, friendlyname from organization
a. Note the GUID. For example, the GUID may be C8AB1D52-9383-4164-B571-
4C80D46674E3 Org Name.
b. Find the PrivUserGroup group and the SQLAccessGroup group in Active Directory. The
group name contains the GUID that you noted in step b.
2. Include the domain account user in the following groups on the Microsoft Dynamics CRM
server:
 The local IIS_WPG group
 The local CRM_WPG group
The domain account user must have the following local user rights:
 Impersonate a client after authentication
 Log on as a service
To do this, follow these steps:
a. On the Microsoft Dynamics CRM server, click Start, point to Administrative Tools, and
then click Local Security Policy.
b. Expand Local Policies, and then click User Rights Assignment.
c. Right-click Impersonate a client after authentication, and then click Properties.
d. Click Add User or Group.
You may have to click Location to select the domain instead of the local
computer.
e. In the Group name box, type the name of the user who is running the Microsoft
Dynamics CRM application pool, and then click OK two times.
f. Repeat steps 2c through 2e for the Log on as a service right.
14
3. Configure the CRMAppPool application pool security account to use a service principal name
(SPN). For steps about how to configure SPNs, see Configuring service principal names
(SPNs) on the Microsoft Dynamics CRM Resource Center.
4. If you have more than one Microsoft Dynamics CRM server and IIS kernel-mode
authentication is disabled, you must configure the CRMAppPool application pool security
account to be trusted for delegation. To do this, follow these steps:
a. Log on to the domain controller by using a user account that has domain administrator
permissions.
b. Start Active Directory Users and Computers. To do this, click Start, point to
Administrative Tools, and then click Active Directory Users and Computers.
c. Expand the domain, right-click the Microsoft Dynamics CRM application pool security
account, and then click Properties.
d. On the Delegation tab, click to select the Trust this user for delegation to any service
(Kerberos only) option.
e. Click OK.
5. Restart Internet Information Services (IIS). To do this, click Start, click Run, type IISRESET,
and then click OK.
See Also
Security considerations for Microsoft Dynamics CRM
Move the Microsoft Dynamics CRM 2011 deployment

By default, automatic error reporting is not enabled in Microsoft Dynamics CRM. Additionally,
Microsoft Dynamics CRM requires that Windows Error Reporting (WER) be enabled in order to
send error reports to Microsoft. To send error reports generated from the Microsoft Dynamics
CRM web application, WER must be enabled on the computer where Microsoft Dynamics CRM
Server 2011 is running. Similarly, to send reports generated from Microsoft Dynamics CRM for
Outlook, WER must be enabled where Microsoft Office Outlook is running.
The option to send WER reports must be enabled for the Microsoft Dynamics CRM organization.
This is done in the Settings area of the Microsoft Dynamics CRM client applications.
Enable Windows Error Reporting (WER) for the Microsoft Dynamics CRM Web
application
1. On the computer where Microsoft Dynamics CRM Server 2011 is running, start Server
Manager. In the Resources and Support area, click Configure Windows Error
Reporting.
15
2. Select one of the following options:
 Yes, automatically send detailed reports
 Yes, automatically send summary reports
For more information about these options, see Windows Server Help.
Enable Windows Error Reporting (WER) for Microsoft Dynamics CRM for Outlook
1. In Control Panel, click Action Center, click Change Action Center settings, and then
click Problem Reporting Settings.
2. Select one of the following options.
 Yes, automatically send summary reports
 Automatically check for solutions and send additional report data, if needed
For more information about these options, see the Windows Server Help.
Note
You can also configure this setting for users by using Group Policy. For more information
about WER and Group Policy, see the Windows Server Help.
Turn on automatic Web application error reporting for the organization

1. In the Microsoft Dynamics CRM client application Settings area, under System, click
Administration, and then click Privacy Preferences.
2. In the Privacy Preferences dialog box, on the Error Reporting tab, select Specify the
Web application error notification preferences on behalf of users.
3. Select the option Automatically send an error report to Microsoft without asking the
user for permission, and then click OK.
See Also
Limit the number of asynchronous jobs picked up for each organization
Limit the number of asynchronous jobs

picked up for each organization
Update Rollup 3 for Microsoft Dynamics CRM Server 2011 introduces a new deployment-wide
setting that limits the number of asynchronous jobs that may be picked up for each organization.
This setting may help reduce asynchronous operation backlog when multiple organizations are
present. Without limiting the maximum number of jobs picked up, if a single organization in the
deployment submits a large number of asynchronous jobs, such as 3,000 jobs, the Asynchronous
16
Service may attend to those jobs first instead of attending to the fewer number of jobs submitted
by other organizations.
The following Windows PowerShell command sets the maximum number of items that can be
queued to 100 for each organization in the deployment.
Important
You must apply Update Rollup 3 for Microsoft Dynamics CRM Server 2011 or a later
version update rollup on all Microsoft Dynamics CRM server roles before you run this
Windows PowerShell command.
To configure the number of asynchronous jobs picked up for

each organization
add-pssnapin Microsoft.Crm.Powershell
$itemSetting = new-object
'System.Collections.Generic.KeyValuePair[String,Object]'("AsyncSelectMaxItems",100)
$configEntity = New-Object "Microsoft.Xrm.Sdk.Deployment.ConfigurationEntity"
$configEntity.LogicalName="Deployment"
$configEntity.Attributes = New-Object "Microsoft.Xrm.Sdk.Deployment.AttributeCollection"
$configEntity.Attributes.Add($itemSetting)
Set-CrmAdvancedSetting -Entity $configEntity
See Also
Monitoring and troubleshooting Microsoft

Dynamics CRM
This section describes tools and recommendations for monitoring and troubleshooting Microsoft
Dynamics CRM.
In This Section
Tracing overview
System Center Monitoring Pack for Microsoft Dynamics CRM 2011
Microsoft Dynamics CRM 2011 performance counters
17
Tracing overview
In Microsoft Dynamics CRM 2011, you can create trace files that monitor the actions that are
performed by the server and client applications. Trace files are helpful when you have to
troubleshoot error messages or other issues in Microsoft Dynamics CRM.
There are two methods to enable Microsoft Dynamics CRM Server tracing: deployment-level
tracing or server-level tracing. Choosing either method determines the range of server roles
monitored, the degree of control and how to enable tracing and the location of the trace files.
Additionally, Microsoft Dynamics CRM Reporting Extensions and Microsoft Dynamics CRM for
Outlook can be enabled for tracing.
In This Topic
Microsoft Dynamics CRM deployment-level tracing
Microsoft Dynamics CRM server-level tracing
Enable tracing for Microsoft Dynamics CRM Reporting Extensions for SQL Server Reporting
Services
Enable tracing for Microsoft Dynamics CRM for Outlook
Microsoft Dynamics CRM deployment-level tracing

Deployment-level tracing monitors all Microsoft Dynamics CRM server roles and services,
regardless of the server roles installed on the local computer. When deployment-level tracing is
enabled, all server roles are monitored such as Asynchronous Service, Sandbox Processing
Service, Unzip Service, Web application (w3wp), and Deployment Tools (mmc-Tools).
Corresponding trace files are created.
Deployment-level tracing is set by using Windows PowerShell commands and is maintained in
the MSCRM_CONFIG database. Deployment-level tracing can only be enabled from a computer
that has the Microsoft Dynamics CRM Deployment Tools server role.
The trace files are located in a folder on the computer where the Microsoft Dynamics CRM
Deployment Tools server role is running. By default, the location is C:\crmdrop\logs.
Caution
Trace files may contain sensitive or personal information. Use discretion when you send
trace files to other people, or when you give other people the ability to view the
information in a trace file.
When you turn on tracing it can significantly affect performance of the application. We
strongly recommend that you only turn on tracing for troubleshooting issues and turn off
tracing after the issue is resolved.
Important
Before you run Microsoft Dynamics CRM Windows PowerShell commands the
Microsoft.Crm.Powershell snap-in must be registered by running the Add-PSSnapin
18
Microsoft.Crm.PowerShell command. For more information, see Operating Microsoft
Dynamics CRM.
Tip
To get a list of the registered Windows PowerShell snap-ins run the Get-PsSnapin –
registered command.
View the current deployment-wide trace settings
Get-CrmSetting TraceSettings
Enable deployment-wide tracing

To turn on deployment-wide trace settings, run the following commands, in the order provided,
from the Windows PowerShell console on the computer where the Deployment Tools server role
is running.
$Setting = Get-CrmSetting TraceSettings
$Setting.Enabled = $True
Set-CrmSetting $setting
Disable deployment-level tracing

To disable tracing, run the following commands, in the order provided, from the Windows
PowerShell console on the computer where the Deployment Tools server role is running.
$Setting = Get-CrmSetting TraceSettings
$setting.Enabled = $False
Set-CrmSetting $setting
Trace files are not deleted when tracing is disabled. Additionally, services used by Microsoft
Dynamics CRM Server lock open the trace files. Therefore, you may have to restart any Microsoft
Dynamics CRM services and the World Wide Web Publishing Service if these services are
running on the computer where you want to delete the trace files.
Microsoft Dynamics CRM server-level tracing

Server-level tracing only monitors those Microsoft Dynamics CRM server roles that are running
on the local computer where server-level tracing is enabled. When server-level tracing is enabled,
trace files that are specific to the Microsoft Dynamics CRM server roles or services that are
running on the local computer are created. Server-level tracing does not require the Deployment
Tools role and can provide a greater degree of control where you can set specific trace values
such as what Microsoft Dynamics CRM features to trace or the maximum trace file size.
For more information about setting server-level tracing properties in Microsoft Dynamics CRM
2011, see How to enable tracing in Microsoft Dynamics CRM.
19
If both deployment-level and server-level tracing are enabled on the same computer, only server-
level tracing will be used.
Server-level tracing must be manually set in the Windows registry on the computer where one or
more Microsoft Dynamics CRM server roles are running.
The server-level tracing files are located in the Traces folder of the Microsoft Dynamics CRM
installation folder. By default, the location is C:\Program Files\Microsoft Dynamics CRM\Trace.
Enable or Disable server-level tracing
Caution
information that a trace file contains.
Caution
This task contains steps that tell you how to modify the registry. However, serious
problems might occur if you modify the registry incorrectly. Therefore, make sure that you
follow these steps carefully. For added protection, back up the registry before you modify
it. Then, you can restore the registry if a problem occurs. For more information about how
to back up and restore the registry, see: How to back up and restore the registry in
Windows.
On the Microsoft Dynamics CRM Server that you want to turn on server-level tracing, start
RegEdit and locate the following registry location.
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSCRM
Create the following two required new values.
1. Value name: TraceEnabled
 Type: DWORD (32-bit)
 Value: 0 or 1
If you use a value of 0, tracing is disabled. If you use a value of 1, tracing is enabled.
2. Value name: TraceRefresh
 DWORD (32-bit)
 Value: A number between zero and 99
This value must change in order for Microsoft Dynamics CRM to detect a change to any
of the other trace values in the Windows registry. For example, if the value is 2, you can
set it to 1 so that other trace values changes, such as a change to TraceCategories, will
be applied.
20
Enable tracing for Microsoft Dynamics CRM Reporting
Extensions for SQL Server Reporting Services
In Microsoft Dynamics CRM 2011, you can create trace files that monitor the actions that are
performed by Microsoft Dynamics CRM Reporting Extensions. Trace files are helpful when you
have to troubleshoot error messages or other issues in Microsoft Dynamics CRM Reporting
Extensions.
Caution
trace files to other people, or when you give others the ability to view the information that
a trace file contains.
You can enable tracing for Microsoft Dynamics CRM Reporting Extensions in two ways:
Using registry values:
Caution
to back up and restore the registry, see: How to back up and restore the registry in
Windows.
1. On the computer where you have installed Microsoft Dynamics CRM Reporting Extensions,
locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\
MICROSOFT\MSCRM
2. Set the following registry values:
 TraceEnabled = 1
 TraceDirectory = <directory path where traces will be stored>
You can also set other row values like TraceCategories, but they already have defaults.
3. Restart Microsoft SQL Server Reporting Services.
Using deployment properties:
1. Go to the DeploymentProperties table in the Configuration Database.
2. Locate the row with the value "TraceEnabled" and set its "BitColumn" column’s value to
"True".
Other row values like TraceCategories, TraceDirectory already have default values, but you
can change these values.
You will start seeing the traces in the directory specified in the TraceDirectory row in the
DeploymentProperties table.
21
3. Restart Microsoft SQL Server Reporting Services.
Registry settings take precedence over deployment properties. If there are any invalid entries in
the registry, for example, and TraceDirectory does not exist, the deployment properties are used.
Important
Traces will not be generated if the folder specified in TraceDirectory does not exist.
Enable tracing for Microsoft Dynamics CRM for Outlook

This section applies to Microsoft Dynamics CRM Online and on-premises versions of Microsoft
Dynamics CRM 2011. Microsoft Dynamics CRM for Outlook tracing monitors the instance of
Microsoft Dynamics CRM for Outlook that is running on the local computer. If an issue is isolated
to a particular user running Microsoft Dynamics CRM for Outlook, enabling Microsoft
Dynamics CRM for Outlook tracing can help determine the cause.
The Microsoft Dynamics CRM for Outlook tracing files are located in the C:\Users\<username>\
AppData\Local\Microsoft\MSCRM\Traces folder.
Caution
information that a trace file contains.
Enable or disable tracing for Microsoft Dynamics CRM for Outlook
1. On the computer running Microsoft Dynamics CRM for Outlook, click Start, click All
Programs, click Microsoft Dynamics CRM 2011, and then click Diagnostics.
2. Click the Advanced Troubleshooting tab, and then select Tracing to enable or click to clear
Tracing to disable.
3. Click Save.
The above steps turn on verbose tracing. You can reduce the amount of information during the
trace by setting the TraceCategories Windows registry value. For example, you can set the value
so that only error messages are recorded. Reducing the amount of logging can be helpful when
you troubleshoot specific issues, such as when you receive error messages going offline. To do
this, follow these steps.
Caution
to back up and restore the registry, click the following article number to view the article in
the Microsoft Knowledge Base: How to back up and restore the registry in Windows.
22
Notice that tracing must already be enabled for the following steps to work.
1. On the computer where you have installed Microsoft Dynamics CRM for Outlook start
RegEdit and locate and then click the following registry subkey: HKEY_CURRENT_USER\
Software\Microsoft\MSCRMClient.
2. If the TraceCategories string value does not exist add it. To do this, right-click MSCRMClient,
click New, click String Value, type TraceCategories and then press ENTER.
3. Right-click TraceCategories, click Modify, type Application.Outlook:Error, and then click
OK.
For more information about the values available for TraceCategories, see How to enable tracing
in Microsoft Dynamics CRM.
Trace files are not deleted when tracing is disabled.
System Center Monitoring Pack for Microsoft

Dynamics CRM 2011
The System Center Monitoring Pack for Microsoft Dynamics CRM 2011 enables you to administer
the Microsoft Dynamics CRM 2011 application in Microsoft System Center Operations Manager
(SCOM) 2007 SP1 and Microsoft System Center Operations Manager 2007 R2.
Download the System Center Monitoring Pack for Microsoft Dynamics CRM 2011 and System
Center Monitoring Pack for Microsoft Dynamics CRM 2011 Guide.
Microsoft Dynamics CRM 2011 performance

counters
Microsoft Windows includes a tool named Windows Performance Monitor. You can configure
Windows Performance Monitor to obtain and display performance data as system components
run on a Microsoft Dynamics CRM deployment.
Performance objects provide sets of counters that generate data about how various components
perform as they run in your Microsoft Dynamics CRM environment. For example, the Processor
object collects metrics that show how one or more microprocessors are performing on a particular
server.
Many performance objects are built into the operating system, and more are installed with
software applications and services. For example, the performance objects installed with SQL
Server and Exchange Server can help you monitor the performance of components that are
relevant to your system.
Monitor performance counters for a Microsoft Dynamics CRM 2011 application, such
as Microsoft Dynamics CRM for Outlook, Email Router or Microsoft Dynamics CRM
Server
1. On the computer where the Microsoft Dynamics CRM application is installed, click Start,
click Run, in the Run dialog box type perfmon into the Open field and then press
23
ENTER.
2. In the navigation pane of the Reliability and Performance Monitor window, select
Performance Monitor.
3. Click the Add (plus sign) toolbar icon in the right pane to open the Add Counters dialog
box.
Alternatively, you can create a new Data Collector Set to organize the CRM counters that
you want to monitor. For more information, see the Performance Monitor Help.
4. In the list of available performance objects, expand the object class that you want to
monitor. Most Microsoft Dynamics CRM performance object classes begin with “CRM.”
For example, select CRM Server to see the list of available counters for that object.
5. Highlight the names of the counters that you want to monitor, click Add, and then click
OK. The selected counters are added to the list of active counters in the Reliability and
Performance Monitor window, and the data that they generate is shown in the dynamic
graph.
For more information about Microsoft Dynamics CRM Server 2011 performance counters,
download Microsoft Dynamics CRM Performance Counters.
See Also

Microsoft Dynamics CRM 2011 provides several options that help make your deployment of
Microsoft Dynamics CRM 2011 run optimally, reliably, and securely. In most situations where
Microsoft Dynamics CRM is running in a production environment, we recommend that you apply
the latest update for all Microsoft Dynamics CRM applications shortly after the update becomes
available.
On-premises versions of Microsoft Dynamics CRM use two kinds of update technology, Setup
update and update rollups.
In This Topic
Microsoft Dynamics CRM 2011 Setup update
Microsoft Dynamics CRM 2011 application update rollup
Frequently asked questions about update rollups for Microsoft Dynamics CRM 2011
24
Microsoft Dynamics CRM 2011 Setup update
Microsoft Dynamics CRM 2011 Setup update, also known as self-healing Setup, makes sure that
you have the latest version of Setup. By using this Setup feature, you can update the Setup
program for Microsoft Dynamics CRM server applications (Microsoft Dynamics CRM Server 2011,
Microsoft Dynamics CRM Reporting Extensions, Microsoft Dynamics CRM Report Authoring
Extension, Microsoft Dynamics CRM Language Pack, and Microsoft Dynamics CRM E-mail
Router) before Setup installs anything on the computer. To use Setup update, select Get updates
for Microsoft Dynamics CRM during Setup.
For Microsoft Dynamics CRM for Microsoft Office Outlook, when you select Get updates for
Microsoft Dynamics CRM, the latest published update rollup is applied at the end of Setup.
For more information, see How to obtain the setup updates for Microsoft Dynamics CRM 2011.
Microsoft Dynamics CRM 2011 application update

rollup
Microsoft Dynamics CRM regularly publishes updates in an update rollup format. An update rollup
is a collection of software updates for a particular Microsoft Dynamics CRM application. Microsoft
fully tests and supports installing any update rollup for Microsoft Dynamics CRM at the time of its
release.
Distribution and application of Microsoft Dynamics CRM

updates
Microsoft Dynamics CRM 2011 is engineered to use Microsoft Update. Microsoft Update is a
service that can automatically download and install updates to Microsoft applications, such as
Microsoft Dynamics CRM Server 2011, Microsoft Dynamics CRM Reporting Extensions, Microsoft
Dynamics CRM Report Authoring Extension, Microsoft Dynamics CRM for Microsoft Office
Outlook, Microsoft Dynamics CRM Language Pack, and Microsoft Dynamics CRM E-mail Router.
During installation or upgrade of a Microsoft Dynamics CRM 2011 application, Setup asks
whether you want to opt in, which sets Microsoft Update to apply automatic updates. If you do not
choose to apply automatic updates during Setup, you can enable this feature later by turning on
automatic updates in the Windows Update area of Control Panel. For more information, see Turn
automatic updating on or off and Change how Windows installs or notifies you about updates.
When you enable Microsoft Update, updates are automatically downloaded for Microsoft
Dynamics CRM and for any other Microsoft applications that are enabled to use Microsoft
Update.
If you decide not to use Microsoft Update, you can still download update rollups from the
Microsoft Download Center and manually install updates or push them out to the appropriate
computers by using Windows Server Update Services (WSUS). For more information about
WSUS, see Windows Server Update Services.
25
For more information about how to manually apply an update, see the Microsoft Knowledge Base
article for the specific update rollup that you want to download. For more information, see
Microsoft Dynamics CRM 2011 updates and hotfixes.
Removing an update rollup

In most cases, you should not have to remove an update rollup. Although, you can typically
uninstall Microsoft Dynamics CRM update rollups after they are applied, some update rollups
cannot be uninstalled.
Important
The following update rollups cannot be uninstalled.
 Update Rollup 4 for Microsoft Dynamics CRM 2011 (for all applications including, Microsoft
Dynamics CRM Server 2011, Microsoft Dynamics CRM Reporting Extensions, Microsoft
Dynamics CRM for Microsoft Office Outlook, Microsoft Dynamics CRM E-mail Router, and
Microsoft Dynamics CRM Language Pack)
If an update rollup cannot be uninstalled, rolling back to a previous update rollup requires you to
uninstall the Microsoft Dynamics CRM 2011 application, reinstall the application, and then apply
the previous update rollup.
Update rollup requirements

An update rollup may require updates to required components, such as the Microsoft .NET
Framework or even an earlier Microsoft Dynamics CRM 2011 update rollup. For more information
about such requirements, see the Microsoft Knowledge Base (KB) article for the update rollup.
Important
 Subsequent update rollups to Microsoft Dynamics CRM 2011 Update Rollup 6 will require
that you first apply Microsoft Dynamics CRM 2011 Update Rollup 6. For example, to apply
Microsoft Dynamics CRM 2011 Update Rollup 7 (when it is available), you must first apply
Microsoft Dynamics CRM 2011 Update Rollup 6.
 Microsoft Dynamics CRM 2011 Update Rollup 6 (version 5.00.9690.1992) is slipstreamed into
the Microsoft Dynamics CRM 2011 applications, including Microsoft Dynamics CRM Server
2011, Microsoft Dynamics CRM Reporting Extensions, Microsoft Dynamics CRM for Microsoft
Office Outlook, Microsoft Dynamics CRM E-mail Router, and Microsoft Dynamics CRM
26
Language Pack, which are all available on the Microsoft Download Center. For more
information, see Update Rollup 6 for Microsoft Dynamics CRM 2011 is available.
Frequently asked questions about update rollups

for Microsoft Dynamics CRM 2011
How are update rollups packaged?
Each update package file corresponds to a Microsoft Dynamics CRM 2011 application and uses
the form CRM_version-KB_Article_Number-platform-application-Language.exe. For example, the
following list describes the Update Rollup 3 package files for the English version.
CRM2011-Server-KB2547347-ENU-amd64.exe. Microsoft Dynamics CRM Server 2011 Update
Rollup package.
CRM2011-Srs-KB2547347-LangID-amd64.3exe. Microsoft Dynamics CRM Reporting Extensions
Update Rollup package.
CRM2011-Bids-KB2547347-LangID-i386.exe. Microsoft Dynamics CRM Report Authoring
Extension Update Rollup package.
CRM2011-Client-KB2547347-LangID-amd64.exe. Microsoft Dynamics CRM for Microsoft Office
Outlook Update Rollup package for x64-bit editions.
CRM2011-Client-KB2547347-LangID-i386.exe. Microsoft Dynamics CRM for Microsoft Office
Outlook Update Rollup package for 32-bit editions.
CRM2011-Router-KB2547347-LangID-amd64.exe. Microsoft Dynamics CRM E-mail Router
Update Rollup package for x64-bit editions.
CRM2011-Router-KB2547347-LangID-i386.exe. Microsoft Dynamics CRM E-mail Router Update
Rollup package for 32-bit editions.
CRM2011-Mui-KB2547347-LangID-amd64.exe. Microsoft Dynamics CRM Language Pack
Update Rollup for x64-bit editions.
CRM2011-Mui-KB2547347-LangID-i386.exe. Microsoft Dynamics CRM Language Pack Update
Rollup for 32-bit editions.
What is the latest Microsoft Dynamics CRM 2011 update rollup?

The latest Microsoft Dynamics CRM 2011 update rollup is described in the Microsoft Knowledge
Base article Microsoft Dynamics CRM 2011 updates and hotfixes.
Should I apply the latest update rollup to my deployment?

In most situations, we recommend that you apply the latest update rollup. Microsoft fully tests and
supports installing any update rollup for Microsoft Dynamics CRM at the time of its release. After
the release of a Microsoft Dynamics CRM update rollup, if issues occur with the rollup, Microsoft
27
will work to address the issue as quickly as possible. For help and support contact information,
see Microsoft Dynamics CRM Customer Service and Support.
Does an update rollup require additional configuration after I

install it?
Some individual updates may require a Windows registry modification or require you to run a
script to finish. For more information about any additional configuration that may be required after
you install an update rollup, see the section “Hotfixes and updates that you have to enable or
configure manually” in the Microsoft Knowledge Base article that accompanies the update rollup.
Are the update rollups cumulative?

Yes, update rollups are typically cumulative. This means that the problems that are fixed in an
update rollup are also fixed in later update rollups. For example, Update Rollup 3 for Microsoft
Dynamics CRM Server 2011 contains all the fixes and feature improvements that are included in
Update Rollup 2 for Microsoft Dynamics CRM Server 2011.
Do I have to apply the previous update rollup before I can apply

a later one?
In most cases, you do not have to apply an earlier update rollup because update rollups are
cumulative. However, some update rollups require an earlier update rollup. For more information,
see Update rollup requirements.
How frequently can I expect a new update rollup to be released?

The Microsoft Dynamics CRM Sustained Engineering team is committed to releasing update
rollups approximately every 8 weeks.
How can I be notified when an update is released?

If you want to know when updates are released for Microsoft Dynamics CRM, you can sign up to
receive email notifications. Notifications may include information about security updates, updates
to Microsoft Dynamics CRM that address feature requests from customers, or the release of a
new version of Microsoft Dynamics CRM. You can sign up for these email notifications by using
either of the two methods that follow.
From a computer that is running a Microsoft Dynamics CRM client application:
1. In the Navigation Pane, click Settings, click Administration, and then click Product
Updates.
2. In the Microsoft Dynamics CRM Product Updates form, sign in to the Microsoft account
service.
3. Select the Subscribe box; confirm your email format, email address, and privacy options;
and then click Continue.
28
Note
Alternatively, you can receive notifications from the Microsoft Dynamics CRM Team Blog by
subscribing to the Really Simple Syndication (RSS) feed. Posts in a variety of topics are
published to the blog almost daily, and when an update rollup is released, you will typically
receive a corresponding blog post about the release via the RSS feed.
In what order should I apply an update rollup?

For server roles and server role groups, you must apply the same update rollup to them before
you bring them back online. Similarly, if you have Microsoft Dynamics CRM Server 2011 installed
on multiple computers, such as in a Network Load Balancing (NLB) configuration, you must
update all the nodes in the NLB cluster before you bring them back online. A mixed deployment of
Microsoft Dynamics CRM servers or server roles that are running different update rollup versions
is not supported.
Microsoft Dynamics CRM for Outlook clients typically function correctly when you connect to a
Microsoft Dynamics CRM server that has the following update rollup deployment configurations:
 Microsoft Dynamics CRM for Outlook clients that are running an earlier update rollup than the
server, which is running the next update rollup. For example, your client is running Update
Rollup 2 for Microsoft Dynamics CRM for Outlook, and it is connected to a server that is
running Update Rollup 3 for Microsoft Dynamics CRM Server 2011.
 Microsoft Dynamics CRM for Outlook clients that are running a later update rollup than the
Microsoft Dynamics CRM server, which is running the earlier update rollup. For example, your
client is running Update Rollup 3 for Microsoft Dynamics CRM for Outlook, and it is
connected to a server that is running Update Rollup 2 for Microsoft Dynamics CRM Server
2011.
For optimal user experience, we recommend that you apply update rollups to your clients soon
after you update to Microsoft Dynamics CRM Server 2011.
How can I check my computer to see if an update rollup is

applied?
You can check whether an update rollup is applied by using either of these two methods:
 Click Start, open Control Panel, open Programs and Features, click View installed
updates, and then look for Microsoft Dynamics CRM Server 2011 in the list.
For clients that are running Windows XP, use similar steps to open Add or Remove
Programs.
 View the details of a binary file, such as the CrmVerServer.dll file, in \Program Files\Microsoft
Dynamics CRM\Server. To view the file details, right-click the file, click Properties, click the
Version tab, and then view the file version.
See Also
29
Improving performance and optimizing Microsoft Dynamics CRM 2011
Improving performance and optimizing

Microsoft Dynamics CRM 2011
This section describes methods and resources that can help you improve performance and
optimize Microsoft Dynamics CRM, such as by improving web browser page load times when you
open a form.
IIS compression
By default, Microsoft Dynamics CRM 2011 is configured to compress web responses that are
sent to web browser clients. However, Microsoft Dynamics CRM 2011 does not configure the
compression of HTTP responses sent to SDK clients, which includes Microsoft Dynamics CRM
for Outlook. This is because HTTP compression of dynamic content is an IIS-wide setting that
cannot be configured at the Microsoft Dynamics CRM website level.
To configure Microsoft Dynamics CRM Server 2011 to compress the HTTP responses that are
sent to Microsoft Dynamics CRM SDK clients, turn on IIS dynamic compression for the SOAP
responses that are returned by Microsoft Dynamics CRM Server. To do this, run the following
command on each of your Microsoft Dynamics CRM web application or API servers and then
restart each server:
Warning
Because IIS dynamic compression for SOAP responses is an IIS server-wide setting,
enabling it may cause unexpected behavior or failure in applications running on the IIS
server that cannot use it.
%SYSTEMROOT%\system32\inetsrv\appcmd.exe set config
-section:system.webServer/httpCompression /+"dynamicTypes.[mimeType='application/soap
%u002bxml; charset=utf-8',enabled='true']" /commit:apphost
For more information about configuring HTTP compression of dynamic content on an IIS server,
see HTTP Compression <httpCompression>.
Antivirus scans and Microsoft Dynamics CRM

When you run an antivirus application on a computer that is running Microsoft Dynamics CRM
Server 2011 or a dependent technology, Microsoft Dynamics CRM performance can be adversely
affected. Moreover, antivirus applications may lock certain files making them inaccessible.
Because antivirus applications can reduce the performance of application servers, instances of
SQL Server, Active Directory domain controllers, Microsoft SQL Server Reporting Services
30
servers, and Microsoft Dynamics CRM client computers, you may want to exclude certain files
from file level antivirus scanning.
Warning
Make sure that any plans to exclude files from antivirus scanning comply with your
internal information technology (IT) management policies.
For more information, including a suggested list of files for exclusion from antivirus applications,
see Antivirus exclusion considerations for Microsoft Dynamics CRM.
Performance and optimization resources for

Microsoft Dynamics CRM
The following documentation can help you improve performance and reliability with Microsoft
Dynamics CRM 2011 and Microsoft Dynamics CRM Online.
Optimizing and Maintaining a Microsoft Dynamics CRM 2011 Server Infrastructure
Optimizing and Maintaining Client Performance for Microsoft Dynamics CRM 2011 and CRM
Online
Microsoft Dynamics CRM 2011 Performance and Scalability on Intel Processor-based Servers
with Solid-State Drives
See Also
Microsoft Dynamics CRM 2011 Operating and Maintaining Guide
Microsoft Dynamics CRM Server 2011 Known Issues
Microsoft Dynamics CRM Server 2011 Known

Issues
This section describes Microsoft Dynamics CRM Server 2011 known issues.
In This Topic
An "A failure was encountered while launching the process serving application pool
'CRMAppPool'" message is logged in the Application log
A "Server Error in '/' Application" error message appears when you try to run a report in a multi-
tenant deployment
31
"Failure: The SQL Server '{0}' is unavailable" error message when you try to create an
organization
“External Error – No such object on server” error message when you try to enable a user
Microsoft Dynamics CRM mobile issues when you use AD FS 2.0
The computer that is running SQL Server 2008 R2 indicates 100% CPU utilization
An "A failure was encountered while launching

the process serving application pool
'CRMAppPool'" message is logged in the
Application log
This error message may be recorded when you configure the CRMAppPool application pool for a
domain account user that does not have sufficient permission. For information about how to grant
sufficient permission, see Change a Microsoft Dynamics CRM service account in this guide.
A "Server Error in '/' Application" error message

appears when you try to run a report in a multi-
tenant deployment
You may receive this error message when you try to run a report in a multi-tenant deployment on
a newly created organization. This can occur when the following conditions are true:
 You create an organization in addition to the default organization.
 You specify a computer running Microsoft SQL Server Reporting Services that is different
than the Microsoft SQL Server Reporting Services that is specified for the default
organization.
You must specify the same computer that is running Microsoft SQL Server Reporting Services for
the new organization that you specified for the default organization. Multiple Microsoft SQL Server
Reporting Services computers within the same Microsoft Dynamics CRM Server 2011
deployment are not supported. However, running multiple Microsoft SQL Server Reporting
Services computers in a network load balancing cluster configuration is supported.
To work around this issue, you must specify and use a single Microsoft SQL Server Reporting
Services computer for the deployment.
"Failure: The SQL Server '{0}' is unavailable" error

message when you try to create an organization
You may receive this error message when you try to create an organization by using the
Deployment Manager.
32
This issue may occur when you have configured the default security policy by using the Security
Configuration Wizard on on the computer where the instance of SQL Server is running that
maintains the configuration database.
To work around this issue, turn on network discovery on the computer where the instance of SQL
Server is running.
Turn on network discovery

1. Start Control Panel, and then click Network and Sharing Center.
2. Click Change advanced sharing settings.
3. Expand Domain, and in the Network discovery area, click Turn on network discovery.
4. Click Save Changes.
“External Error – No such object on server” error

message when you try to enable a user
You may receive this error when the following conditions are true:
1. You disable a Microsoft Dynamics CRM user.
2. You delete the associated Active Directory account for the Microsoft Dynamics CRM user.
3. You add a new Active Directory account that uses the same name as the original Active
Directory account.
4. You try to enable the Microsoft Dynamics CRM user.
To work around this issue, follow these steps.
Add a Microsoft Dynamics CRM user that was previously deleted from Active
Directory
1. Create an Active Directory user account that will only be used as an interim step to
resolve this issue. For example, you can name the Active Directory user account
tempuser. For information about how to create a new Active Directory user, see Active
Directory Users and Computers Help.
2. In Microsoft Dynamics CRM, in the Settings area, click Administration, and then click
Users to locate and open the User form for the Microsoft Dynamics CRM user that
cannot be enabled.
3. Click Enable. When you receive the error message, click OK to be able to edit the form.
4. Type the Active Directory user account that is only used to resolve this issue, such as
tempuser, press the Tab key, and then click Save.
5. Click Enable.
6. Type the Active Directory user account that you were unable to select before, press the
Tab key, and then click Save.
33
Microsoft Dynamics CRM mobile issues when you
use AD FS 2.0
The following topics describe issues that may occur when you use Microsoft Dynamics CRM
mobile that is configured to use AD FS 2.0.
You cannot sign out of Microsoft Dynamics CRM when you use a
mobile device
When you use a mobile device and sign out of Microsoft Dynamics CRM, the sign out screen
does not indicate that the sign out has completed. This issue can occur when the following
conditions are true:
 You use a mobile device, such as a Blackberry Curve.
 The Microsoft Dynamics CRM deployment is configured to use AD FS 2.0 authentication.
For information about how to resolve this issue, see the "Customize Mobile Express for Microsoft
Dynamics CRM" topic that is in the Microsoft Dynamics CRM SDK.
Some application pages do not display completely when viewed

by mobile users
Some pages, such as the sign-in and sign-out pages presented to external mobile device users
through an Internet-facing deployment (IFD), cannot be completely viewed. Additionally, these
pages cannot be read by screen reading software.
For information about how to resolve this issue, see the "Customize Mobile Express for Microsoft
Dynamics CRM" topic that is in the Microsoft Dynamics CRM SDK.
The computer that is running SQL Server 2008 R2

indicates 100% CPU utilization
This issue occurs because the Ghost Cleanup task uses 100% of the CPU on an idle system in
Microsoft SQL Server 2008. To resolve this issue, apply the following update that is most
appropriate for you.
Cumulative Update package 1 for SQL Server 2008 R2
Cumulative update package 7 for SQL Server 2008 Service Pack 1
See Also
34
Backing Up the Microsoft Dynamics CRM
System
To recover from any scenario, you must back up all needed information and store a copy off site.
A backup plan should be created and rehearsed for all Microsoft Dynamics CRM components and
services to make sure that, if a disk or other failure occurs, the maximum amount of data is
recoverable.
In This Topic
Backup requirements summary
Selecting a backup type
Backing up Windows Server
Backing up Active Directory
Backing up SQL Server, including Reporting Services
Backing up Microsoft Dynamics CRM Server 2011
Exporting customizations and solutions
Backup requirements summary

Backup requirements vary according to the servers involved. The following table is a summary of
what to back up for Microsoft Dynamics CRM.
Server What to back up for Microsoft Dynamics CRM Comments
Domain Full System State None.

controller
Exchange Backup not required by Microsoft Dynamics CRM. Backup may be required

Server for Exchange Server.
SQL MSCRM_CONFIG The

Server OrganizationName_MSCRM OrganizationName_MSCR
M and ReportServer
master
databases should have full
msdb database backups and
ReportServer transaction log backups.
ReportServertempdb For databases that are
rarely updated, such as
msdb, you may select only
full database backup.
35
Server What to back up for Microsoft Dynamics CRM Comments
Backups of the master

and msdb databases are
not required by Microsoft
Dynamics CRM but should
be part of an overall
backup strategy.
SharePoin Backup recommended if SharePoint integration is If you have enabled

t enabled. SharePoint integration, we
recommend that you back
up the SharePoint
databases. For more
information, see the
SharePoint
documentation.
Microsoft web.config The web.config file is

Dynamics (Default location: c:\Program Files\Microsoft Dynamics required only if the file has
CRM CRM\CRMWeb) been changed from the
Server default settings.
Windows registry:
2011 Windows registry subkey.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
MSCRM
Selecting a backup type

Windows Server 2008 supports external and internal hard disks, optical media drives, and
removable media drives. To perform a scheduled backup, as a best practice, use an external hard
disk that supports either USB 2.0 or IEEE 1394.
In Windows Server 2008, you can perform three types of backup:
 System state backup, which includes all the files that are required to recover Active Directory.
 Critical-volumes backup, which includes all the volumes that contain system state files.
 Full server backup, which includes all volumes on the server.
Backing up Windows Server

Windows Server has a backup tool that lets you back up important company data to disk or
removable media. The scheduling capability found in the Backup and Restore Wizard provides
data backup for the server itself and workstations in the small business network. The data backed
up includes security information, file and share permissions, and registry data. For data security,
36
only a member of the Administrators or Backup Operators group can perform a backup. Individual
files and directories on the server can be restored by using the Backup and Restore Wizard.
Backing up Active Directory

The Backup and Restore Wizard can back up System State data, which includes Active Directory,
system startup files, the Component Services Class Registration database, the registry, and
SysVol. Possible backup locations for System State data include floppy disks, hard disks,
removable media, recordable compact discs, and tapes.
Although we recommend that you back up Active Directory, the only way to avoid data loss is to
have multiple Active Directory domain controllers. Then, if a domain controller fails, the other
domain controllers will have a complete copy of the directory. With a backup, you have data only
as recent as your last backup.
Active Directory is a transacted database system that uses log files that support roll-back
semantics to make sure that transactions are committed to the database. The files associated
with Active Directory are as follows:
 Ntds.dit. The database.
 Edbxxxxx.log. Transaction logs.
 Edb.chk. Checkpoint file.
 Res1.log and Res2.log. Reserved log files.
Ntds.dit grows as the database fills up. However, the logs are of fixed size (10 MB). Any change
made to the database is also appended to the current log file, and its disk image is always kept
up to date.
Edb.log is the current log file. When a change is made to the database, it is written to the Edb.log
file. When the Edb.log file is full of transactions, it is renamed to Edbxxxxx.log. (It starts at 00001
and continues to increment by using hexadecimal notation.) Because Active Directory uses
circular logging, old log files are deleted as soon as they have been written to the database. At
any point in time, you will have the Edb.log file and maybe one or more Edbxxxxx.log files.
The Edb.chk file stores the database checkpoint, which identifies the point where the database
engine has to replay the logs, generally at the time of recovery or initialization.
Res1.log and Res2.log are "placeholders," designed to reserve (in this case) the last 20 MB of
disk space. This gives the log files sufficient room for a graceful shutdown if all other disk space is
consumed.
For more information, see:
Backup and Recovery (Windows Server 2008)
Administering Active Directory Backup and Recovery (Windows Server 2008)
Backing Up and Restoring Data for Windows Server 2003
Server Clusters: Storage Best Practices for Windows 2000 and Windows Server 2003
How to use the backup feature to back up and restore data in Windows Server 2003
37
Backing up SQL Server, including Reporting
Services
The Backup and Restore Wizard in Windows Server 2008 uses Volume Shadow Copy Services
(VSS) to back up Microsoft SQL Server databases. An alternative solution that can be used while
SQL Server runs is the built-in backup. Use SQL Server Management Studio to create a backup
of the SQL Server databases. Then, you can run a backup job from the Backup and Restore
Wizard to include database backups that Reporting Services created. You would schedule the
backup routing in Reporting Services to run first, followed by a backup job run in the Backup and
Restore Wizard. For more information about SQL Server backups, see SQL Server Books Online.
Microsoft Dynamics CRM creates at least two Microsoft Dynamics CRM-specific databases on
SQL Server. In addition, Microsoft Dynamics CRM requires the default master and msdb SQL
Server databases for database services and the default report server SQL Server databases for
Reporting Services. The databases that make up a Microsoft Dynamics CRM system on SQL
Server are as follows:
 OrganizationName_MSCRM
 MSCRM_CONFIG
 ReportServer
 ReportServertempdb
 master
 msdb
Note
Your Microsoft Dynamics CRM deployment may include more than one
OrganizationName_MSCRM database.
The SQL Server backup plan should address each of these databases to make sure that
Microsoft Dynamics CRM could recover if one, or all, databases fail. If your organization already
has SQL Server or another database application, your database administrator may have a
database backup strategy. However, if this is the first database application in your organization,
you can create and maintain scheduled jobs to perform the necessary backups by using the
Maintenance Plan Wizard in SQL Server Management Studio. To start the Maintenance Plan
Wizard, in Reporting Services, expand the server, expand the Management folder, right-click the
Maintenance Plans folder, and then click Maintenance Plan Wizard.
Your backup plan for the Microsoft Dynamics CRM databases provides you a backup set that
includes a full database backup and some number of transaction log backups, depending on the
Microsoft Dynamics CRM installation and the frequency with which you determine whether you
must have backups. For more information about backup and restore strategies, see SQL Server
Books Online.
For databases that are updated infrequently, such as the msdb database, you might perform only
full database backups. The OrganizationName_MSCRM, MSCRM_CONFIG, and ReportServer
databases should have both full database and transaction-log backups.
38
Databases on which transaction log backups will be performed must have the Full recovery
model database property set. You can set this property through SQL Server Management Studio.
For more information about how to set database properties, see SQL Server Books Online.
Schedule full database backups frequently enough to reduce the number of restores after a
failure. For example, if one day's data loss is acceptable, you can back up the transaction log one
time per day, and back up the database one time per week. If only one hour's maximum data loss
is acceptable, you can back up the transaction log one time per hour. To reduce the number of
restores, back up the database one time per day.
To create a database maintenance plan for scheduled backups, run the Maintenance Plan Wizard
from SQL Server Management Studio. Select the option to back up the database as part of the
maintenance plan for a full database backup. Select the option to back up the transaction log as
part of the maintenance plan for a transaction log backup.
Your computer that is running SQL Server should also be designed with a level of fault-tolerance
that is correct for a database server. This includes a RAID-5 disk array for your databases and a
RAID-1 (mirror) for your transaction logs. With the correct level of hardware fault-tolerance,
restoring from backup should be a very uncommon occurrence.
For information about the other options available in these maintenance plans, such as where to
store the backups, see the Maintenance Plan Wizard topics in SQL Server Books Online.
For more information about how to back up and restore SQL Server databases, see:
SQL Server Books Online
Backing Up and Restoring Databases in the SQL Server
Optimizing Backup and Restore Performance in SQL Server
Backing up Microsoft Dynamics CRM Server 2011

Backing up and restoring the Microsoft Dynamics CRM Server 2011 basically involves the
following data:
 Microsoft Dynamics CRM Server 2011 database files (explained previously)
 Microsoft Dynamics CRM Server 2011 program files
 Microsoft Dynamics CRM website files
Important
 For information about how to back up solutions and customizations that have been
implemented outside of the Microsoft Dynamics CRM application, contact your solution
vendor.
 We recommend that you keep a record of your current Microsoft Dynamics CRM update
rollup level. Therefore, if failure recovery is required, the appropriate Microsoft Update can be
reapplied.
By default, all Microsoft Dynamics CRM program files are located in the following folder:
C:\Program Files\Microsoft CRM\
By default, the Microsoft Dynamics CRM website files are located in the following folder:
39
C:\Program Files\Microsoft CRM\CRMWeb
Exporting customizations and solutions

The Solutions feature can be used to export all unmanaged solution customizations such as
modified forms, views, and mappings. The Solutions feature is located in the Customizations
area of the Settings area in the Microsoft Dynamics CRM web application navigation pane. It is a
good practice to export your customizations before you make changes so that they may be
imported back if there is unexpected behavior. For more information about how to export and
import solutions, see the Transportable customizations.
See Also
Failure Recovery
Failure Recovery
To understand the failure-recovery procedures, you must examine several different scenarios to
learn how restoration occurs in each case. For each scenario in this guide, total server failure is
assumed. The following scenarios contain information that shows the steps to ensure successful
recovery:
 Scenario A: SQL Server failure
 Scenario B: Microsoft Dynamics CRM Server 2011 failure
 Scenario C: Exchange Server failure
 Scenario D: Active Directory failure
 Microsoft Dynamics CRM for Outlook failure recovery
See Also
Microsoft Dynamics CRM 2011 Implementation Guide
Scenario A: SQL Server failure

If the computer that is running Microsoft SQL Server fails, you must restore the databases from
backup, and then reassociate them with the Microsoft Dynamics CRM deployment.
Scenario-A recovery
40
To recover from this failure, follow these steps:
1. Install Windows Server 2008 and make sure that the computer is in the same domain as
the Microsoft Dynamics CRM Server 2011. In addition, you should use the same
database name and disk structure. If you change either of these, you must take additional
steps to correctly restore the SQL Server databases.
2. Install SQL Server.
3. If you have a valid backup of the master database, restore that backup. For more
information, see Restoring the master Database in SQL Server Books Online.
4. Restore the msdb database. For more information, see Restoring the model and msdb
Databases in SQL Server Books Online.
5. Restore the MSCRM_CONFIG and OrganizationName_MSCRM databases. For more
information about how to restore databases, see Backing Up and Restoring Databases.
6. If Microsoft SQL Server Reporting Services and the Microsoft Dynamics CRM 2011
Connector for SQL Server Reporting Services are also installed on the instance of SQL
Server, restore the ReportServer and ReportServertempDB databases. For more
information about how to restore databases, see Backing Up and Restoring Databases.
7. If you restored the MSCRM_CONFIG database, you must run Microsoft Dynamics CRM
Server Setup and use the Connect to existing databases option on the Specify
Deployment Options page. If you did not restore the MSCRM_CONFIG database and the
database is functioning correctly, you can reconnect the organization database to the
system. To do this, in Deployment Manager right-click the organization and select
Disable, right-click the organization again, click Edit Organization, and then change the
SQL Server value in the wizard. For more information about how to edit an organization,
see the Deployment Manager Help.
This scenario is a worst-case situation, that is, total failure of the computer that is running SQL
Server. In other circumstances, such as the failure of a disk, you may only have to restore a
single database to recover the environment.
For more information about failure recovery for SQL Server, see Disaster Recovery Planning
(Database Engine).
See Also
Failure Recovery
Scenario B: Microsoft Dynamics CRM Server 2011 failure
Scenario B: Microsoft Dynamics CRM Server

2011 failure
Most of the Microsoft Dynamics CRM configuration information is stored on the computer that is
running SQL Server. Therefore, the information can be recovered if all, or part, of Microsoft
41
Dynamics CRM Server 2011 fails. Registry entries on the Microsoft Dynamics CRM Server 2011
are recovered when you run repair or reinstall processes for the Microsoft Dynamics CRM Server
2011 and Microsoft Dynamics CRM 2011 Connector for SQL Server Reporting Services.
We recommend that you keep a record of your current Microsoft Dynamics CRM update rollup
level. Therefore, if failure recovery is required, the appropriate update rollup can be reapplied.
Scenario-B recovery
If the computer that is running Microsoft Dynamics CRM Server 2011 fails, follow
these steps:
1. Install the operating system on another server and join the same domain as the computer
that is running SQL Server.
2. Install Microsoft Dynamics CRM Server 2011. During Setup, you must select Connect to,
and if necessary, upgrade an existing deployment when you are prompted. If
Microsoft Dynamics CRM 2011 Connector for SQL Server Reporting Services was also
installed on the computer that failed, install the Microsoft Dynamics CRM 2011 Connector
for SQL Server Reporting Services after Microsoft Dynamics CRM Server 2011 is
completed.
3. If the ISV.config and web.config files have been changed from their default settings,
restore these files from backup.
4. Publish all customizations. For information about how to publish customizations, see the
Microsoft Dynamics CRM Help.
See Also
Failure Recovery
Scenario C: Exchange Server failure
Scenario C: Exchange Server failure

The process to restore a Microsoft Exchange Server computer that is used by Microsoft
Dynamics CRM depends on the other uses of that instance of Exchange Server. Except for the
forward mailbox, Microsoft Dynamics CRM does not directly use Exchange Server mailboxes.
Note
Installing the E-mail Router on a computer that is running Exchange Server is not
required.
Scenario-C recovery
To restore Exchange Server in a Microsoft Dynamics CRM environment, follow these
steps: 42
1. Restore Exchange Server.
2. If the E-mail Router was installed on the computer that is running Exchange Server,
reinstall the E-mail Router.
3. Restore the Microsoft.Crm.Tools.EmailAgent.xml file. By default, this file is located in the
Drive:\Program Files\Microsoft CRM Email\Service folder. If this file is not available, you
must reconfigure the profiles, settings, users, queue, and forward-mailbox information by
running the E-mail Router Configuration Manager.
For more information about how to restore Microsoft Exchange Server 2003, see:
 How to Back Up and Restore an Exchange Computer by Using the Windows Backup
Program
 Disaster Recovery Includes Metabase Backup and Restore
 How to Recover or to Restore a Single Mailbox in Exchange Server 2003
 Microsoft Exchange Server 2003 technical library
For more information about how to restore Microsoft Exchange Server 2007, see:
 Single Mailbox Recovery
For more information about Microsoft Exchange Server 2010 backup and recovery see:
 Understanding Backup, Restore and Disaster Recovery
See Also
Failure Recovery
Scenario D: Active Directory failure
Scenario D: Active Directory failure

In most environments, it is highly unlikely that Active Directory will fail on its own, because more
than one Active Directory domain controller should be installed.
Scenario-D recovery
To recover from a failed domain controller, follow these steps:
1. Reinstall the Windows Server 2008 operating system.
2. Perform a system state restore.
Make sure that you have a method for recovering from an Active Directory failure. Regardless of
the size of your environment, you should consider having multiple domain controllers with regular
backups of the system state. If your backups are not current, any data that belongs to Microsoft
Dynamics CRM objects in Active Directory will be orphaned in SQL Server and therefore will be
unrecoverable. Any changes that are made in Microsoft Dynamics CRM, such as adding new
43
Microsoft Dynamics CRM users or queues, requires that Active Directory is backed up
immediately after the change.
One major problem can occur with Active Directory that stops Microsoft Dynamics CRM from
functioning. If an administrator unintentionally deletes the organizational unit (OU) that
corresponds to a Microsoft Dynamics CRM deployment, it becomes inoperable. Similarly, if any of
the OU security groups that are created by Microsoft Dynamics CRM are deleted (such as
PrivUserGroup, ReportingGroup, PrivReportingGroup, or SQLAccessGroup), Microsoft
Dynamics CRM will no longer function correctly. In either of these events, an authoritative restore
of Active Directory restores the deleted OU, and security groups, to their original state.
Important
If you cannot restore an Active Directory backup, you can create new security groups by
reinstalling Microsoft Dynamics CRM Server 2011 as a new deployment. After the
installation is complete you can import the organization databases.
For more information about Active Directory backup and recovery, see Steps for Backing
Up and Recovering AD DS.
See Also
Failure Recovery
Microsoft Dynamics CRM for Outlook failure recovery
Microsoft Dynamics CRM for Outlook failure

recovery
Microsoft Dynamics CRM for Microsoft Office Outlook with Offline Access includes functionality
that uses Microsoft SQL Server Express. This enables Microsoft Dynamics CRM users to work
offline with data synchronized to SQL Server when Microsoft Dynamics CRM for Microsoft Office
Outlook with Offline Access is brought online again.
In some cases, Microsoft Dynamics CRM users may want to back up the local Microsoft SQL
Server Express database. This is especially useful when Microsoft Dynamics CRM users are
offline for prolonged periods. The following table indicates different methods that can be used for
backing up Microsoft Dynamics CRM for Microsoft Office Outlook with Offline Access.
Backup Method What to Back Up for Microsoft Comments

Dynamics CRM
Offline backup Contents of Microsoft Dynamics CRM data Before you start the
directory. Default location is: backup, make sure that
SystemDrive:\Program Files\Microsoft the SQL Server (CRM)
service is stopped.
44
Backup Method What to Back Up for Microsoft Comments
Dynamics CRM
Dynamics CRM\LocaleCode\sql\ 5.0 Restart the service after

the backup is complete.
Online backup using MSDE_MSCRMbuildnumber.mdf Use SSMSE or

Microsoft tools MSDE_MSCRMbuildnumber_log.LDF sqlcmd.exe (a command-
line tool) that is available
for download.
Online backup using MSDE_MSCRMbuildnumber.mdf Look for tools that are

non-Microsoft tools MSDE_MSCRMbuildnumber_log.LDF compatible with Microsoft
SQL Server Express.
Microsoft SQL Server Management Studio Express (SSMSE) provides a graphical management
tool for Microsoft SQL Server 2008 Express Edition that includes backup and recovery features.
You can download SSMSE and sqlcmd.exe at Microsoft SQL Server 2008 Management Studio
Express.
If there is a problem with Microsoft Dynamics CRM for Microsoft Office Outlook with Offline
Access before the user can reconnect to the server, the backup can be used to restore Microsoft
Dynamics CRM functionality to the client. Microsoft Outlook should be in offline mode before you
restore the backup. When restored, you can then connect to the Microsoft Dynamics CRM Server
2011 (online mode). The data not already on the server will be transferred to the server from the
client. Be careful when reconnecting to the server. If you restore from an outdated backup, the
existing data on the server may have subsequently changed. However, neither Microsoft SQL
Server Express nor SQL Server recognizes this fact. Therefore you run the risk of overwriting
current data on the server by using older data from the offline client backup.
See Also
Failure Recovery
45

CRM2011IG OpandMaint

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CRM2011IG OpandMaint

Uploaded by

Copyright:

Available Formats

Microsoft Dynamics CRM 2011 Operating and

Operating Microsoft Dynamics CRM............................................................................................... 7

Move the Microsoft Dynamics CRM 2011 deployment....................................................................8

Change a Microsoft Dynamics CRM service account...................................................................13

Enable Windows Error Reporting.................................................................................................. 15

Limit the number of asynchronous jobs picked up for each organization......................................16

Monitoring and troubleshooting Microsoft Dynamics CRM...........................................................17

Updating Microsoft Dynamics CRM 2011.....................................................................................24

Improving performance and optimizing Microsoft Dynamics CRM 2011.......................................30

Microsoft Dynamics CRM Server 2011 Known Issues..................................................................31

Backing Up the Microsoft Dynamics CRM System.......................................................................35

Scenario A: SQL Server failure..................................................................................................... 40

Scenario B: Microsoft Dynamics CRM Server 2011 failure...........................................................42

Scenario C: Exchange Server failure............................................................................................ 42

Scenario D: Active Directory failure.............................................................................................. 43

Microsoft Dynamics CRM for Outlook failure recovery..................................................................44

Send us your comments about this

Using Windows PowerShell to perform Microsoft

Setting Microsoft Dynamics CRM properties manually

Move the Microsoft Dynamics CRM 2011

Redeploy the Microsoft Dynamics CRM

Move the Microsoft Dynamics CRM Server or one

Change a Microsoft Dynamics CRM service

Change a Microsoft Dynamics CRM service

Manually change the CRMAppPool service

Determine the groups to update

Enable Windows Error Reporting

Turn on automatic Web application error reporting for the organization

Limit the number of asynchronous jobs

To configure the number of asynchronous jobs picked up for

$configEntity = New-Object "Microsoft.Xrm.Sdk.Deployment.ConfigurationEntity"

$configEntity.Attributes = New-Object "Microsoft.Xrm.Sdk.Deployment.AttributeCollection"

Set-CrmAdvancedSetting -Entity $configEntity

Monitoring and troubleshooting Microsoft

Microsoft Dynamics CRM deployment-level tracing

Enable deployment-wide tracing

Disable deployment-level tracing

Microsoft Dynamics CRM server-level tracing

Enable tracing for Microsoft Dynamics CRM for Outlook

System Center Monitoring Pack for Microsoft

Microsoft Dynamics CRM 2011 performance

Updating Microsoft Dynamics CRM 2011

Microsoft Dynamics CRM 2011 application update

Distribution and application of Microsoft Dynamics CRM

Removing an update rollup

Update rollup requirements

Frequently asked questions about update rollups

What is the latest Microsoft Dynamics CRM 2011 update rollup?

Should I apply the latest update rollup to my deployment?

Does an update rollup require additional configuration after I

Are the update rollups cumulative?

Do I have to apply the previous update rollup before I can apply

How frequently can I expect a new update rollup to be released?

How can I be notified when an update is released?

In what order should I apply an update rollup?

How can I check my computer to see if an update rollup is

Improving performance and optimizing

Antivirus scans and Microsoft Dynamics CRM

Performance and optimization resources for

Microsoft Dynamics CRM Server 2011 Known

An "A failure was encountered while launching

A "Server Error in '/' Application" error message

"Failure: The SQL Server '{0}' is unavailable" error