Update Rollup 2 for Microsoft Dynamics CRM 4.0 - More Info

Matt Brown wrote this

---

On 2/8/2008, the CRM Sustained Engineering team released a new version of the Update Rollup 2 packages. The new version of Update Rollup 2 addresses some of the issues that have been noted in the comments for this blog entry.

Including:

• Strings in the localized product showing up as garbage or in English.

• Customized web.config causing issues after Update Rollup 2 is installed.

Customers do not need to uninstall the original Update Rollup 2 packages. The new packages will install over the top. If a customer has not been affected by the issues in the original Update Rollup 2 package they do not need to update to the new version. Customers can install Client, Server, Router Update Rollup 2 in any order.

The steps for the AutoUpdate have caused some confusion. There is a different PatchId and LinkId for every language of the product. You will find a table at the bottom of this post that has the PatchId and LinkId for each Language. Note: The new packages changed the PatchId so it will need to be updated, as the previous PatchId is no longer valid.

***

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup 2 on Thursday, January 15, 2009.

Below is the link to the release and related information about the Rollup. Please see the Knowledge Base (KB) article for more details about the Update Rollup 2 content and instructions..

• Microsoft Download Center: http://www.microsoft.com/downloads/details.aspx?familyid=aa671769-61e9-45c4-919f-c88199aa4241&displaylang=en&tm
• Microsoft Knowledge Base Article: http://support.microsoft.com/kb/959419

Install Details about Update Rollup 2

• Update Rollup 1 is not a prerequisite for installing Update Rollup 2
• The Update Rollup 2 client can be deployed before the server is upgraded to Update Rollup 2
• Update Rollup 2 can be uninstalled
• Unlike Update Rollup 1, Update Rollup 2 is packaged so that each language is packaged individually. As a result, the download size of the packages for Update Rollup 2 is significantly smaller. For example, the CRM Server package size is reduced from about 171 MB in Update Rollup 1 to about 9 MB in Update Rollup 2. The Outlook Client package size is reduced from about 78 MB in Update Rollup 1 to about 4 MB in Update Rollup 2

How to avoid a required reboot when installing a patch for the CRM Outlook Client

• Before starting the update process, go to Options from the CRM menu. On the “General” tab, uncheck the bottom checkbox that says “Always run the…Host process” and then click “Ok” button.
• When manually checking for updates, go ahead and close Outlook by choosing Exit from Outlook’s File menu. This will close Outlook along with the CRM add-in and the Hoster process.
• Now check for updates by selecting All Programs from the Start menu. Then select Microsoft Dynamics CRM 4.0 and choose Update.
• Restart Outlook after the patch is installed.

Note: If the user doesn’t want to make the permanent change of always having the Hoster process exit when Outlook exits, they can close the Hoster process manually after Outlook has been closed by right clicking on the Dynamics icon in the Notification Area of the Task Bar.

Making Update Rollup 2 available to your clients via AutoUpdate:

You can find more information about AutoUpdate in Eric Newell’s blog entry at http://blogs.msdn.com/crm/archive/2008/05/08/crm-client-autoupdate.aspx and the Microsoft Dynamics CRM 4.0 Operating and Maintaining Guide, part of the Microsoft Dynamics CRM 4.0 Implementation Guide.

If you have a direct internet connection from your client machines, you can avoid some of the configuration steps and use the LinkId directly. Below are the necessary steps to configure the AutoUpdate for Update Rollup 2.

Note: These are steps 5, 6 and 7 of Eric’s blog.

*** 2/9/2008 Update ***

The steps below are for the English version of the product. The PatchId and LinkId values will be different for every localized version of CRM 4.0. There is a table at the bottom of this post that lists the correct PatchId and LinkId for each language.

***

1. Create the configuration XML file and save it.

<ClientPatches>

   <Create>

      <!--- *** UR2 PATCH -->

        <ClientPatchInfo>

<!--- *** The PatchId is different for every Language. Please see the table at the end for correct Link ID to use -->

          <PatchId>{321EFF1F-4402-4554-B037-B1492FFA67E9}</PatchId>

          <Title>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)</Title>

          <Description>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)</Description>

          <!--- *** This will make it Mandatory -->

          <IsMandatory>true</IsMandatory>

          <IsEnabled>true</IsEnabled>

          <ClientType>OutlookLaptop, OutlookDesktop</ClientType>

<!--- *** The LinkId is different for every Language. Please see the table at the end for correct Link ID to use -->

          <LinkId>140023</LinkId>

      </ClientPatchInfo>

   </Create>

</ClientPatches>

2. From the command prompt, go to the directory where the ClientPatchConfigurator.exe is located ([ServerInstallDir]\Tools and type microsoft.crm.tools.clientpatchconfigurator.exe [configfile].xml

3. Once the patch has been uploaded, launch the Outlook client

The dialog should now appear saying that “Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)” is available. If the <IsMandatory> is set to false, the client will only see the update if the user selects “Check for Updates” via the CRM Menu in the Outlook client.

*** 2/9/2008 Update ***

Arabic

LinkID: 140023&clcid=0x401

PatchID: {5976FEF7-2939-4597-B849-378B5010E7EA}

Chinese (Simplified)

LinkID: 140023&clcid=0x804

PatchID: {1F9AD22B-7E77-4704-94F2-ED4C9A9204FE}

Chinese (Hong Kong)

LinkID: 140023&clcid=0xc04

PatchID: {8E4BD4EB-6024-4F50-9F8B-ECB2D2962268}

Chinese (Traditional)

LinkID: 140023&clcid=0x404

PatchID: {544B5D8F-1561-4079-9D1B-871958FD5784}

Czech

LinkID: 140023&clcid=0x405

PatchID: {7703B3AB-5040-43A0-9E51-C679C1D901DB}

Danish

LinkID: 140023&clcid=0x406

PatchID: {9CE94585-65D2-4032-8E9C-2BEC113DBBC5}

Dutch

LinkID: 140023&clcid=0x413

PatchID: {B0DABBC4-7E03-4BF4-85CB-7F6556D7A57D}

English

LinkID: 140023&clcid=0x409 (or just 140023)

PatchID: {321EFF1F-4402-4554-B037-B1492FFA67E9}

Finish

LinkID: 140023&clcid=0x40b

PatchID: {318C90C1-FE54-4383-BF1F-B9C20BBD2E58}

French

LinkID: 140023&clcid=0x40c

PatchID: {AA73B91A-CDAD-43CB-AD46-725AC839DAA4}

German

LinkID: 140023&clcid=0x407

PatchID: {C9344B1E-E32A-4C78-ADAB-332C3F934A95}

Greek

LinkID: 140023&clcid=0x408

PatchID: {460B3EBE-525F-44C2-8F59-D71DAA1E0136}

Hebrew

LinkID: 140023&clcid=0x40d

PatchID: {9C5A6F83-2C6E-4B32-91D8-6ADB7E279184}

Hungarian

LinkID: 140023&clcid=0x40e

PatchID: {CB0F2A7F-11F1-4AEE-AF5F-78A485DEB43A}

Italian

LinkID: 140023&clcid=0x410

PatchID: {1BF9AC1B-C4B8-4555-AABE-595C653C1A0D}

Japanese

LinkID: 140023&clcid=0x411

PatchID: {FF755164-2686-4B81-860A-13B66A62A10A}

Korean

LinkID: 140023&clcid=0x412

PatchID: {6FD317AE-D2E1-4307-9E4F-F324B6615632}

Norwegian

LinkID: 140023&clcid=0x414

PatchID: {821536C9-5E42-4B95-879B-DEAD921C8510}

Polish

LinkID: 140023&clcid=0x415

PatchID: {D5D73DEA-FBC7-4B73-BDAF-3C54CD735DB0}

Portuguese (Brazil)

LinkID: 140023&clcid=0x416

PatchID: {98557D6F-49E8-4280-9435-9FE0CD6979F5}

Portuguese (Portugal)

LinkID: 140023&clcid=0x816

PatchID: {63F4323D-5341-4EC2-A7E6-6EB6A12E5EC5}

Russian

LinkID: 140023&clcid=0x419

PatchID: {D6A8BD6F-E3AF-42DB-95C1-4538520C227D}

Spanish

LinkID: 140023&clcid=0xc0a

PatchID: {52B9A75C-22E0-4556-B978-9CF5CAB5353F}

Swedish

LinkID: 140023&clcid=0x41d

PatchID: {75EF6272-B9A7-4C78-87B4-1730B019C431}

Turkish

LinkID: 140023&clcid=0x41f

PatchID: {6F3E936F-F745-44CE-8412-EA5CDE05748D}

Keep your comments, experiences, and observations coming. We're listening.

Matt Brown

Can't publish a workflow after installing a Rollup Update? Read on...

Posted by Mike Snyder on January 22, 2009

---

If you have installed the Microsoft CRM Update Rollup 1 or Update Rollup 2, you might experience an error where you cannot publish a workflow rule anymore. According to Microsoft this might happen if you modified the web.config file in your deployment:

If you have modified the Microsoft CRM website web.config file, then you need to manually open the Microsoft CRM Web site web.config file in an editor like Notepad and add the following section to it in order to continue being able to publish workflows:

In the section <authorizedTypes>

…multiple lines here

<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Globalization" TypeName="CultureInfo" Authorized="True"/>

</authorizedTypes>

Microsoft said they are looking at modifying the install notes to include this warning and/or revising the Update Rollup 2 installation files.

Posted by Mike Snyder on January 22, 2009

Cannot change Business Unit.

Wow, that was rough! I have a client that had a very weird error. Every time you tried to change someone’s business unit you received the all-so-helpful error page that told you nothing. Looking into the event logs held no errors and the trace logs were difficult to ponder as well. That led to a call to MS for help. In the end it appeared to be a timeout issue while it was trying to change the business units.

Within the logs they found the following error:

Crm Exception: Message: , ErrorCode: -2147204784, InnerException: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

If you read the article http://support.microsoft.com/kb/918609 it appears to be around customizations and uploading them, but it worked in this instance as well.

To resolve this problem, use one of the following methods.

Method 1: Add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values

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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

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.

Method 2: Modify a parameter in two different Web.config files

1. Click Start, click All Programs, click Administrative Tools, and then click Internet Information Services (IIS) Manager.



2. Expand the server name, and then expand Web Sites.



3. Right-click the Microsoft CRM v3.0 Web site or the Microsoft CRM v4.0 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"/>





6. Increase the "8192" value to a value that is large enough to handle the Customization.xml file.



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



8. In the directory in which you opened the Web.config file, open the MSCRMServices folder.



9. Right-click the Web.config file, click Open With, and then click Notepad.



10. In Notepad, locate the following line.





• <httpRuntime maxRequestLength="8192"/>





11. Change the "8192" value to the value that you specified in step 6.



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

The OLEDBTimeout value

The unit of the OLEDBTimeout value is seconds. By default, the OLEDBTimeout value is 30 seconds. The OLEDBTimeout value controls the SQL time-out value that is used for a single SQL query. The increased OLEDBTimeout value is useful when the SQL server is overloaded. Additionally, the query takes a longer time to process.

The ExtendedTimeout value

The unit of the ExtendedTimeout value is milliseconds. By default, the ExtendedTimeout value is 1000000 milliseconds. The ExtendedTimeout value controls the ASP.NET time-out value that is used for import requests. The time-out value must be larger than the time for finishing the whole import process. The increased ExtendedTimeout value is useful when the import process takes a long time.

Automatic Update Strikes Again. (KB953838)

Murphy and Microsoft must be bed partners. Imagine going to your biggest CRM implementation to provide your training for roll out. As you bring up the system and start training you get a file download prompt for blank.aspx. Interesting, it could just be the machine. However, 80% of all the computers are getting it. Every time you move another entity, you get that wonderful prompt. It is annoying the first 10 times, but words cannot describe the feeling you have after two days of training with it.
After dome digging it turns out Microsoft put out an IE Update on 8/12 that dropped the mapping on client machines to aspx pages. Nice! And as many people who work with web pages can tell you “about:blank” is used as a white space filler on i-frames. Nice testing Microsoft! Well, enough of my complaining. There is an update that is automatically applied (if you have auto updates turned on) called KB953838. If you have IE 7 installed, you may not have the issue. If you have this issue you have a couple of options.

1. Upgrade to IE7.
2. Uninstall KB953838

a. When you get the prompt, Download it to your desktop.
b. Right click and open with.
c. Select Internet Explorer and check off always open with this program

CRM4 Outlook Client – Issues and Fixes

Smiti Shah Published Wednesday, August 06, 2008 10:50 AM by crmblog

---

This must-have fix is likely the most common perf/stability issue out there, especially on Outlook 2007. This fix resolves the issue. A current workaround exists by turning off the To Do bar.
http://support.microsoft.com/kb/952724

2. With E-mail Auto Promotion Enabled, Outlook may not close cleanly/properly.

This fix addresses a memory allocation issue that can occur somewhat unpredictably. If your users are using e-mail auto promotion, I encourage you to deploy this hotfix.

http://support.microsoft.com/kb/948121

3. Contacts with birthdays earlier than 1/1/1970 causes Outlook to crash

This was caused by an API change by one of our dependencies.

http://support.microsoft.com/kb/948045

4. Items in Shared Calendars will report Sync Issues

We do not support Shared Calendars in CRM 4.0, we encountered a couple of cases where some code was getting executed against a shared calendar and causing problems.

http://support.microsoft.com/kb/949086

5. Cannot Promote an E-mail where the name of the attached file contains a ‘&’ symbol.

If the attachment to an e-mail contains the ‘&’ symbol, it will fail to track in CRM.

http://support.microsoft.com/kb/949719

6. Selecting Dismiss on Outlook Calendar reminder for Service Activity causes record to change Status Reason back to default value for that record.

Selecting Dismiss on Outlook Calendar reminder for Service Activity causes record to change Status Reason back to default value for that record

http://support.microsoft.com/kb/950475  (not yet published)

7. OWA Sent Emails Get Stuck in Outlook Draft Folder When Outlook Is Open And CRMADDIN is Enabled

When you have both Outlook and OWA open, and you have the Microsoft Dynamics CRM client for Microsoft Office Outlook installed, and you send an email form OWA, the email will be stopped in the Draft folder instead of being sent

http://support.microsoft.com/kb/950088

Smiti Shah

CRM Outlook Client update

An optional software update is now available for Microsoft Dynamics CRM Online for Microsoft Office Outlook. This optional software download includes an update that can increase the performance and reliability for everyday system use.

From Microsoft Office Outlook, users can automatically download this update by navigating to the CRM menu found at the top of their Microsoft Office Outlook screen (see below). Within the CRM menu, there is an option to check for software updates – which will download this update so that installation can begin. The user will then be presented with a set of instructions on how to download and apply this update to their client configuration.

Additional information about the client updates can be found online at http://support.microsoft.com/kb/954491. Refer to Knowledge Base article KB 954491 for a summary of items addressed in this update.

If you experience problems downloading or installing this update, please contact Microsoft Dynamics CRM Support. Support contact information can be found at http://crm.dynamics.com/crm_training_and_support/index.html.

Reporting Server will not work after upgrade.

This article Posted by Matt Wittemann seems to cover an issue that we are having.

---

The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
Posted by Matt Wittemann

In a recent upgrade environment, now running CRM 4.0, I found that reports stopped working from CRM. What was strange was that reports could still be run from the SQL Reporting Services website, just not from CRM - not even on the CRM server, so I knew it wasn't just a Kerberos authentication problem (and SQL was on the same box with CRM anyway!). After checking and re-checking all the settings in the SSRS website, the registry hive for CRM, and everywhere else I could think of, I opened a support ticket with Microsoft.

But whenever I have to ask for outside help, I feel like I need to re-double my efforts in locating the problem and fixing it myself. (I should probably just open tickets all the time!). After much searching, I found an obscure reference on a SQL forum about this error (The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.) and a mention of an update for SQL 2005. I logged onto the SQL server and ran Windows Update, and there it was - KB948109. Downloading this update and installing it fixed the problem. After the update, there was an error in the event log indicating that the .NET Framework 2.0 could not recompile, but upon running a report and waiting a long time for the app to compile, reports started working again throughout the network. Yay!

Here's a link to the update for more information:
http://support.microsoft.com/kb/948109

HOTFIX ALERT: You cannot view any e-mail messages in the folders after you install the Microsoft Dynamics CRM 4.0 On-Premise client for Outlook

This one has caused me some problems with our CRM implementation as well as a few clients. The end user will call you and tell you that thier Outlook is stuck and the moving bar never stops.

---

SYMPTOMS
After you install the Microsoft Dynamics CRM 4.0 On-Premise client for Microsoft Office Outlook, you can select different folders in Outlook. However, you cannot view any e-mail messages in the folders. In the area where the e-mail messages should be displayed, Outlook displays "loading."
RESOLUTION
click here to open the KB Article
Click here to request the Hotfix

Email Router Hotfix

David Fronk wrote on Tuesday, July 01, 2008

---

received word from Microsoft that they have an update available to fix an issue that occurs with the email router. For whatever reason the email router will poll for an hour and then lock for an hour. If it unlocks itself after that second hour it will work for another hour and then lock itself again. The hour comes from the default polling time that is set up in the email router config file. So, if you were to modify that polling time then you would extend the life of your email router from locking up but also extend the amount of time to get the email router back up once it is locked.

I used a work around to get by until this hotfix became available by restarting the email router service each hour via a bat script.

However the hotfix you want to check out is KB article 952019. You will need to contact Microsoft via PartnerSource or CustomerSource in order to obtain the hotfix, but you will not be charged for the ticket if you are requesting the hotfix.

Hope this comes in handy for someone else as well.

Follow-up Fall-down

We have noticed that sometimes the follow-up wizard will not allow you to assign the activity to someone else. You must open the activity and change the owner. I have found a KB Atricle on this:
"A new follow-up activity is still owned by the original user after you change the user in Microsoft Dynamics CRM 4.0" Article ID : 948008

SYMPTOMS
Consider the following scenario in Microsoft Dynamics CRM 4.0. On an account form, you try to create a new follow-up activity in the Form Assistant. In the Form Assistant, you change the user in the Assign to field to another user. Then, you click Save and Open. In this scenario, the new follow-up activity is still owned by the original user who was in the Assign to field.

This problem also occurs if you change any field in the Form Assistant that is mapped between the source entity and the selected activity entity. For example, this problem also occurs if you change the Phone Number field in the follow-up activity. The Phone Number field is mapped to the Main Phone field on the account form. In this case, the value that exists on the source entity overwrites the value that you specify in the follow-up activity.

Where to find CRM 4.0 Hotfixes

Microsoft has a standard KB page listing all of the available hotfixes for MSCRM 4.0. It can be found at http://support.microsoft.com/kb/949256/en-us. You may want to book mark this page and come back once a month to see if there are any that may apply to your implementation.

Where to find CRM 4.0 Hotfixes

Microsoft has a standard KB page listing all of the available hotfixes for MSCRM 4.0. It can be found at http://support.microsoft.com/kb/949256/en-us. You may want to book mark this page and come back once a month to see if there are any that may apply to your implementation.