You experience timeouts or slow performance when you reassign records from one user to another user in Microsoft Dynamics CRM 3.0

When you reassign records from one user to another user in Microsoft Dynamics CRM 3.0, you experience one of the following problems:

• You experience timeouts.
• You experience slow performance. When the records are being reassigned, Microsoft Dynamics CRM takes a long time to open the Microsoft Dynamics CRM forms.

Additionally, if you use System Monitor on a computer that is running Microsoft SQL Server, the performance counters show that the reassignment process causes high CPU usage and many SQL Server locks.

This problem occurs if you reassign many records from one user to another user. For example, this problem may occur if you use the Bulk Reassign functionality to assign the records.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft Dynamics CRM 3.0 server

Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers

Installation information

Install this hotfix on computers that are running the Microsoft Dynamics CRM 3.0 server.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Note If the default values are small, you may have to create or change the OleDbTimeout value and the ExtendedTimeout value. Then, the MSCRMFastReassign.exe tool can process all the records. To do this, follow these steps.

Create or change the OleDbTimeout value

1. In Registry Editor, locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
2. Double-click the OleDbTimeout value.
   
   Note If the OleDbTimeout value does not exist, create an OleDbTimeout value. To do this, follow these steps:
   1. Right-click MSCRM, point to New, and then click DWORD value.
   2. Type OleDbTimeout.
3. In the Edit DWORD Value dialog box, click Decimal, type 600 in the Value data field, and then click OK.
   
   Note The value of 600 represents 600 seconds. By default, the value is 30 seconds.

Create or change the ExtendedTimeout value

1. In Registry Editor, locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
2. Double-click the ExtendedTimeout value.
   
   Note If the ExtendedTimeout value does not exist, create an ExtendedTimeout value. To do this, follow these steps:
   1. Right-click MSCRM, point to New, and then click DWORD value.
   2. Type ExtendedTimeout.
3. In the Edit DWORD Value dialog box, click Decimal, type 5400000 in the Value data field, and then click OK.
   
   Note The value of 5400000 represents 5,400 seconds. By default, the value is 900 seconds.

To install this hotfix, follow these steps:

1. Move the MSCRMFastReassign.exe file to the following folder:
   C:\Program Files\Microsoft CRM\Tools
2. Log on to the Microsoft Dynamics CRM server as a user who has the Administrator role.
3. Run the MSCRMFastReassign.exe file.
4. In the Entity Reassignment Tool dialog box, select the user in the Current User list from whom you want to reassign the records.
5. In the New User list, select the user to whom you want to reassign the records.
6. Click Reassign.
   
   Note You cannot undo this action.

After you finish the reassignment process, you receive the following message: Notes

• The User1 placeholder represents the actual user who you select in the Current User list.
• The User2 placeholder represents the actual user who you select in the New User list.
• The tool may take 90 minutes or longer to reassign 900,000 records or more records, depending on the performance of the Microsoft Dynamics CRM server and the Microsoft SQL Server that are used.
• To determine the number of records that a user has, you must run a query against the Microsoft Dynamics CRM database in SQL Query Analyzer or in SQL Server Management Studio. You must run the query as a Microsoft Dynamics CRM Administrator, because the records that are displayed depend on which records the user has access to or has the visibility to see. If you want to see the records that are owned by the user for other entities, you must change FilteredContact to Filtered_EntityName. EntityName is the name of the other entity, such as FilteredAccount. This query estimates how long it will take the MSCRMFastReassign.exe tool to assign records from one Microsoft Dynamics CRM user to another Microsoft Dynamics CRM user. If accurate estimates of the time to run this tool are required, you should run this tool in a test deployment that contains a copy of the Microsoft Dynamics CRM production databases on similar hardware. To determine the number of records that a user has, run the following query against the Microsoft Dynamics CRM database in SQL Query Analyzer or in SQL Server Management Studio, as a Microsoft Dynamics CRM Administrator.

  SELECT OwnerIdName, count(*) as 'RecordCount'
  FROM FilteredContact
  GROUP BY OwnerIdName
  ORDER BY 'RecordCount'
  

Prerequisites

No prerequisites are required to apply this hotfix.

Restart requirement

If you are prompted, restart the computer after you install the hotfix.

Removal information

To remove this hotfix from a computer that is running Microsoft Windows Server 2003, Microsoft Windows XP, or Microsoft Windows 2000, use Add or Remove Programs in Control Panel.

System administrators can use the Spuninst.exe tool to remove this hotfix from a computer that is running Microsoft Windows Server 2003, Microsoft Windows XP, or Microsoft Windows 2000.

The Spuninst.exe tool is located in the %Windir%\$NTUninstallKB921235$\Spuninst folder. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For information about performance tuning for CRM 3.0, click the following link to see the "Optimizing the Performance of Microsoft Dynamics CRM 3.0 White Paper" white paper: For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base: