Exchange 2003 MSExchangeIS Mailbox Error Event ID 1022
The application event log on our Exchange 2003 server is full of error Event ID: 1022 (attached).
They start at 7p every night and run until about 12a -- repeating the error for the same dozen or so users over and over about every 10-20 minutes.
Looking at the accounts, they do appaer to be newer accounts or special accounts that aren't used often. Maybe it's account that haven't been logged into yet?
We use Symantec BackupExec on this server.
Microsoft KB suggests making sure the accounts are not locked or disabled - no fix there.
Another post on here said a SP install fixed their problem, but I'm already on SP2 for both the Server and Exchange.
Thoughts?
They start at 7p every night and run until about 12a -- repeating the error for the same dozen or so users over and over about every 10-20 minutes.
Looking at the accounts, they do appaer to be newer accounts or special accounts that aren't used often. Maybe it's account that haven't been logged into yet?
We use Symantec BackupExec on this server.
Microsoft KB suggests making sure the accounts are not locked or disabled - no fix there.
Another post on here said a SP install fixed their problem, but I'm already on SP2 for both the Server and Exchange.
Thoughts?
MSExchangeIS Mailbox
Logon Failure on database "First Storage Group\Mailbox Store (SUNNA)" - Windows 2000 account NT AUTHORITY\SYSTEM; mailbox /o=Dana College/ou=First Administrative Group/cn=Recipients/cn=doe.john .
Error: -2147221231
Rajith Enchiparambil
http://support.microsoft.com/kb/555420
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Rajith_Enchiparambil -
The accounts aren't disabled or locked out.
gupnit -
Can you expand on the last step?
"Reset the Associated External Account permission to SELF."
If no account has the Associated External Account permission, give it to SELF . . . and then "Reset" the permission? How?
The accounts aren't disabled or locked out.
gupnit -
Can you expand on the last step?
"Reset the Associated External Account permission to SELF."
If no account has the Associated External Account permission, give it to SELF . . . and then "Reset" the permission? How?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hope the Link Rajith gave helped you....let me know if u have further queries...:-)
ASKER
Sorry, guys: beginner here.
I'm more confused now.
We don't have multiple forests.
Should I still grant External Associated Account permission to the SELF of the problem accounts?
Looking at non-problem accounts, no user has the EAA permission either.
I'm more confused now.
We don't have multiple forests.
Should I still grant External Associated Account permission to the SELF of the problem accounts?
Looking at non-problem accounts, no user has the EAA permission either.
It has nothing to do with multple forest.
You can follow the article above. It won;t do any harm.
You can follow the article above. It won;t do any harm.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@tastas: That sounds quite possible. The accounts with errors appear to be either new (not yet logged into) or very old and abandoned.
Once users logged into their new mailboxes they quit throwing the error. The remaining errors are for the abandoned accounts which I'll have to track down and re-create or delete.
Thanks to all.
Once users logged into their new mailboxes they quit throwing the error. The remaining errors are for the abandoned accounts which I'll have to track down and re-create or delete.
Thanks to all.
ASKER
Thanks