Exchange Server 5.5 records event 1016 in the application event log regardless of how you set the diagnostic logging level in the Microsoft Exchange Information Store service (Store.exe). Exchange 2000 and Exchange 2003 only log event 1016 in the application event log when the diagnostic logging level is set to at least Minimum in the Logons category of the Microsoft Exchange Information Store service.
This event is also logged when you try to access another user's mailbox or calendar, even if you have permission to access the mailbox or the calendar. This event is logged regardless of whether your attempt to access the user's mailbox or calendar is successful or unsuccessful. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
- When an account logs on to a mailbox successfully. For example, if Jane Doe has the required permissions and logs on to John Doe's mailbox, the Mailbox Resources tab will show that the account (Jane Doe) is logged on to the Exchange Mailbox (John Doe) at the time that the user logged on.
- When a user tries to access another user’s mailbox folders, such as the Inbox, Calendar, Contacts, Journal, Tasks, or Notes folders. For example, Jane Doe logs on to her own mailbox and then tries to gain access to John Doe's calendar. She receives a message that states that she does not have permissions. However, the Mailbox Resources tab shows that the account (Jane Doe) is logged on to the Exchange Mailbox (John Doe) at the time that the user logged on.
- When an account logs on to a mailbox, Mailbox Resources is updated to show that the Exchange Service Account has logged on to the System Attendant mailbox.
Note The Exchange Service Account is the account that is used to start the Microsoft Exchange System Attendant service.
- Mailbox Resources does not show which folder is being logged on to. For example, Mailbox Resources does not indicate whether it is the Inbox, the Calendar, or the Contacts folder.
- Mailbox Resources does not show whether the logon was successful or unsuccessful.
Article ID: 867640 - Last Review: 25 Oct 2007 - Revision: 1