• Option 1: If you customer is ok with upgrading all of the users to IE 8 or 9, they will see performance enhancements for sure comparing to IE 7.  However not an ideal option since enterprise customers are not moving as fast as smaller companies on their infrastructure and on the users’ operating system.
• Option 2: Update 2 IE settings and add a registry key to the user’s machine, I can’t believe what I am seeing.  CRM 2011 performs extremely well after the changes.  Here’s what I did.
  1. Change the Internet Explorer settings
     • Navigate to Tools | General | Tabs (Settings).
     • Unselect Enable Quick Tabs.
     • Select Let Internet Explorer decide how pop-ups should open.
     • Click OK and then restart the browser.
  2. Add the following registry key (by default, IE only has 2 connections)
     • Click Run  | Regedit.
     • Navigate to hkeycurrentuser\software\microsoft\windows\currentversion\internetsettings.
     • Add new DWORD MaxConnectionPerServer with Decimal value of 10.
     • Add new DWORD MaxConnectionsPer1_0Server with Decimal value of 10.
     • Close Regedit.

Thanks to my buddy, Jim Wang, for the great tips!

Please make sure you provide me your contact information so I can get in touch with you.

Thank you for your support!

Darren Liu

1. Turn BitLocker Off.
   • Navigate to Control Panel | System and Security | BitLocker Drive Encryption.
   • Click Turn Off BitLocker for the Hard Drive that has BitLocker On.
2. Install the HD Clone Software.
3. Follow the wizard to clone the hard drive.
4. Turn BitLocker On.

Break the solution into smaller solutions :  Since we have a 6MB unmanaged solution, we need to break it into smaller packages so the import and publish can be faster.  At this moment, we are breaking our solution into smaller unmanaged solutions.  So how should we break the big solution?   After learning from our colleagues and friends, we split our solution into 5 smaller solutions.  Here’s what we did:

1. Customization
   • Data Model
   • Form and Views
   • Web Resources
   • Global Option Sets
   • Site Map
   • Application Ribbon
2. Plugins
3. Processes
4. Reports and Dashboards
5. Security Roles (Note: It’s recommended to split our security roles into its own solution because when importing security roles, a lot of calculations are happening in the background, so importing security roles with other components could slow down the import quite a bit)

We are going to package our solution into managed solution.  The recommendation we received is to break the solution into smaller managed solutions.  Because managed solution is smaller because it only contains the delta customizations.  The table below will shows the customizations included in the file when you package the solution.

Change the timeout value: Out of the box CRM timeout values are too short for a big solution, it’ll timeout/hang.  Below are the things that you can do.  Thanks Alok from our team for the detail step by step instructions.

Registry Settings

1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
   

3. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
4. Rename the DWORD value to the following value:

   OLEDBTimeout
   

5. Right-click the DWORD value, and then click Modify.
6. In the Edit DWORD Value dialog box, type 86400 in the Value data box, click Decimal in the Base option, and then click OK.

   Note: According to the requirement of the computer that is running SQL server and the number of customization files, the value can be larger than 86400. The value of 86400 is equivalent to 24 hours.

7. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
8. Rename the DWORD value to the following value:

   ExtendedTimeout
   

9. Right-click the DWORD value, and then click Modify.
10. In the Edit DWORD Value dialog box, type 1000000 in the Value data box, and then click OK.
    
    Notes
    • In the Value data box, you can type a value that is larger than 1,000,000. However, do not type a value that is larger than 2,147,483,647. This is hexadecimal 0x7FFFFFFF.
    • If this key already exists, notice the current value. After you have completed the import or the upgrade for Microsoft Dynamics CRM, set the value of this key back to the original value or delete the key if it did not previously exist. The default OLEDB timeout value is 30 seconds.

Web.Config File

1. Navigate to the CRMWeb directory. Usually this directory is located in [Drive]:\Program Files\Microsoft Dynamics CRM\CRMWeb
2. Right-click the Web.config file, click Open With, and then click Notepad.
3. In Notepad, locate the following line.

   <httpRuntime maxRequestLength="8192"/>
   

4. Change change maxRequestLength="20000".
5. Save and then close the Web.config file.

MSCRM_CONFIG Settings

1. Execute the following on the MSCRM_CONFIG DB on the MSCRM SQL Server.

USE MSCRM_CONFIG

GO

UPDATE DeploymentProperties SET IntColumn=9000 WHERE ColumnName='SqlCommandTimeout'

Do an IIS Reset after you complete all of the steps above.

I hope this helps you in your CRM project.

Also the CRM Engineering for Enterprise Team and the CRM Content Publishing Team release a white paper today on Deploying Microsoft Dynamics CRM 2011 and CRM Online Solutions from Development through Test and Production Environment, which is available for download from the Microsoft Download Center. 

This white paper explores deploying real-world Microsoft Dynamics CRM solutions across test and production environments in reliable and repeatable ways by using automation. The paper also provides some automation example and highlights the specific constraints associated with deploying and testing solutions in a Microsoft Dynamics CRM Online environment. 

Thanks to the CRM team for the opportunity to contribute to this white paper.  Couple of my colleagues and myself contributed to this paper as well!

• You import a solution that contains a plug-in that has empty methods. You publish the customizations. When the plug-in is triggered in this situation, you receive the following error message:

  Unexpected Error
  An error has occurred.

  .

• The search results for system views in the Dynamics CRM 2011 client for Outlook are not compliant with the search results in the Microsoft Dynamics CRM web client.
• Assume that you enable the http compression setting on the Dynamics CRM server. In this situation, the Microsoft Dynamics CRM 2011 Outlook client does not receive responses for SDK calls as compressed. This problem occurs because the Outlook client does not send an "EnableDecrompression" http header with the request.
• The Dynamics CRM 2011 client for Outlook initiates background send requests to the CRM server. This behavior can cause high server load and decreased performance because these requests are not throttled. This fix throttles these background send requests.
• Consider the following scenario:
  • You create a custom entity that has a custom icon.
  • You create at least two records that begin with the letter "A."
  • You create a "1 to many" relationship from the custom entity to another entity.
  • You expose the Lookup field for the relationship to the custom entity in the related entity.
  • You log on to a Microsoft Dynamics CRM 2011 Outlook client that connects to the environment through IFD/Claims.
  • You clear the Microsoft Internet Explorer cache.
  • You create a new record for the related entity.
  • You run the auto-resolving lookup function by using the letter "A" for the custom entity.

  In this situation, you receive a warning message that states there are multiple matching records. Additionally, the icon does not appear.

• The Help files are updated.
• Assume that you configure the Dynamics 2011 client for Outlook. You browse to the Account folder or the Contact folder. In this situation, you experience slow performance when ribbons and menus are rendered.
• The Start Date field in the Fiscal Year Settings dialog box does not display the date that is converted according to the user time zone settings.
• The value for the Set this computer to be the synchronizing client in the Dynamics CRM 2011 client for Outlook is different if you open the personal settings dialog box by clicking the Options button in the Track In CRM pane in an email message or an appointment. Additionally, if you select the Set this computer to be the synchronizing client check box, the dialog box becomes unresponsive.
• Some duplicate attribute labels exist. Therefore, it is difficult to map data on imports.
• The Russian translations of the Create column heading and the Delete column heading are incorrect in the security role permissions.
• When you send a Direct Email message to a large dataset, duplicate email messages are generated.
• When you add a user in a multi-site domain, you experience slow performance after you click Save.
• Assume that you enable auditing for the Contact entity. If you use a Microsoft Dynamics CRM 2011 Client for Outlook, an auditing log is displayed every 15 minutes or every time that the Outlook client is synchronized with Microsoft Dynamics CRM 2011.
• Some translations for the Slovenian language are incorrect.
• Assume that you specify a comma as the decimal separator in the personal format settings. When you enter a decimal custom value in a Duration field, the value is rounded unexpectedly.
• When you export a static Microsoft Excel worksheet with non-English operating system settings, the Currency values are multiplied by 10,000.
• When you export a Duration field to an Excel worksheet, the value in the Duration field is displayed as text instead of as a number.
• If an organization starts many asynchronous operations, the Asynchronous Service allocates many resources to process those requests from the organization. In this situation, other organizations will have an increasing backlog of asynchronous operations. This fix introduces a new deployment setting, called AsyncSelectMaxItems, in the DeploymentProperties table. This setting limits the number of items that can be processed by a single organization at one time. By default, the value is not set. It can be set manually if you experience this issue.
• Metadata cache access for one organization is blocked if another organization is loading metadata.
• Assume that you create a contact who has a 200-character email message in Microsoft Dynamics CRM 4.0. When you upgrade the system to Microsoft Dynamics CRM 2011, you receive an upgrade error.
  When you create a contact who has a 200-character email message in Microsoft Dynamics CRM 2011, an internal server error occurs.
• When you add a URL that contains a query string parameter to a sitemap area or to a subarea in Microsoft Dynamics CRM 2011, the URL is rendered incorrectly.
• Some Swedish language translations are incorrect.
• Assume that you have a contact who has the Business Phone filed populated. When you add a new phone call activity by using the ribbon from the Activities area, the Phone Number field is not populated in the phone call activity.
• When you import a solution, some entities are not imported. Additionally, you receive the following error message:

  Cannot change the max length of the owneridname attribute.

• When you view the file properties of some files by clicking the Details tab, the value in the Company name field and the value in the Product name field are blank.

If you ever run into a situation that you imported your solution successfully and not able to publish it, the reason is because either the size of the solution might be too large or the SQL is not fast enough. 

We ran into this problem earlier this week.  We have a slow SQL server and the size of our solution is big, we can’t publish it and we don’t know what was the reason behind it since CRM didn’t provide any helpful error messages.

Cause:

After hours of troubleshooting, we finally figured out that CRM has a default timeout value of 300 seconds = 5 minutes. If any process takes more than 5 minutes, it’ll stop. 

Solution:

Modify the parameters in two different Web.config files:

File 1:

1. On the CRM application server, open Internet Information Services (IIS) Manager.
2. Expand the server name, and then expand Web Sites.
3. Right-click the Microsoft CRM Web site, and then click Open.
4. Right-click the Web.config file, click Open With, and then click Notepad.
5. In Notepad, locate the following line.

   <httpRuntime executionTimeout="300" maxRequestLength="8192"/>

   Change to

   <httpRuntime executionTimeout="3600" maxRequestLength="20000"/>

6. Save and then close the Web.config file.

File 2:

1. Browse to the folder in which you opened the Web.config file, expand the MSCRMServices folder.
2. Open the Web.config file with Notepad.
3. Locate the following line.

   <httpRuntime maxRequestLength="8192"/>

   Change to:

   <httpRuntime maxRequestLength="20000"/>

4. Save and then close the Web.config file.

I hope this will save you hours if you run into a similar situation.

• English
• Chinese (Simplified)
• Danish
• French
• German
• Japanese
• Portuguese
• Russian
• Spanish
• Turkish