If this is your first time using Add2Exchange or you are upgrading or migrating, post here.

5/25/2011 8:56:00 AM
Total Posts 158

Moved a mailbox from one 2007 to another 2007 server and get: An error occurred while attempting to logon to:

1. One month ago, we moved some mailboxes from the Exchange server 2007 EXTRE07 to a new server EXBRE07.   Since this migration,  the contact relationship has a problem.

2. Also when I want to create a new relationship with a mailbox on EXBE07-Y I have this error:

 An error occurred while attempting to logon to: ....

3. We now have the public folders on the EXTRE07  exchange server and mailboxes on both EXTRE07 and EXBRE07.

  Is there something to change in the configuration or should I change the license product ? 

  It is possible to keep the public folder on EXBE07-X, move all the mailboxes on EXBE07-Y and use the A2EToolBox.exe to change the Exchange server ?


First, let's answer your last questions first to get them out of the way. You can have folders anywhere you want on any server(s) if the proper permissions are applied to the A2E service account.

Make sure the following Permissions are set on the 2003,  2007 or 2010 servers:

The A2E service account is part of local administrators of any Exchange Servers so it can test to see if the store is up using WMI over RPC.  This is the issue here.

Next, be sure the following Permissions are set on just the 2007 or 2010 servers.  When you run this, make sure you run this on the Exchange Server (one with Exchange PowerShell) as an Exchange Org/admin/domain admin with rights to give the Add2Exchange Service Account the appropriate rights. http://support.diditbetter.com/kb/A2E_214.aspx

Then log off of the A2E server and back on to the server as the A2E service account 

Wait a bit for the exchange permissions to catch up to you and then try again to make the relationship again.

Important Tip, if you had an Add2Exchange or Add2Outlook relationship before you migrated the mailbox and then moved it, and did not remove the relationship before you migrated, that existing relationship would still have destination items copied there and the relationship would have gone into alert.  If you still have that relationship, it would be best to fix that relationship with the Recovery and Migration Tool to avoid any duplication.  Buy Now

If you did remove the relationship before you migrated and selected to remove the destination items, then after the permissions above are applied, you can reset the same relationship up and it will work after you give the new permissions.

If you already deleted the relationship in alert status for those mailboxes or public folders which you migrated,  resetting up the relationship will cause duplication if you recreate it, once for the old relationship and once for this relationship.

In order to fix the problem where you deleted the alerted relationship, if you know that that folder is not the source of any other relationship or is a special non default folder, you could just delete the folder or the folder contents.   This is a big IF so pay attention to the prior IF,  I would back up and then move folders rather than delete to be safe, and moving a folder within a mailbox or changing the name does not disassociate it from the relationship. Since it keys on the store and folder ID, you would have to move the folder to another store, export to PST or move it to a public folder for backup.  My personal favorite is to use the Add2Exchange Service account as the place to put all backups.  This can be done with this procedure: http://guides.diditbetter.com/a2e-guide/managing_relationships.htm


If this condition is not the case here, that you can't simply remove the folder because this folder is not the source or destination of any other relationship, you can use the A2E Toolbox, Inspector General, Surgeon General to strip the items or remove the copies from that destination automatically.  Buy Now

using this procedure: http://guides.diditbetter.com/a2e-guide/inspectorgeneral2.htm


Another big TIP These are the normal migration instructions:


To be complete, if you are migrating away from a 2003 Server and you are decommissioning it, make sure you do this:


Incidentally, we offer remote recertification services to unravel anything you can’t wait for to solve:



Hope this helps