Article ID: 222066 - View products that this article applies to.
This article was previously published under Q222066
This article is a consolidation of the following previously available articles: 222066, 288264 and 326648
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
When you use the MsExchange Event Services (Events.exe) in a Microsoft Exchange Server 5.5 or a Microsoft Exchange 2000 Server environment, you may receive the following error message in the application event log when a client action spawns the activation of a script:
Event ID: 11
Depending on the size of your environment, you may notice that some or all scripts are not running. In a large environment, it may appear that the scripts are running successfully because of the inability to pinpoint the failing script.
This issue may occur if any one of the following conditions are true:
Step1: Determine if there is a duplicate mailbox alias (Mixed or Pure Exchange environments)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.
After the multiple aliases have been determined, you must decide whether you want to choose a different (unique) mailbox to edit the scripts or remove the other mailboxes from the global address list.
If the scripts are installed in mailbox folders, the next part is even more detailed if you do not have a list of which mailboxes have scripts associated with them or there are many that do. This is because even with Event Service logging turned up to Maximum (5) in the registry, the Event ID 16385 (which occurs just before the Event ID 11) says that the folder being processed is Inbox. Every mailbox has an Inbox folder. So you cannot know which mailbox has been altered by the "rogue" EventConfig owner.
Step2: Resolve known issues with permissions (Mixed or Pure Exchange environments)
NOTE Step1 and/or Step2 should resolve the event error in a pure Exchange 5.5 organization. If Event ID 11 is still being logged and you are in a mixed Exchange environment, go to Step3.
Step3 (Mixed Exchange 2000 and Exchange 5.5 environment only)Add the MSExchange Event system service account on the Exchange 2000 Server-based computer to the folder client-permissions list as owner.
NOTE The additions of the same Exchange Server 5.5 service account to the Exchange 2000 Server event service does not resolve this issue.
An Event ID 15 is logged with the same MAPI error code (80040111) if the execution of the script has been scheduled to run. Make sure the mailboxes that have Owner permissions on the EventConfig_servername folder are not hidden because the Event Service algorithm needs to resolve the name before it executes. It is a good idea to name the Event Service Accounts something that will be unique to the global address list and always log on as this person when you want to modify the scripts.
The EventSink caches the information about the last person who modified the script. However, if there is more than one user in the global address list with the same alias as the person that last modified a folder's Agent or Script, the Collaboration Data Objects (CDO) routine cannot determine which alias is the correct one, so it stops responding and logs the 80040111(MAPI_E_LOGON_FAILURE) error. This error creates the impression that the account that caused the script to run doesn't have the necessary permissions on the folder, which is not true. In fact, it is the CDO routine that fails to log on to run the script from within the Event Service.
For more information about how to use Exchange Event Service with Exchange 2000, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/277844/ )Exchange 2000 Release Notes, Part I
Contact us for more help
Connect with Answer Desk for expert help.