Showing posts with label Rollups. Show all posts
Showing posts with label Rollups. Show all posts

Thursday, February 12, 2009

CRM Update Rollup 2 Musings

Posted by Jim Steger on February 11, 2009


As most of you know by now, Microsoft CRM Support has released Update Rollup 2 for Dynamics CRM 4.0. Here are some quick findings that we have discovered that I hope can be useful for some of you.

Exporting and importing customizations
Update Rollup 2 made some schema changes to the customizations and the rollup documentation provides a general warning about only export/importing customizations from system with the same rollup installed. This approach is painful for our development environment and for ISVs, as it is not easy to guarantee that all customers will be on the same rollup. What I learned from the product and support teams (and confirmed with some quick testing) is the schema changes to the customization file in UR2 is confined to just Templates and Outlook Synchronization areas.

Therefore, if you need to import/export between different rollup deployments, you should be ok provided you excluded those two customizations from your file.

I am hoping that CRM Support will be more specific with the customization schema changes on future rollup releases, or better yet, allow them to be backwards compatible between rollups.
Manually configured steps
There are a number of hotfixes that require manual configuration. I didn't see these documented too well (although I could have missed it). Anyway, here is a list that we have discovered. Note that this could just be a partial list.

  • 955452 (http://support.microsoft.com/kb/955452/ ) Line feeds are not used when you send an e-mail message that uses an e-mail template to render data that has line feeds in Microsoft Dynamics CRM 4.0
  • 955745 (http://support.microsoft.com/kb/955745/ ) Error message when you try to configure the Microsoft Dynamics CRM 4.0 client for Outlook: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms"
  • 956527 (http://support.microsoft.com/kb/956527/ ) The Microsoft Dynamics CRM client for Outlook consumes three times as much memory in version 4.0 as in version 3.0
  • 959248 (http://support.microsoft.com/kb/959248/ ) Microsoft Dynamics CRM 4.0 slows to unacceptable levels when you process e-mail messages by using the Microsoft Dynamics CRM E-mail Router
  • 957871 (http://support.microsoft.com/kb/957871/ ) The Workflow Expansion Task records cause the AsyncOperationBase table in the MSCRM database to grow too large in Microsoft Dynamics CRM 4.0

Miscellaneous Notes/FAQ

  • When you install any rollup, it will affect the entire deployment. For those of you that leverage multi-tenancy (as we do in our client development environment), you need to be aware of this and plan the release accordingly. Pay special care to the customizations changes and quickly review each hotfix within the rollup to ensure there won't be compatibility issues with your custom code. Naturally if your custom code follows the supported SDK, you should be ok from rollup to rollup.
  • Update Rollup 2 may screw up your existing CRM web.config. I recommend you make a backup of the CRM web.config file prior to running the rollup. Here are two errors we have seen:
    • Publishing workflow rules fails. This error is now documented in the release notes. You need to update the CRM web.config files and add the following line to the <authorizedTypes> section:
      <authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Globalization" TypeName="CultureInfo" Authorized="True"/>
    • We had our IFD settings wiped out from the CRM web.config. To correct, we used the IFD tool to reset the values.
  • Microsoft recommends that you keep the update rollups between the Outlook client and the CRM server in sync. I am not sure this is always a hard requirement, as we have some internal Outlook clients on the latest rollup, prior to updating our server. This is something you can test, if rolling out to your Outlook clients users is not always easy to do.
  • Each rollup *should* be cumulative. This means that you can install UR2 on a system that hasn't been patched with UR1.

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..

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

Friday, January 23, 2009

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

Wednesday, January 21, 2009

Update Rollup 2 for Microsoft Dynamics CRM 4.0

Smiti Shah Published Tuesday, January 20, 2009 8:11 AM


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..

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 Update Rollup 2 for 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.
  • Check for Updates and start the install.  While that is running, choose Exit from Outlook’s File menu to close down Outlook.  This will avoid any “File in use” errors.  If you do get the error, you were probably a little slow in shutting down Outlook.  You can click-on “Retry” once Outlook and the CRM hoster process have completed their shutdowns.
  • Restart Outlook after the patch is installed.

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 1.

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

1. Create the configuration XML file and save it.

<ClientPatches>

   <Create>

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

        <ClientPatchInfo>

          <PatchId>{9EA7FDEB-9D7E-4278-8CD1-94ACEFA40D3F }</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>

          <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.

Smiti Shah

Friday, January 16, 2009

Update Rollup 2 for Microsoft Dynamics CRM 4.0 is available

I'm not sure if I'm happy or worried that we have another Rollup out so soon after Rollup 1. However, it is here and you can review the fixes and installation instructions here

The issues that are fixed in Update Rollup 2 for Microsoft Dynamics CRM 4.0
Update Rollup 2 is a cumulative fix that includes all the fixes for the issues that are documented in Update Rollup 1. For more information about Update Rollup 1 and about the issues that it fixes, click the following article number to view the article in the Microsoft Knowledge Base:

952858 (http://support.microsoft.com/kb/952858/ ) Update Rollup 1 is available for Microsoft Dynamics CRM 4.0

This update rollup fixes the following issues:

  • 946745 (http://support.microsoft.com/kb/946745/ ) You cannot import the customization for an entity to a new system in Microsoft Dynamics CRM

  • 947762 (http://support.microsoft.com/kb/947762/ ) A workflow that is defined to be triggered on a "Record attribute change" condition may be unexpectedly triggered even though the monitored attribute is not changed in Microsoft Dynamics CRM 4.0

  • 948987 (http://support.microsoft.com/kb/948987/ ) Error message when you import data into Microsoft Dynamics CRM 4.0 by using the Data Import Wizard or start a new data migration by using Data Migration Manager: "Mismatched data delimiter: only one delimiter was found"

  • 949069 (http://support.microsoft.com/kb/949069/ ) Multi-lookup attributes are disabled in some forms after you import some customizations in Microsoft Dynamics CRM 4.0

  • 949202 (http://support.microsoft.com/kb/949202/ ) Error message when you click a section of a chart to view some data tables in Microsoft Dynamics CRM 4.0: "The processing of FilterExpression for table 'Table0' cannot be performed"

  • 949652 (http://support.microsoft.com/kb/949652/ ) Error message when you try to import a CSV file into Microsoft Dynamics CRM 4.0: "The source data is not in the required format"

  • 949844 (http://support.microsoft.com/kb/949844/ ) The Async service stops unexpectedly or you cannot start the Async service after you import an organization from another Microsoft Dynamics CRM 4.0 deployment

  • 950207 (http://support.microsoft.com/kb/950207/ ) Error message when you try to open a campaign activity in Microsoft Dynamics CRM 4.0: "Exception of type 'System.Web.HttpUnhandledException' was thrown"

  • 950266 (http://support.microsoft.com/kb/950266/ ) You are looped in the sign-in page when you try to run the Data Migration Manager Wizard in Microsoft Dynamics CRM 4.0

  • 950307 (http://support.microsoft.com/kb/950307/ ) The go offline process does not download a user record to the local MSDE database in Microsoft Dynamics CRM 4.0

  • 950372 (http://support.microsoft.com/kb/950372/ ) You are prompted to enter your user name and password multiple times when you start Outlook, or when you click a Microsoft Dynamics CRM folder in Outlook, on a Windows Vista-based computer

  • 951432 (http://support.microsoft.com/kb/951432/ ) You cannot go online again in the Microsoft Dynamics CRM 4.0 client for Outlook with Offline Access if you switch to a different network connection while you are offline

  • 951909 (http://support.microsoft.com/kb/951909/ ) Error message when you try to import a customization to another Microsoft Dynamics CRM 4.0 server: "Invalid name prefix"

  • 952148 (http://support.microsoft.com/kb/952148/ ) Error message the first time that you try to go online after you upgrade the Microsoft Dynamics CRM 3.0 client for Outlook to the Microsoft Dynamics CRM 4.0 client for Outlook with Offline Access: "An unidentified error occurred"

  • 952322 (http://support.microsoft.com/kb/952322/ ) A workflow rule does not work as expected when you perform the workflow rule in Microsoft Dynamics CRM 4.0

  • 952599 (http://support.microsoft.com/kb/952599/ ) The label of the address field may be incorrect after you publish the customization of the Contact entity and the Account entity in Microsoft Dynamics CRM 4.0

  • 952658 (http://support.microsoft.com/kb/952658/ ) You cannot find a Knowledge Base article when you search for this article in the Microsoft Dynamics CRM 4.0 client for Outlook

  • 952680 (http://support.microsoft.com/kb/952680/ ) Error message when you try to add a contract line to a contract in Microsoft Dynamics CRM 4.0: "The requested record was not found or you do not have sufficient permissions to view it"

  • 952852 (http://support.microsoft.com/kb/952852/ ) The returned count is incorrect when you run a FetchXML query from the Microsoft Dynamics CRM 4.0 Software Development Kit

  • 952855 (http://support.microsoft.com/kb/952855/ ) A user who has the Administrative mode client access license can access custom entities unexpectedly in Microsoft Dynamics CRM 4.0

  • 953033 (http://support.microsoft.com/kb/953033/ ) Error message when you try to import data that involves a picklist attribute in Microsoft Dynamics CRM 4.0: "Transform parse data"

  • 953489 (http://support.microsoft.com/kb/953489/ ) No records are displayed when you perform a mail merge against the "All Records On Current Page" option or against the "All Records On All Pages" option in Microsoft Dynamics CRM 4.0

  • 953586 (http://support.microsoft.com/kb/953586/ ) Error message when you try to start the Async service in Microsoft Dynamics CRM 4.0: "Exception while starting async service: MSCRMAsyncService"

  • 953764 (http://support.microsoft.com/kb/953764/ ) The "Parent Downloaded" filter on a Custom entity does not work as expected in Microsoft Dynamics CRM 4.0

  • 953887 (http://support.microsoft.com/kb/953887/ ) Error message when you try to edit some properties of an imported workflow in Microsoft Dynamics CRM 4.0: "Record is unavailable"

  • 953999 (http://support.microsoft.com/kb/953999/ ) Microsoft Dynamics CRM 4.0 does not return the results if you try to export the results to an Excel worksheet after you use the Next X Days condition in the Advance Find query

  • 954227 (http://support.microsoft.com/kb/954227/ ) Error message when you run the Duplicate Detect function on data records in Microsoft Dynamics CRM 4.0: "Object required"

  • 954313 (http://support.microsoft.com/kb/954313/ ) Error message when you try to log on to the Microsoft Dynamics CRM Web site from the Microsoft Dynamics CRM 4.0 server: "Request IP Address has different address family from network address"

  • 954322 (http://support.microsoft.com/kb/954322/ ) Error message when you import some customizations to an upgraded installation of Microsoft Dynamics CRM 4.0: "Either the file could not be uploaded or Import failed"

  • 954433 (http://support.microsoft.com/kb/954433/ ) You receive an error message or you cannot select the lookup value in the Advanced Find page in Microsoft Dynamics CRM 4.0

  • 954592 (http://support.microsoft.com/kb/954592/ ) Any mappings between the Lookup property of a custom entity and the Customer property of a quote use an incorrect object type code after you create a relationship in Microsoft Dynamics CRM 4.0

  • 954640 (http://support.microsoft.com/kb/954640/ ) A folder that does not have a name appears in the Parent field when you open the Address form in Microsoft Dynamics CRM 4.0

  • 954682 (http://support.microsoft.com/kb/954682/ ) The tab sequence is not in the expected order if tabs contain large sections that include multi-row fields in Microsoft Dynamics CRM 4.0

  • 954929 (http://support.microsoft.com/kb/954929/ ) Performance is poor when you change a user from one business unit to another in Deployment Manager in Microsoft Dynamics CRM 4.0

  • 954940 (http://support.microsoft.com/kb/954940/ ) Error message when you try to delete a custom entity record in Microsoft Dynamics CRM 4.0: "An error has occurred, please contact your administrator"

  • 955006 (http://support.microsoft.com/kb/955006/ ) You cannot add a user from a parent domain to Microsoft Dynamics CRM 4.0

  • 955051 (http://support.microsoft.com/kb/955051/ ) Not all the required attributes are selected and displayed correctly when you define a new Data Map that targets the Contract entity in Microsoft Dynamics CRM 4.0

  • 955055 (http://support.microsoft.com/kb/955055/ ) Error message when you open a Mail Merge document in Microsoft Dynamics CRM 4.0: "Mail_Merge_[Number][1] is a mail merge main document. Word cannot find its data source"

  • 955058 (http://support.microsoft.com/kb/955058/ ) Performance is slow when you perform some configuration changes in Microsoft Dynamics CRM 4.0

  • 955061 (http://support.microsoft.com/kb/955061/ ) Error message when you use a Presend Callout event to retrieve the regarding object of an e-mail message in the Microsoft Dynamics CRM 4.0 client for Outlook: "Send() failed, HR = 80045f00"

  • 955064 (http://support.microsoft.com/kb/955064/ ) You cannot view created activities in the Campaign Activity form in the Microsoft Dynamics CRM 4.0 Web client

  • 955206 (http://support.microsoft.com/kb/955206/ ) A report snapshot is not created when you try to schedule a report in Microsoft Dynamics CRM 4.0

  • 955233 (http://support.microsoft.com/kb/955233/ ) You receive an error message when you save a security role in Microsoft Dynamics CRM 4.0

  • 955253 (http://support.microsoft.com/kb/955253/ ) Error message when you try to add attendees into an existing appointment in Microsoft Dynamics CRM 4.0: "You do not have enough privileges to access the Microsoft Dynamics CRM object or perform the requested operation"

  • 955418 (http://support.microsoft.com/kb/955418/ ) You cannot delete a note by using a user for which a role has no the Print permission in Microsoft Dynamics CRM 4.0

  • 955422 (http://support.microsoft.com/kb/955422/ ) Error message when you try to reopen a closed opportunity in Microsoft Dynamics CRM 4.0: "1 is not a valid status code on opportunity"

  • 955423 (http://support.microsoft.com/kb/955423/ ) Error message when you merge two accounts that are added to an inactive marketing list in Microsoft Dynamics CRM 4.0: "The merge is cancelled, contact your systems administrator and try again"

  • 955469 (http://support.microsoft.com/kb/955469/ ) You receive an error message when you try to assign an instance of an entity to another user in the Microsoft Dynamics CRM Web client or in the Microsoft Dynamics CRM 4.0 client for Outlook

  • 955482 (http://support.microsoft.com/kb/955482/ ) The "actualstart" attribute and the "actualend" attribute of the ActivityPointer entity are unexpectedly set to "Date Only" in Microsoft Dynamics CRM 4.0

  • 955487 (http://support.microsoft.com/kb/955487/ ) The line feeds are lost when you send an e-mail message by using the mail merge template in Microsoft Dynamics CRM 4.0

  • 955574 (http://support.microsoft.com/kb/955574/ ) Error message when you perform a mail merge in Microsoft Dynamics CRM 4.0: "Error 0x80041103 'Contact' entity doesn't contain attribute with Name = ''"

  • 955685 (http://support.microsoft.com/kb/955685/ ) A user who has the Assign Role privilege in a child business unit can unexpectedly assign the System Administrator role in Microsoft Dynamics CRM 4.0

  • 955750 (http://support.microsoft.com/kb/955750/ ) You can unexpectedly create a service appointment even if you do not have the privileges of the Service entity in Microsoft Dynamics CRM 4.0

  • 955833 (http://support.microsoft.com/kb/955833/ ) Error message when you try to change a logon user account in the Specify Security Account page in Microsoft Dynamics CRM 4.0: "The Microsoft CRM services account is not valid"

  • 955977 (http://support.microsoft.com/kb/955977/ ) You cannot open a custom entity record while you are offline even if you have permission to open the record in the Microsoft Dynamics CRM 4.0 client for Microsoft Office Outlook

  • 955981 (http://support.microsoft.com/kb/955981/ ) Error message when you try to open a custom view in a service calendar in Microsoft Dynamics CRM 4.0: "savedquery With Id = 407a955c-6053-dd11-858a-000bdbda0c1e Does Not Exist"

  • 956045 (http://support.microsoft.com/kb/956045/ ) Only the short date format is displayed in the "Created On" and "Last Modified On" fields in the "Properties Web page" dialog box of a record in Microsoft Dynamics CRM 4.0

  • 956079 (http://support.microsoft.com/kb/956079/ ) Only records that were changed in the past 30 days are displayed for the related record type when you create a report by using the Report Wizard in Microsoft Dynamics CRM 4.0

  • 956112 (http://support.microsoft.com/kb/956112/ ) Error messages in the Application log on the Microsoft Dynamics CRM server after you delete a quick campaign: "Deletion Service failed to clean up table=[Table_Name]"

  • 956127 (http://support.microsoft.com/kb/956127/ ) Some Outlook Synchronization entity attributes are missing in an exported customizations file from Microsoft Dynamics CRM 4.0

  • 956151 (http://support.microsoft.com/kb/956151/ ) Error message in the Service Calendar in Microsoft Dynamics CRM 4.0: "Query Builder Error"

  • 956237 (http://support.microsoft.com/kb/956237/ ) The workflow remains in a waiting state after you create a workflow rule to update the status of an opportunity in Microsoft Dynamics CRM 4.0

  • 956257 (http://support.microsoft.com/kb/956257/ ) The fiscal year start date is incorrect in Microsoft Dynamics CRM 4.0 if you are in a time zone of GMT+12 or GMT+13

  • 956282 (http://support.microsoft.com/kb/956282/ ) Error message when you use the Microsoft Dynamics CRM 4.0 SDK to develop a Custom Workflow Activity assembly: "The Key cannot be NULL"

  • 956283 (http://support.microsoft.com/kb/956283/ ) Error message when you try to edit a weekly working schedule for a user or for equipment in Microsoft Dynamics CRM 4.0: "An error has occurred and you should contact your administrator"

  • 956370 (http://support.microsoft.com/kb/956370/ ) The date in the Start Date field in a contract line is incorrect after you perform the Renew Contract action in Microsoft Dynamics CRM 4.0

  • 956445 (http://support.microsoft.com/kb/956445/ ) A record remains in the Microsoft Dynamics CRM database after you delete the record in the Microsoft Dynamics CRM 4.0 Web client

  • 956521 (http://support.microsoft.com/kb/956521/ ) Changes are not reflected if you reschedule a service activity by using the "Reschedule" button in Microsoft Dynamics CRM 4.0

  • 956537 (http://support.microsoft.com/kb/956537/ ) The attachment that is included in a mail merge template is lost during the customization import process in Microsoft Dynamics CRM 4.0

  • 956751 (http://support.microsoft.com/kb/956751/ ) A workflow is triggered two times even though you set the corresponding workflow rule to run only when the activity status is Completed in Microsoft Dynamics CRM 4.0

  • 956771 (http://support.microsoft.com/kb/956771/ ) A mail merge template is unexpectedly associated with an incorrect custom entity after you export the template into a new environment in Microsoft Dynamics CRM 4.0

  • 956852 (http://support.microsoft.com/kb/956852/ ) Error message when you run a report that uses the "StoredProcedure" command type in the Microsoft Dynamics CRM Connector for SQL Server Reporting Services: "Query execution failed for data set 'Test_MSCRM'"

  • 956859 (http://support.microsoft.com/kb/956859/ ) The Microsoft Dynamics CRM toolbar is disabled in Outlook after you lose the network connection for less than one minute

  • 957031 (http://support.microsoft.com/kb/957031/ ) Error message when you try to start Microsoft Dynamics CRM 4.0 after you upgrade the operating system to Windows Server 2008: "The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly"

  • 957057 (http://support.microsoft.com/kb/957057/ ) You cannot set the Delete behavior to "Remove Link" or to "Restrict" for a custom relationship between two custom entities in Microsoft Dynamics CRM 4.0

  • 957086 (http://support.microsoft.com/kb/957086/ ) Error message when you try to change an organizer of an appointment in Microsoft Dynamics CRM 4.0: "You cannot unshare this record. The owner of the selected record is the only one allowed to move others from the share"

  • 957225 (http://support.microsoft.com/kb/957225/ ) Microsoft Dynamics CRM 4.0 unexpectedly triggers a workflow rule when you send a quick campaign e-mail activity

  • 957270 (http://support.microsoft.com/kb/957270/ ) You can unexpectedly promote an appointment that has no specified subject even though the Subject attribute of the Appointment entity is set to Business Required in Microsoft Dynamics CRM 4.0

  • 957299 (http://support.microsoft.com/kb/957299/ ) You receive an error message when you click Set Properties on a Send E-mail step in Microsoft Dynamics CRM 4.0 Workflow Designer

  • 957305 (http://support.microsoft.com/kb/957305/ ) An unexpected error message occurs when you add products to the quotes, orders, or invoices that are created from an opportunity in Microsoft Dynamics CRM 4.0

  • 957318 (http://support.microsoft.com/kb/957318/ ) In the Service Calendar in Microsoft Dynamics CRM 4.0, you can view records for the users and for the equipment that you do not have access to through your security role

  • 957377 (http://support.microsoft.com/kb/957377/ ) Localized views contain an invalid layoutXML element after you upgrade the Norwegian version of Microsoft Dynamics CRM 3.0 to the Norwegian version of Microsoft Dynamics CRM 4.0

  • 957380 (http://support.microsoft.com/kb/957380/ ) You cannot set the statuscode attribute by using the CompoundCreate process before you create the invoice in Microsoft Dynamics CRM 4.0

  • 957406 (http://support.microsoft.com/kb/957406/ ) Error message when you try to create an appointment by using the Contact form in Microsoft Dynamics CRM 4.0: "At least one recipient does not have an e-mail address or is marked as "Do Not Allow" e-mail"

  • 957421 (http://support.microsoft.com/kb/957421/ ) Outlook may crash when you synchronize Outlook with the Microsoft Dynamics CRM 4.0 client for Outlook

  • 957589 (http://support.microsoft.com/kb/957589/ ) Error message when you try to edit some columns of the workflow entity views by using the Advanced Find feature in Microsoft Dynamics CRM 4.0: "Microsoft Dynamics CRM has encountered an error"

  • 957704 (http://support.microsoft.com/kb/957704/ ) No users are found when you search for some system users by using their last names from a relationship in Microsoft Dynamics CRM 4.0

  • 957788 (http://support.microsoft.com/kb/957788/ ) Error message when you try to open an activity that is based on an ActivityPointer entity in a custom report in Microsoft Dynamics CRM 4.0: "4200 is not a recognized Object type"

  • 957919 (http://support.microsoft.com/kb/957919/ ) You receive the incorrect error message when you create the same invoice again in Microsoft Dynamics CRM 4.0

  • 957920 (http://support.microsoft.com/kb/957920/ ) No e-mail message is sent after you complete the Create Quick Campaign Wizard in Microsoft Dynamics CRM 4.0

  • 957960 (http://support.microsoft.com/kb/957960/ ) You cannot go online after you send an e-mail message to another user in Microsoft Dynamics CRM 4.0 client for Microsoft Office Outlook

  • 957970 (http://support.microsoft.com/kb/957970/ ) Tabs may disappear when you click between the tabs of some entity forms in Microsoft Dynamics CRM 4.0 and the desktop

  • 957975 (http://support.microsoft.com/kb/957975/ ) Microsoft Dynamics CRM 4.0 processes a decimal value incorrectly when you run a workflow

  • 958003 (http://support.microsoft.com/kb/958003/ ) Error message when you publish an imported workflow in Microsoft Dynamics CRM 4.0: "Automatic workflow cannot be published if no activation parameters have been specified"

  • 958031 (http://support.microsoft.com/kb/958031/ ) Error message when you go online in the Microsoft Dynamics CRM 4.0 client for Outlook over a low-bandwidth network or a high-latency network: "An unknown error has occurred"

  • 958072 (http://support.microsoft.com/kb/958072/ ) You cannot use some user queries that run against contacts, leads, or accounts after you upgrade from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0

  • 958181 (http://support.microsoft.com/kb/958181/ ) Error message when you import an organization in Microsoft Dynamics CRM 4.0: "The type or namespace name 'InvokeDotNetAssembly' does not exist in the namespace 'Microsoft.Crm.Workflow'"

  • 958256 (http://support.microsoft.com/kb/958256/ ) The Parent Customer field is not populated on the contact record after you convert a lead to an account record and to a contact record in Microsoft Dynamics CRM 4.0

  • 958280 (http://support.microsoft.com/kb/958280/ ) Error message when you try to save a recurring weekly schedule in Microsoft Dynamics CRM 4.0: "Value was either too large or too small for an Int32"

  • 958287 (http://support.microsoft.com/kb/958287/ ) Error message when you view an activity form in Microsoft Dynamics CRM 4.0: "Exception of type 'System.Web.HttpUnhandledException' was thrown"

  • 958363 (http://support.microsoft.com/kb/958363/ ) You cannot upgrade some saved queries from Microsoft Dynamics CRM 3.0 to Microsoft Dynamics CRM 4.0

  • 958487 (http://support.microsoft.com/kb/958487/ ) Error message when the administrator bulk reassigns records from one user to another user in Microsoft Dynamics CRM 4.0: "Only published workflows and workflow templates can be unpublished"

  • 958563 (http://support.microsoft.com/kb/958563/ ) The contents of the body of an e-mail message are not displayed when you view the properties for a step that refers to an e-mail message in a workflow in Microsoft Dynamics CRM 4.0

  • 958791 (http://support.microsoft.com/kb/958791/ ) Error message when you try to add a user from a trusted domain to Microsoft Dynamics CRM 4.0: "An error has occurred"

  • 958836 (http://support.microsoft.com/kb/958836/ ) Error message when you run a custom report in Microsoft Dynamics CRM 4.0: "An error has occurred"

  • 958902 (http://support.microsoft.com/kb/958902/ ) The tabs are truncated or invisible when you add notes to an entity form in Microsoft Dynamics CRM 4.0

  • 959208 (http://support.microsoft.com/kb/959208/ ) The duplicate detection job does not detect all duplicates in Microsoft Dynamics CRM 4.0

  • 959226 (http://support.microsoft.com/kb/959226/ ) Error message when you import an organization into Microsoft Dynamics CRM 4.0: "Changing the report parameters or data sources to the values you specified is not allowed"

  • 959248 (http://support.microsoft.com/kb/959248/ ) Microsoft Dynamics CRM 4.0 slows to unacceptable levels when you process e-mail messages by using the Microsoft Dynamics CRM E-mail Router

  • 959394 (http://support.microsoft.com/kb/959394/ ) An incorrect record is opened when you double-click a record in Microsoft Dynamics CRM 4.0

  • 959572 (http://support.microsoft.com/kb/959572/ ) The "Source Campaign" field on an opportunity is not populated when you convert a campaign response in Microsoft Dynamics CRM 4.0

  • 960249 (http://support.microsoft.com/kb/960249/ ) Error message when you try to run the Data Import function to import some data in the Traditional Chinese (CHT) version of Microsoft Dynamics CRM 4.0: "CrmSoapExtension detected non-CrmException"

  • 960286 (http://support.microsoft.com/kb/960286/ ) A new update is available for the time zone and daylight saving time changes in Microsoft Dynamics CRM 4.0 and in the Microsoft Dynamics CRM 4.0 client for Microsoft Office Outlook

This update rollup fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
  • If you add users from an Outgoing forest trusted domain, you receive the following error message:

    AuthenticationException: Logon failure: unknown user name or bad password.

  • If BulkDeleteIndependent_ tables are created and if the dbo user account is not the owner of these tables, the database size increases.
  • If you enter custom attributes by using the Mail Merge process, the activities that are created by the Mail Merge process may lose the values for the custom attributes.
  • When you synchronize Microsoft Office Outlook with Microsoft Dynamics CRM 4.0, the attendee response tracking of an Outlook appointment is broken. This issue occurs in Microsoft Office Outlook 2003 and in Microsoft Office Outlook 2007.
  • After you apply update 959209, you cannot publish XAML workflows. For more information about update 959209, click the following article number to view the article in the Microsoft Knowledge Base:

    959209 (http://support.microsoft.com/kb/959209/ ) An update for the .NET Framework 3.5 Service Pack 1 is available

  • When you use impersonation in an Internet-Facing Deployment (IFD) environment, you receive the following error message:

    0x80040204 Invalid user auth.

  • When you try to import a Data Map of the Customer Relationship type, you receive the following error message:

    Unmapped required columns: 1

  • When you run a report as a user who is disabled in another organization, you receive the following error message:

    Error Number: 0x80040225
    Error Message: The specified user is either disabled or is not a member of any business unit.

  • When you go offline in the German version of the Microsoft Dynamics CRM client for Outlook, you receive the following error message:

    0x80044150
    Generic SQL error

  • Notification tables do not have useful indexes that can improve performance.
  • The related entity data is not returned when you perform an Advanced Find query for Activity entities. Examples of Activity entities are as follows:
    • The Appointment entity
    • The E-Mail entity
    • The Fax entity
    • The Phone call entity
  • Reports that use the FilteredActivityPointer view return incorrect statuscode values.
  • Serializable connections are not reset to the Read Committed isolation level. Therefore, when a transaction is committed, you may encounter locks in Microsoft SQL Server.
  • When you click Set Properties in a workflow on a custom workflow activity, static text is deleted.
  • Microsoft Dynamics CRM 4.0 cannot load custom pages that reference assemblies. This issue occurs if the assemblies are deployed to the following folder:

    <crmwebroot>\ISV\<app>\bin

  • When you edit the IF condition in a workflow in the Brazilian version of Microsoft Dynamics CRM 4.0, the date format is changed from dd/mm/yyyy to mm/dd/yyyy. This issue occurs if you open the IF condition.
  • When you run a saved query from a grid and then you click Mail Merge, the data that is included in the data source is not filtered based on the filters for the saved query.
  • You cannot register a plug-in on the Create message for the CustomerOpportunityRole entity.

 

Hotfixes and updates that you have to enable or configure manually
Update Rollup 2 for Microsoft Dynamics CRM 4.0 contains the following hotfixes and updates that you have to enable or configure manually. To enable or configure these hotfixes on the server that is running Microsoft CRM 4.0, follow the instructions in the following Microsoft Knowledge Base articles:
  • 955138 (http://support.microsoft.com/kb/955138/ ) You experience slow performance or timeouts when you try to access some views in Microsoft Dynamics CRM 4.0

  • 955452 (http://support.microsoft.com/kb/955452/ ) Line feeds are not used when you send an e-mail message that uses an e-mail template to render data that has line feeds in Microsoft Dynamics CRM 4.0

  • 955745 (http://support.microsoft.com/kb/955745/ ) Error message when you try to configure the Microsoft Dynamics CRM 4.0 client for Outlook: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms"

  • 956527 (http://support.microsoft.com/kb/956527/ ) The Microsoft Dynamics CRM client for Outlook consumes three times as much memory in version 4.0 as in version 3.0