Article ID: 952673 - Last Review: January 20, 2012 - Revision: 3.2

Error message when you try to open a Calendar view in Microsoft Dynamics CRM 4.0: "Event Journaling Invalid Recipient Type"

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

In Microsoft Dynamics CRM 4.0, you specify a time-off day on the Schedule Time Off page for a user. When you try to open a Calendar view from the Workplace pane, you receive the following error message:
Event Journaling
Invalid Recipient Type
Additionally, if the DevErrors value in the Web.config file is set to On, you receive the following error message:
The 'Retrieve' method does not support entities of type 'CalendarRule'.
Back to the top

RESOLUTION

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949256  (http://support.microsoft.com/kb/949256/ ) Microsoft Dynamics CRM 4.0 updates and hotfixes
Back to the top

STATUS

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

MORE INFORMATION

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:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
887283  (http://support.microsoft.com/kb/887283/ ) Microsoft Business Solutions CRM software hotfix and update package naming standards
Back to the top
APPLIES TO
  • Microsoft Dynamics CRM 4.0
Back to the top
Keywords: 
kberrmsg kbmbsmigrate kbqfe kbhotfixserver kbfix kbautohotfix kbexpertiseinter KB952673
Back to the top