Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

EventID: 1023 Failure Audit Logon

Status
Not open for further replies.

dennisbbb

MIS
Jun 4, 2003
489
US
EventID: 1023
Failure Audit
Logons


ExchgSvr\JohnDoe was validated as /o=ExchgSvr/ou=Corporate/cn=Recipients/cn=JohnDoe but was unable to log on to /o=ExchgSvr/ou=Corporate/cn=Recipients/cn=JaneSmith.

=========================================================
The problem:
JaneSmith has long left the company. Mailbox and username had been deleted off the server.

From Microsoft.com
Event ID: 1023
Source: MSExchangeIS Private
Type: Failure Audit
Category: Logons
Description:
MESSAGING\ServiceAccount was validated as
/o=Organization/ou=Site/cn=Recipients, Utility/cn=MSExchangeMCA
but was unable to log on to
/o=Organization/ou=Site/cn=Recipients/cn=mailbox.


CAUSE
This event is logged when you run MBClean from a server where the user mailboxes do not reside. This event is informational only and does not result in any failures in running MBCLean. The event can be ignored.

WORKAROUND
Install MBClean on a server where the user mailboxes are located

DIFFERENCES:

I don't have MBClean installed on the Server. The attempt is by another user "johndoe".

Suspicion and Question:

Since this may likely be caused by an Appointment/scheduler/invitation in Outlook, how does one stop this problem from the Exchange Server Administrator console?

 
Go to John Doe's workstation and check his Outlook profile. Make sure he is not trying to open Jane Smith's mailbox along with his own.
 
Thanks for the reply fuego007. That will be my last step to look at with this problem. There are so far 2 users that have a tendency to cause this log on the Exchange. The possibility of them trying to log on as the ex-user is not likely because this log is random thru out the week (as if there was an embedded link on an Excel sheet with the ex-user info).

 
This problem was resolved by deleting the problem user's (JohnDoe) "default" email profile and recreating a new one.
 
It was probably a delegate issue - they are usually the cause of this sort of thing when all other avenues have been tried.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top