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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Event 1022 Errors After Moving Mailbox

Status
Not open for further replies.

philzero

IS-IT--Management
Jan 9, 2009
6
GB
After I move a mailbox between databases, whether on the same server or not, every 15 minutes I get the follow event generated in the application log for the original database location:

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: Logons
Event ID: 1022
Date: 4/15/2010
Time: 11:46:50 AM
User: N/A
Computer: ExServer
Description:
Logon Failure on database "MailSG\MailDB" - Windows account NT AUTHORITY\SYSTEM; mailbox /o=domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=mailuser.
Error: 1144
Client Machine: ExServer
Client Process: Microsoft.Exchange.Search.ExSearch.exe
Client ProcessId: 0
Client ApplicationId: Client=CI

The mailbox move completed successfully. The user account was not connected during the move. The mailbox can be accessed normally, doesn't appear to have any problem or errors sending/receiving/viewing mail.

It just looks like MSExchangeSearch is trying to index the mailbox every 15 minutes in the wrong location, so it keeps generating these errors. It's annoying more than anything else, but I'd like to resolve it if possible.
Any thoughts gratefully received.
 
Normally you only get one of these errors after a mailbox move, but sometimes if AD information is cached by the Store service and not refreshed, the errors will continue to happen for several hours after a move and then go away. They will certainly not survive a reboot, so I wouldn't worry about them.

Dave Shackelford MVP
ThirdTier.net
TrainSignal.com
 
Thanks for the response. In this case the errors lasted for 25 hours before stopping - seems like a long time for AD info to be cached. Annoying to not know how to stop these errors, but at least they seem to clear themselves up.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top