Transaction rollbacks can happen for a variety of reasons.  This means something is preventing the system from making copies.

These can be caused by the source or destination folder is either hidden, disabled, probably not yet deleted,

or the service account is not part of the local administrators group of the exchange servers in your org

it could be the protocols for that user in exchange are disabled in EMC

the account has migrated to a new data store

and potentially we don’t have full access permission to one side or the other

or the service account doesn’t have ownership to the public folder

or the pivot folder

 one of the folders is in the process of migrating

one of the folders is replicating through Exchange Management to another mailbox or public folder server and constant replication has not been set on between those folders

there is mistakenly “per user read and unread” on a public folder or the pivot folder

We are replicating that pivot folder around incorrectly – turn that off

Any of this can cause “bad rows” in the database – so we check and remove them by running “Sanitize the db” to see from diags, tools

Older versions of Add2Exchange did not employ transaction processing.  Upgrade using this process for free if you are still under valid Software Assurance.

Once upgraded, do not open the Console, but run the process to sanitize the database first. Run this process.

Important note! If while running the sanitize db process there are any more than 0 “bad” rows in the database, please delete them all.

A big reason for transaction rollbacks are in a private to private relationship, you have the pivot folder full of items.  That folder should be empty and is safe to delete the items. It is often easy to do this with an Outlook profile to the A2E Service account.  Also with a pivot folder, Exchange could be replicating the pivot folder to another server.  Turn off Exchange pivot folder replication for that pivot folder.

Turn of “Per user read and unread” for the folder in Exchange Management Console and set the retention and age limits to 1 day for both.

Yet another reason is this could occur because there was an Exchange Migration or a new Exchange Server was added (2007 or 2010) without doing the prerequisites on the new Exchange server.  When running this utility, select the correct name of the A2E service account and select that it already exists.

If you are on Premier Support, create a ticket so we can help. 

If not on Premier and want us to recertify your replication server, below are some of the options.

• Cheapest OPTION 1: A single remote session for up to 1 hour of remote/phone support in a single session is $199.  Buy Now  
  Sessions are held by appointment during our normal business hours, weekdays between 9 am and 5 pm ET.
   
• Best Deal: OPTION 2: 4 hour block of Premier Support (remote assistance) for $399   Buy Now
  This option covers up to 4 hours of remote /phone support with one of our techs for help with your Add2Exchange installation, updates, upgrades, relationship set up, moves/ migration. There are several benefits to opting for Premier Support in this link.  Our normal business hours are weekday between 9 am and 5 pm ET, excluding holidays; sessions held by appointment.  Any time remaining after this session can be used for future remote/phone support services and any time before or after normal business hours can be scheduled at time and a half off agreement. A free license transfer when you migrate Exchange is included.  For both essential tools and 4 hours of Premier Support, click here:  Buy Now

You can purchase the support online or call in.  

Once your order is completed, open a ticket online and we'll contact you to schedule a session.  Once scheduled, call us at your session time and ask for the tech assigned to your ticket. .