<div>
Hi,<br />
Did you try using LISTMAILBOXES.VBS to query whether the mailbox in question is successfuly registered or not.<br />
Go through this link if you haven't already<br />
<a href="http://msexchangeteam.com/archive/2006/03/20/422534.aspx" rel="ugc">http://msexchangeteam.com/<wbr />archive/20<wbr />06/03/20/4<wbr />22534.aspx<wbr /></a><br />
Let me know <br />
Thanks<br />
Nitin<br />

</div>


<div>
Thanks for the response. &nbsp;I did run through that link. &nbsp;Although it does return the accurate number of registered mailboxes, this seems interesting.<br />
<br />
I'm running this as a domain admin who I know has permissions to not only the mailboxes; but also the entire Exchange Server.<br />
<br />
DEBUG: The AdminURL is : <a href="http://exchsrvr/exadmin/admin/abbottspine.com/mbx/Sys" rel="ugc">http://exchsrvr/exadmin/admin/abbottspine.com/mbx/Sys</a><br />
temMailbox{1BD1BC5E-E952-4<wbr />228-A1DC-C<wbr />7968DFDB3D<wbr />E}/StoreEv<wbr />ents/Inter<wbr />nal<br />
C:\Program Files\Exchsrvr\Agents\Auto<wbr />Accept\Lis<wbr />tMailboxes<wbr />.vbs(329, 2) msxml3.dll<br />
: Access is denied.<br />
<br />

</div>


<div>
Not sure but I read some where that this worked::::<br />
<b><i>&quot;Finally - I've had another go fixing it today, and fixed my problem by uninstalling the &quot;Internet Explorer Enhanced Security&quot; from Windows 2003. Problem fixed.&quot;</i></b><br />
<br />
hope this helps you.<br />
&nbsp;<br />

</div>


<div>
Also try...<br />
-Unregister all resource mailboxes from the Agent<br />
-Uninstall the Auto Accept Agent<br />
-Delet the AutoAccept folder from Exchsrvr\Agents<br />
-Reboot the Server<br />
-Install the Auto Accept Agent<br />
-Re-register all mailboxes <br />

</div>


<div>
thank gupnit.<br />
<br />
I can at least rule out the IE Enhanced Security option. &nbsp;Uninstalling and reinstalling the AAA will have to wait until this weekend.<br />
<br />
I hate to have to do that for all of the resources since it's just one of them that is having the issue.<br />
<br />
Does anyone know how to determine what account was originally used as the trustee account? &nbsp;This was configured by a former tech and he apparently did not create a service account for it. &nbsp;I'm wondering if this particular resource might have been setup with a different account or something; but haven't found a way to examine that to be sure.
</div>


<div>
I've resolved this issue although I'm not certain what the root cause was. &nbsp;I'd be glad to award the points to someone if they can tell me how to determine the orignal trustee account associated with the AAA.<br />
<br />
I moved the broken resource mailbox to a new store, unregistered it, moved it back to the original store and re-registered it which appears to have resolved the problem.<br />
<br />
Apparently, I needed to un-register the mailbox while it was in the second store to get the situation resolved since I'd done the exact same steps while the mailbox was in the original store.<br />
<br />
I'm confused about why it works; but it is resolved now.
</div>


<div>
Great .... so unregistering and reregistering did work.<br />
Well as far as I know you can get the info from DEBUG.....thats for sure !!<br />

</div>


<div>
<div class="content wysiwyg-content">
Last night I moved several resource mailboxes which are configured with the auto accept agent to a new mailbox store.<br />
<br />
Afterwards, the auto accept agent stopped working. &nbsp;Almost all of the mailboxes are working again now that they've been rehomed in the original mailbox store; but one of the resource mailboxes is not working.<br />
<br />
I've attempted to unregister and then re-register one of the mailboxes using the registermailbox.vbs and that appears to work successfully; but it is still not processing mtg invites.<br />
<br />
I've been unable to locate any specific kb articles or message posts that might help resolve this so I was hoping someone might have some information/suggestions on what to do next.<br />

</div>
</div>


Last night I moved several resource mailboxes which are configured with the auto accept agent to a new mailbox store.

Afterwards, the auto accept agent stopped working.  Almost all of the mailboxes are working again now that they've been rehomed in the original mailbox store; but one of the resource mailboxes is not working.

I've attempted to unregister and then re-register one of the mailboxes using the registermailbox.vbs and that appears to work successfully; but it is still not processing mtg invites.

I've been unable to locate any specific kb articles or message posts that might help resolve this so I was hoping someone might have some information/suggestions on what to do next.


Move Mailbox broke auto accept agent

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.