An update for the 2007 daylight saving time changes is available for Microsoft Dynamics CRM 3.0 and for the Microsoft Dynamics CRM 3.0 client for Outlook

In 2007, the start dates and the end dates for daylight saving time (DST) in the United States will change to comply with the Energy Policy Act of 2005. The dates will change as follows. After daylight saving time goes into effect on March 11, 2007, you may experience the following problems in Microsoft Dynamics CRM:

• When you view appointments or tasks in the Microsoft Dynamics CRM Web client or in the Microsoft Dynamics CRM client for Microsoft Office Outlook, the appointments and the tasks may be scheduled one hour ahead of the actual event time or one hour behind the actual event time.
• Some activities and some resources in the service calendar in Microsoft Dynamics CRM may be scheduled one hour ahead of the actual event time or one hour behind the actual event time.

The DST changes affect many time zones that are stored in Microsoft Dynamics CRM. These time zones may affect all Microsoft Dynamics CRM users. This includes users who are outside the United States. For a list of the affected time zones, see the “More information” section.

Update information

A supported update is now available from Microsoft for computers that are running the following:

• Microsoft Dynamics CRM 3.0
• Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers
• The Chinese version and the Japanese version of Microsoft Dynamics CRM 3.0
• Microsoft Dynamics CRM 3.0 client for Outlook

Note The update for the Microsoft Dynamics CRM 3.0 client for Outlook includes the Microsoft Dynamics CRM 3.0 client for Microsoft Office Outlook Compatibility Release. This release makes the Microsoft Dynamics CRM 3.0 client for Outlook compatible with Windows Vista and with 2007 Microsoft Office programs.

The following files are available for download from the Microsoft Download Center.

Microsoft Dynamics CRM 3.0

• Download this file if you are using the Microsoft Dynamics CRM 3.0 client for Outlook or if you are using the Microsoft Dynamics CRM 3.0 client for Outlook Compatibility Release.
  
  
  Collapse this imageExpand this image

  
  Download the CRM3.0-KB925874-Client-<ENU>.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A7319E6-5B86-4E7A-9BE1-763F2072BE21&displaylang=en)
• Download this file if you are using the Microsoft Dynamics CRM 3.0 server software.
  
  
  Collapse this imageExpand this image

  
  Download the CRM3.0-KB925874-Server-<ENU>.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A7319E6-5B86-4E7A-9BE1-763F2072BE21&displaylang=en)

Microsoft Dynamics CRM 3.0 Update Rollup 2
The update for the 2007 daylight saving time changes is included in Microsoft Dynamics CRM 3.0 Update Rollup 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers

• Download this file if you are using the Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers server.
  
  
  Collapse this imageExpand this image

  
  Download the CRM3.0PE-KB925874-Server-<ENU>.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A7319E6-5B86-4E7A-9BE1-763F2072BE21&displaylang=en)
• Download this file if you are using the Microsoft Dynamics CRM 3.0 client for Outlook together with Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers.
  
  
  Collapse this imageExpand this image

  
  Download the CRM3.0PE-KB925874-Client-<ENU>.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A7319E6-5B86-4E7A-9BE1-763F2072BE21&displaylang=en)

The Chinese version and the Japanese version of Microsoft Dynamics CRM 3.0

• Download this file if you are using the Chinese version and the Japanese version of Microsoft Dynamics CRM 3.0:
  http://www.microsoft.com/downloads/details.aspx?displaylang=ja&FamilyID=8a7319e6-5b86-4e7a-9be1-763f2072be21 (http://www.microsoft.com/downloads/details.aspx?displaylang=ja&FamilyID=8a7319e6-5b86-4e7a-9be1-763f2072be21)

Release Date: March 2, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Note In the file names, the <ENU> placeholder in the file names is a placeholder for the abbreviation of the language version that you install.

What the update includes

This update includes the following:

• The new 2007 DST start dates and end dates for several time-zone definitions in Microsoft Dynamics CRM. For example, all United States time zones will be changed to reflect the new DST start dates and the new DST end dates.
• Several new stored procedures and tables that are used by the Update Time Zone Wizard. This wizard uses these stored procedures and tables to determine the Microsoft Dynamics CRM records that may have to be updated to reflect the DST changes.

File information

The English version of this update 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 client for Outlook

Microsoft Dynamics CRM client for Microsoft Office Outlook Compatibility Release

Microsoft Dynamics CRM 3.0 server

Installation information for the update

Install this update on computers that are running the Microsoft Dynamics CRM 3.0 server software, the Microsoft CRM 3.0 client for Outlook, or Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers.

Synchronize offline data from computers that are running the Microsoft Dynamics CRM laptop client for Outlook

We recommend that you synchronize all the offline data from all the computers that are running the Microsoft Dynamics CRM laptop client for Outlook to the Microsoft CRM server before you install this update. The list of candidates that are eligible for the DST changes is created during the installation of this update. This list cannot be re-created. The candidate table is used by the Update Time Zones Wizard. This wizard lets the administrator make data corrections that reflect the DST changes. The wizard updates the candidate table with information about the records that have been updated for the DST changes.

If you do not synchronize the offline data from all the computers that are running the Microsoft Dynamics CRM laptop client for Outlook before you install the Microsoft CRM server-side hotfix, the following sequence of events causes data to appear incorrectly in Microsoft CRM.

• You install the Microsoft CRM server-side update that creates the list of candidates.
• A computer that is running the Microsoft Dynamics CRM laptop client for Outlook synchronizes data to the Microsoft CRM server.
• The data that was synchronized is not added to the candidate table. Therefore, that data may appear incorrectly in Microsoft Dynamics CRM.

Note The Microsoft CRM client for Outlook includes both the Microsoft CRM laptop client for Outlook and the Microsoft Dynamics CRM desktop client for Outlook.

Install the client-side update on computers that are running the Microsoft CRM client for Outlook

We recommend that you install the client-side update on computers that are running the Microsoft CRM laptop client for Outlook and on computers that are running the Microsoft Dynamics CRM desktop client for Outlook. The DST issues in the Microsoft Dynamics CRM desktop client for Outlook are resolved in the Microsoft Dynamics CRM server-side update. However, this update also includes other hotfix file information. The Microsoft Dynamics CRM client-side update must be installed on computers that are running the Microsoft Dynamics CRM desktop client for Outlook to maintain file consistency. This file consistency is required because of other hotfix dependencies.

Install the server-side update on all the Microsoft Dynamics CRM servers

If you have multiple Microsoft Dynamics CRM servers, you must install the server-side update on all the Microsoft Dynamics CRM servers. However, do not install this update on each Microsoft Dynamics CRM server at the same time. Install this update on each Microsoft Dynamics CRM server separately to prevent deadlocks in Microsoft SQL Server.

Install the server-side update in new installations of Microsoft Dynamics CRM 3.0

If you install Microsoft Dynamics CRM after the new start date and the new end date for DST go into effect, you must still apply this update. This update adds the new time zone definitions. You should install this update before users enter any data in Microsoft Dynamics CRM.

Recommended installation order

We recommend a specific installation order when you install DST updates for other products that are used by Microsoft Dynamics CRM. We also recommend a specific installation order when you install the server-side update and the client-side update. We also recommend that you run the Update Time Zones Wizard at a specific point in the installation process. For more information, see the “Recommended sequence of update actions for the Microsoft CRM system” section of the Microsoft Dynamics CRM 3.0 Remediation Instructions for 2007 Daylight Saving Time Changes document. This document is available for download from the Microsoft Download Center.

The following file is available for download from the Microsoft Download Center:

Download the CRM_DST_Remediation_Details_Rev1.1.exe package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A7319E6-5B86-4E7A-9BE1-763F2072BE21&amp;amp;displaylang=en)

Release Date: March 2, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Required user rights

You must be a member of the Microsoft Dynamics CRM PrivUserGroup in Active Directory to install this update.

If many records are affected by the DST changes

You must increase the OLEDB time-out registry value if many records are affected by the DST changes. You must do this to prevent a possible Microsoft SQL Server time-out when you install this update.

Note If this registry subkey already exists, note the current value. After you complete the DST changes for Microsoft Dynamics CRM, set the value of this registry subkey back to the original value. Or, delete the registry subkey if it did not exist previously. The default OLEDB time-out value is 30 seconds. To increase the OLEDB time-out registry value, follow these steps:

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.
4. Rename the DWORD value as "OLEDBTimeout."
5. Right-click the DWORD value, and then click Modify.
6. Under Base, click Decimal. Then, type 3600 in the Value data box, and then click OK.
   
   Note A decimal value of 3,600 equals 60 minutes.

Prerequisites

You must have Microsoft Dynamics CRM 3.0 installed to apply this hotfix.

Restart requirement

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

Removal information

You cannot remove this hotfix.

Known issues

Issue 1

If you have installed a third-party program that registers the Microsoft.Crm.MetadataService.dll file to the global cache assembly (GCA), you may experience a problem saving or updating an entity or attribute in Microsoft Dynamics CRM after you install this update.

For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:

Issue 2

Important This section, method, or 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, click the following article number to view the article in the Microsoft Knowledge Base:
When you install update 925874, you receive the following error message:You may receive this error message for one of the following reasons:

• A registry key is missing. This registry key is required by the TimeZoneUpdatePatch.exe file. The TimeZoneUpdatePatch.exe file runs as a subprocess of the update 925874 installation. See Resolution 1 in this section.
• An unknown registry key is queried by the TimeZoneUpdatePatch.exe file. The TimeZoneUpdatePatch.exe file runs as a subprocess of the update 925874 installation. See Resolution 2 in this section.

Note Time zones are stored in the registry in the following location:

Resolution 1

1. Copy the time zone registry key values to a text file. To do this, type the following command at the command prompt:
   REG QUERY "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Time Zones" /s | findstr /I "index software Dlt Std Display TZI" >TimeZoneRegInfo.txt
2. Use the same command on another Microsoft Dynamics CRM server on which update 925874 was successfully installed.
3. Download the Windiff.exe file. To do this, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en)
4. Run the Windiff.exe file to compare the TimeZoneRegInfo.txt files. Compare the TimeZoneRegInfo.txt files to determine which time zones are missing an index entry for a specific time zone. Time zones that are missing an index entry have a value of DWORD.
5. Update the registry value that is missing an index entry for a specific time zone. To open the registry, click Start, click Run, type regedit, and then click OK.

Resolution 2

1. Copy the time zone registry key values to a text file. To do this, type the following command at the command prompt:
   REG QUERY "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Time Zones" /s | findstr /I "index software Dlt Std Display TZI" >TimeZoneRegInfo.txt
2. Use the same command on another Microsoft Dynamics CRM server on which update 925874 was successfully installed.
3. Download the Windiff.exe file. To do this, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en)
4. Run the Windiff.exe file to compare the TimeZoneRegInfo.txt files.
5. In the TimeZoneRegInfo.txt file for the Microsoft Dynamics CRM server on which update 925874 was successfully installed, look for time zones that are unknown. For example, the following registry key prevents update 925874 from being installed successfully:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Jerusalem Standard Time
6. Export the unknown time zone registry key to create a backup. To do this, select the registry key, click File, and then click Export. Save the registry key as an .reg file.
7. Start the installation of update 925874 again.
8. After update 925874 is successfully installed, reenter the unknown time zone registry key in the registry. To do this, double-click the file that you created in step 6.

Issue 3

When you install update 925874, you receive the following error message: Additionally, the following error message is logged in the KB925874_err.log file:
Notes

• The KB925874_err.log file is located in the <drive>:\windows directory on the Microsoft Dynamics CRM server.
• Update 925874 includes other Microsoft Dynamics CRM hotfixes. This issue is typically because of many contacts that must be updated by hotfix KB923057.

To resolve this issue, add or increase the HotFixDBTimeout RegDWORD registry value. To do this, follow these steps.

Important This section, method, or 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, click the following article number to view the article in the Microsoft Knowledge Base:

1. On the Microsoft Dynamics CRM server, click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM
3. If the HotfixDBTimeout key does not exist, follow these steps:
   1. On the Edit menu, point to New, and then click DWORD Value.
   2. Type HotfixDBTimeout, and then press ENTER.
   3. Right-click HotfixDBTimeout, and then click Modify.
   4. Under Base, click Decimal, type 65000 in the Value data box, and then click OK.
      
      Note Microsoft Dynamics CRM hotfix installations only recognize HotfixDBTimeout registry values between 0 and 65535. These values represent the number of seconds of a time-out. You can leave the default value after you install the hotfix.
   5. On the File menu, click Exit.

Note You may have to add or modify the OLEDBTimeout registry value. If this registry subkey already exists, note the current value. After you complete the DST changes for Microsoft Dynamics CRM, revert the value of this registry subkey to the previous value. Or, delete the registry subkey if it did not previously exist. The default OLEDB time-out value is 30 seconds.

To increase the OLEDB time-out registry value, follow these steps:

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.
4. Rename the DWORD value as "OLEDBTimeout."
5. Right-click the DWORD value, and then click Modify.
6. Under Base, click Decimal. Then, type 65000 in the Value data box, and then click OK.
7. On the File menu, click Exit to exit Registry Editor.
8. Install KB925874 again on the Microsoft CRM Server. After it has successfully installed, revert the OLEDBTimeout registry value back to the previous value. Or, delete the registry subkey if it did not exist previously.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Stored procedures

The following Microsoft SQL Server stored procedures are installed in the Organization_Name_MSCRM database when you install this update:

• p_TimeZoneUserCandidates
• p_TimeZoneNonUserCandidates
• p_TimeZoneSecureUserCandidates
• p_TimeZoneGenerateCandidates
• p_TimeZoneGetTimeZonesInUse
• p_TimeZoneGetEntitiesByTimeZone
• p_TimeZoneGetEntitiesAllTimeZone
• p_TimeZoneCandidateSummary
• p_UpdateCalendarTimeZone
• p_PopulateTimeZoneCodeLegacy
• p_UpdateEntityTimeZoneCode
• p_UpdateEntityTimeZone

The following Microsoft SQL Server tables are installed in the Organization_Name_MSCRM database when you install this hotfix:

• TimeZoneAdjustmentWindows
• TimeZoneEntityAttribute
• TimeZoneUserSetting
• TimeZoneEntityCandidate
• UpdateEntityTimeZoneInput

Time zones that are affected by the DST changes for Microsoft Dynamics CRM 3.0

The following is a list of time zones that are affected by the DST changes for Microsoft Dynamics CRM 3.0. For more information about the Microsoft Dynamics CRM 3.0 Update Time Zones Wizard, click the following article number to view the article in the Microsoft Knowledge Base: For more information about Microsoft CRM and DST, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft Dynamics CRM 3.0 Update Rollup 1

The installation of this update is not dependent on the installation of Microsoft Dynamics CRM 3.0 Update Rollup 1. This update includes some of the fixes that are in Update Rollup 1. But this update does not include all the fixes that are in Update Rollup 1. You can install this update even if you have not installed Update Rollup 1. For more information about Update Rollup 1, click the following article number to view the article in the Microsoft Knowledge Base:

Additional problems that this update resolves

Microsoft Dynamics CRM 3.0

This update for Microsoft Dynamics CRM 3.0 also resolves the problems that are described in the following Microsoft Knowledge Base articles.

Japanese or Chinese versions of Microsoft Dynamics CRM 3.0

This update for the Japanese or Chinese versions of Microsoft Dynamics CRM 3.0 also resolves the problems that are described in the following Microsoft Knowledge Base articles.

Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers

This update for Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers resolves the problems that are described in the following Microsoft Knowledge Base articles.

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: