<div>
<a href="http://support.microsoft.com/kb/555420" rel="ugc nofollow">http://support.microsoft.com/kb/555420</a>
</div>


<div>
<a href="http://support.microsoft.com/kb/278966" rel="ugc nofollow">http://support.microsoft.com/kb/278966</a>
</div>


<div>
Rajith_Enchiparambil -<br />
The accounts aren't disabled or locked out.<br />
<br />
gupnit - <br />
Can you expand on the last step?<br />
&quot;Reset the Associated External Account permission to SELF.&quot;<br />
<br />
If no account has the Associated External Account permission, give it to SELF . . . and then &quot;Reset&quot; the permission? How?
</div>


<div>
Hope the Link Rajith gave helped you....let me know if u have further queries...:-)
</div>


<div>
Sorry, guys: beginner here.<br />
I'm more confused now.<br />
We don't have multiple forests.<br />
Should I still grant External Associated Account permission to the SELF of the problem accounts?<br />
Looking at non-problem accounts, no user has the EAA permission either.
</div>


<div>
It has nothing to do with multple forest.<br />
You can follow the article above. It won;t do any harm.
</div>


<div>
@tastas: &nbsp;That sounds quite possible. &nbsp;The accounts with errors appear to be either new (not yet logged into) or very old and abandoned.<br />
<br />
Once users logged into their new mailboxes they quit throwing the error. &nbsp;The remaining errors are for the abandoned accounts which I'll have to track down and re-create or delete.<br />
<br />
Thanks to all.
</div>


<div>
<div class="content wysiwyg-content">
The application event log on our Exchange 2003 server is full of error Event ID: 1022 (attached).<br />
<br />
They start at 7p every night and run until about 12a -- &nbsp;repeating the error for the same dozen or so users over and over about every 10-20 minutes.<br />
<br />
Looking at the accounts, they do appaer to be newer accounts or special accounts that aren't used often. &nbsp;Maybe it's account that haven't been logged into yet?<br />
<br />
We use Symantec BackupExec on this server.<br />
<br />
Microsoft KB suggests making sure the accounts are not locked or disabled - no fix there.<br />
Another post on here said a SP install fixed their problem, but I'm already on SP2 for both the Server and Exchange.<br />
<br />
Thoughts?<br />

<pre><code class="code-1 nolinks" id="code-122758"><span>MSExchangeIS Mailbox</span>
<span> </span>
<span>Logon Failure on database &quot;First Storage Group\Mailbox Store (SUNNA)&quot; - Windows 2000 account NT AUTHORITY\SYSTEM; mailbox /o=Dana College/ou=First Administrative Group/cn=Recipients/cn=doe.john .</span>
<span>Error: -2147221231</span>
</code></pre>
</div>
</div>


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?

Exchange 2003 MSExchangeIS Mailbox Error Event ID 1022

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).