Article ID: 913275
Article Last Modified on 7/17/2007
APPLIES TO
- Microsoft Dynamics CRM 3.0
SYMPTOMS
Neither the PreSetState callout event nor the PostSetState callout event is run when a user is disabled in Microsoft Dynamics CRM 3.0. Additionally, the custom business logic is not run. This problem occurs if the following conditions are true:
- You subscribed to the PreSetState callout event or to the PostSetState callout event for the SystemUser entity. Then, you created custom business logic that responds to the event.
- You used one of the following methods to disable a user:
- You used the SystemUserSetState message and the Execute method from the CrmService Web service.
- In Microsoft Dynamics CRM 3.0, you disabled the user in the business unit settings.
Note To disable a user in this manner, click Settings, click Business Unit Settings, click Users, click the user, click More Actions, and then click Disable.
RESOLUTION
This problem is fixed 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:
927751 Update Rollup 2 is available for Microsoft Dynamics CRM 3.0
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 Description of the standard terminology that is used to describe Microsoft software updates
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards
Additional query words: crm3 crm30 crm3.0
Keywords: kbmbscustomization kbhotfixserver kbqfe kbmbsmigrate kbpubtypekc KB913275
