How to Troubleshoot an Event 9983 in the Windows Application Event Log (822791)



The information in this article applies to:

  • Microsoft Operations Manager 2000

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SUMMARY

This article discusses how to troubleshoot an Event ID 9983 event message in the Windows Application event log. You may receive this event message when you use the "Check mailbox store availability - MAPI logon test (server_name)" event rule. This rule is available in the Exchange 2000 Management Pack for Microsoft Operations Manager (MOM) 2000.

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To locate the availability rule, follow these steps:
  1. Click Start, point to Programs, point to Microsoft Operations Manager, and then click MOM Administrator Console.
  2. Expand Microsoft Operations Manager (default).
  3. Expand Rules, and then expand Processing Rule Groups.
  4. Expand Microsoft Exchange 2000 Server (enabled), expand Server Availability Monitoring (enabled), and then click MAPI Logon Check (enabled).
  5. On the right view pane under Event Rules, click Check mailbox store availability - MAPI logon test (SP1 - Local System).
This rule may generate an event 9983 in the Windows Application event log. This event triggers the Cannot verify Exchange Information Store service availability due to an unexpected error event rule. If the description for the Event 9983 is "Cannot Impersonate Mailbox Access Account", then either one of the following problems may be the cause:
  • The user credentials for the Mailbox Access account are incorrect. This account is specified when you run ExchangeMOMSetCredentialUtility.exe. The account information is then stored on the Exchange server. Review the Exchange 2000 Management Pack configuration guide for information about how to rerun ExchangeMOMSetCredentialUtility.exe with the correct credentials for the Mailbox Access account.
  • The Mailbox Access account does not have the "Log on locally" permission to the Exchange server. Confirm that the Mailbox Access account has "Log on locally" permissions in the Local Security Policy or in the Domain Controller Security Policy if the Exchange server is also a domain controller.
If the Event ID 9983 event message contains Error ID: 0x800406F7, confirm that the Mailbox Access account can read and write to the systemroot\Temp\Exmppd folder on the Exchange server. The temporary MAPI logon profiles are created in the Exmppd folder. To test the permission of the Mailbox Access account, follow these steps:
  1. Log on to the Exchange server as the Mailbox Access account.
  2. Click Start, and then click My Computer.
  3. Use Windows Explorer to locate the systemroot\Temp\Exmppd folder.
  4. Right-click in the folder window, point to New, and then click Text Document.
  5. Provide any name for the new file. If this procedure is successful, the account has all the required permissions.
Make sure the registry on the Exchange server points to the Exmppd folder. To do so, follow these steps:
  1. Click Start, and then click Run.
  2. Type regedit and then click OK.
  3. Locate the following key in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Windows Messaging Subsystem

  4. Confirm that the ProfileDirectory key has the following value:systemroot\temp\exmppd, for example c:\winnt\temp\exmppd.
Try to log on to the Exchange server as a domain user. If you cannot log on to the server, look for and resolve any errors reported on the domain controllers. Lastly, make sure that all the Exchange-related services are running on the Exchange server.

Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbSysAdmin kbinterop kbMiscTools kbhowto kbinfo KB822791 kbAudITPRO