we currently testing Add2Exchaneg pro. Installation was ok and GAL Sync is running. We using Exchange 2010.

Is there an way to choose what fields are synchronised ? Example: We have for all user an filled attribute "initials". This is synced to "second name" what is not the same. We can delete all initals, but this is not the right way. Or is this an german locale problem ?

Alex

You can use the Add2Outlook Toolkit change items option to fix invalid recurring appointment end dates on both source and destination sides of the relationship, with the Add2Outlook Toolkit. This routine will edit and change the end dates of recurring appointments for an entire folder to 5 or 10 years in the future, for example and use a group policy to require an end date moving forward so it doesn't happen again. See this link for a better description.  For the Add2Outlook Toolkit, this is the link and this is the link for us to fix it for you though Premier Remote Support. 

Also, if you have many relationships, (+250) combined with the above solution, we have noticed you can change the method it uses to load relationships and sync by changing the registry key for Session Sync Pass in the HKLM Software or Wow6432 Node\Software\OpenDoor Software\Add2Exchange\  to 2 instead of 3 for a full sync.

Add2Agent Process Exception.

SOURCE: Redemption.RDOAppointmentItem

MESSAGE: Error in IMAPIFolder::OpenEntry: MAPI_E_CALL_FAILED

DATA: System.Collections.ListDictionaryInternal

TARGET SITE: Add2Agent.Redemption.IRDOMail.get_Subject

STACKTRACE: Add2Outlook.Relationship.vb:line 1293

Build: 5.15.0916

This process should be done when we receive notification of departure and before account is hidden, deleted or disabled.

On Add2Outlook Contact Sync System
1. In Outlook Profile using zAdd2Outlook (typically already running)
2. Click Add-In Ribbon Selection
3. Click Stop Sync and Timer Stop
4. Right Click on Departed User’s name in the navigation pane on left side of Outlook.  Select Data File Properties -> Select Add2Outlook Tab
5. Scroll down to Contact or whatever folder type and find the relationship(s) and select it.
6. Right click on one of the user’s relationship.  Select Delete
7. Acknowledge Delete warning and put in reason.  Select to remove destination items.
8. Repeat Steps 5 through 7 for all relationships until done
9. Close the console and start the Sync from the Add ins tab or wait since the timer is set on when you drop the A2O Console. Wait for the removal of sync’d contacts from the user’s Contacts.  This may take several minutes or hours, depending on the amount of data. 
10. The remaining steps can be done when we archive/delete the user account.

When fully deleting user – After above steps are complete and Contacts are cleaned
On Contact Sync System
11. File -> Account Settings -> Change Account -> More Settings button -> Advanced Tab
12. Remove the departed user account from the list of additional mailboxes.
13. OK, Next -> Finish -> Close

Optional - On System with Primary Admin Outlook Profile
14. Open Outlook profile using Primary Admin in non-cached mode
15. Archive departed user’s to a PST using Export on specific user account
16. Name export file ‘User’_saved.
17. Move saved PST to on Exchange Exports share on server

On Office 365 Admin Login
18. Delete user account

We have found that Add2Exchange will not synchronize until a database maintenance is performed:

Event ID 2005
20140818231220: Database Maintenance Required. Add2Exchange can not synchronize until you have performed required database maintenance. The Database interface attempted to perform this maintenance but apparently failed. Please contact Tech Support. Location: AgentSynchronize | Calling program: A2ESP

For further information/support, please visit:
http://www.diditbetter.com/support

Can someone confirm how this maintenance can be performed please?

Regards,

Craig

In a full mesh, you need a public to private, private to public and private to private template attached to one distribution group.

You can make individual relationships, but it is much easier to make relationships with the relationship group manager so you can make exactly what you want with ease, instead of making one to one relationships as in Standard.  You can actually drive the relationship creation and removal by the inclusion or removal from a specially attached distribution list, named something like z_ContactSync.  The members get the kind of relationships you would attach a template to.

In this case, you have a ripple.  Some people can make them and some people can’t, but everyone needs to get copies of the items.

In the Enterprise/365 edition you will need two Distribution lists, one whose members can edit/make items and one whose members cannot.

Scenario:  One public folder to 7 people, 2 of which can edit the copied items and update everyone and the same 2 who can make new items and have them go to the Public and to the other 5.  The 5 people can make items in their privates, but they dont get copied anywhere.

In our example, let’s call the distribution lists: 
z_ContactSync_noedit  for those who cannot edit
and
z_ContactSync_Edit who can edit and make items from their folders.

Your 5 non editing people would be in the z_ContactSync_noedit.

Your two super users (older citizens) can make and edit and are in z_ContactSync_Edit.

Next we would make a few templates to attach them to:

Public to Private - non edit (unidirectional) and attach to z_ContactSync_noedit to make 5 relationships.

Public to Private  - edit and create (directional) and attach to z_ContactSync_Edit to make 2 relationships.

Private to Public - attach to z_ContactSync_Edit to make 2 relationships – anything made in the 2 users privates will go to public.

Private User 1 to 5 Users - attach to z_ContactSync_noedit to make 5 relationships  - anything made in the private 1 go to 5 users.

Private User 2 to 5 Users - attach to z_ContactSync_noedit to make 5 relationships - anything made in the private 2 go to 5 users.

Single Private User 1 - to user 2 to make 1 relationship  - anything made in user 1 goes to 2.

Single Private User 2 - to user 1 to make 1 relationship  - anything made in user 2 goes to 1.

Total of 21 relationships.

The result is user 1 and 2 can make and edit all from the public and they make items that go to the public and everyone else.

Non editing users can’t edit anything but get all contact items made in public and either private.
Anyone with editor or above Client access permissions to the public folder can edit and delete any items from the public no matter where it was made.

If this is still confusing, we include remote install and certification support in every Value Bundle so we can set up exactly the relationships you need!!

Below are some tips and links which may prove helpful:

Overview

Our Add2Exchange server-side solution is versatile – you can set it up to sync new items created in a public folder to a user’s mailbox folder or another public folder;  you can set it up to sync new items made in a user’s mailbox to a public folder or someone else’s private folder.  For more information please reference the administration guide ‘Sync Models & Concepts’ sections. For mobile device users who want to view public folders Contacts for example, you would create a public to private relationship for each user from the Exchange public folder Contacts to the user’s mailbox folder; once Add2Exchange gets the information into the personal folder, the device’s sync software takes over from there. If a user will be creating a new item on the device, or in the personal mailbox folder and you want the item to sync to the public folder and to the other users, you would create a private to public folder relationship and also a private to private relationship for each user.  When anyone makes it anywhere and it goes to everyone else, we call this a Full Mesh Sync Relationship.   

Each relationship has its own sync rules so the data can be for information purposes only or users can edit from the mobile device and it be synced back to others.  The same with deleting; it can be recopied if deleted or actually delete them all.  You can even exclude items marked ‘private’ for all folder types supporting it.   In Calendar relationships you can still block out time and replicate only a portion of the item’s details.  To help identify where the copied item came from, it is also helpful to use the automatic placement of initials in the subject of the item. 

• You can use the auto populate text feature when creating each relationship to help users identify the folder the item was created in; for example, a user’s initials, PUB or PF for public folder.
• You can use the Do Not Copy Private Items feature.  Users have a private contact (family, friends, doctors) or appointment (such as a doctor’s appt or lunch with a friend) which they don’t want synchronized to the public or each the other users.  When the user creates the contact in his personal contacts folder or appointment in his personal calendar, the user will mark the contact or appointment item ‘Private’ and it won’t sync to the public or to each of the other users.   
• One of the more popular features of Add2Exchange Enterprise/365 is the ability to setup Active Directory Distribution Groups and create relationship templates to the Active Directory group. Adding new relationships is done by adding users to the distribution group. The next time Add2Exchange syncs, it creates each relationship and can even create new folders for you, if necessary. You can find additional information regarding this in the Add2Exchange Guide under Relationship Group Manager.  Group relationships allow you to manage large number of relationships on an on-going basis through relationship templates and distribution lists.
• CONTACTS Edition: Unidirectional GAL Sync. Another benefit of the Add2Exchange Enterprise Contacts is the automatic replication of the Global Address List. There is no need to export and import the Active Directory list anymore as was necessary with our retired Standard edition. Add2Exchange Enterprise takes care it for you automatically. Just set it and forget it! Global Address List synchronization allows you to treat Outlook’s Global Address List as the source of a relationship, to be synchronized with one or more destinations. GAL Sync Relationships & Initializing GAL Sync

Every source to destination combination (folder pair) equals 1 relationship; the source is the folder new items are made in and the destination is the folder you want it to sync to.  Once installed and set up, the solution works automatically in the background based on the settings and process intervals you selected during the installation.

Helpful Topic: Product Guide includes prerequisites, system requirements and guided install steps.

• Top 10 Do’s and Don’ts
• Best Practices
• Planning Calendar Relationships
• Planning Contact Relationships
• Triggers and Responses – how you want edits and deletes treated for each relationship.
• Recommended Settings for Relationships & Relationship Fundamentals
• Relationship Group Manager – Add2Exchange Enterprise/365 feature.
• Folder Grouping/Full Mesh – all users will have same info and a copy comes and goes into the public folder.
• Do Not Copy Private Items feature
• Confidentiality Module for Calendars
• Avoiding Duplication
• Processing Interval - for specifying how often Add2Exchange syncs relationships & common values.   

Please make sure you have updated to the latest version of Add2Exchange, which is free if you are within your software assurance period.

Follow this procedure:  http://support.diditbetter.com/kb/A2E_194.aspx

If this does not fix the issue, please submit a request here: http://support.diditbetter.com/support-request.aspx

If you are on Premier Support, we will schedule a remote "looksee" and recertify your machine or you may want to Escalate if you are not yet on Premier:

http://support.diditbetter.com/premium-support.aspx

hope this helps!

The behavior we are seeing is that contacts will appear one day and they will be gone the next, however, they will remain on other devices.  I tend to think this is due to an implementation of BB's ActiveSync, however, I wanted to see if anyone has observed similar behaviour.

Thank you.

Thank you for your response.  I've confirmed that the service account has the appropriate access to the mailbox account, unfortunately I'm continuing to get these messages in the eventlog and the specific user is not getting sync'd

did you run the preinstaller on the exchange server?

go to full mailbox access in EMC and remove the service account and re-add it and try again please.

It is unable to log into the mailbox to create the relationship for that user.  Is the user hidden from the GAL?

We are currently running with the following environment:

Exchange 2007

Add2Exchange 15.5.1565

I've enabled the extended logging on the server in order to better diagnose the issue and have routinely come across the following errors:

"Maintain Relationship Splitting Destination Folder Error

A2ERelMgrPgm v15.5.1565"

"Failed Get Session's Primary Exchange Mailbox for User: <User>@<Domain> trying to resolve: Contacts,2| in routine: splitLogic

A2ERelMgrPgm v15.5.1565"

"Load Group Membership <Lastname>, <FirstName> Confirmation Failed To Get Default Exchange Mailbox via <User>@<Domain> In Order To Update Source/Destination Folders Mailbox."

Any assistance would be greatly appreciated.

Thank you,

Todd.

Run-time error "-2147221219 (8004011d)":

[Collaboration Data Objects - 

[MAPI_E_FAILONEPROVIDER(8004011D)]]

Solution:

This typically means that there are no public folders.

1. Make a public folder database and make one folder in it.  
2. Then run C:\Program Files\Microsoft\Exchange Server\V14\Scripts where C: is the installation drive for Exchange on your system.
3. Once the path is modified, log off and back on for it to take effect.
4. Open the Exchange Management Shell and execute:

AddUsersToPfRecursive-TopPublicFolder"\"-User"zAdd2Exchange"-Permissions"Owner" - replace your service account name with zAdd2Exchange

Note: the script emits an error for the root folder.  This is normal.  The rest of the folders will still receive the necessary permissions.

5. Remake the relationship.

If the deleted source folder is a public folder, usually you can just restore the public folder from Recover deleted items and then run the Recovery and Migration Manager Tool (RMM) to repoint the Add2Exchange Relationships to the recovered source folder.

Open Outlook as the Add2Exchange service account

Select option to Recover Deleted items from Customize (right click top bar, Customize Quick access Toolbar, show all commands, select Recover Deleted Items)

Run Recovery and Migration Manager tool (RMM) on the replication server. http://www.diditbetter.com/a2e-rmm.aspx

However if the deleted folder is a private mailbox folder, it could have been deleted and is still under the Deleted Items.  Restore it (move, don’t copy) and run Recovery and Migration Manager.

Occasionally the folder which was deleted was a public and when restored it is empty.

At this point a restore of a backup and run of RMM would fix it.

If a backup is unavailable, and if the replicated items are still replicated to a destination, we could use that as the source with the use of some tools. As long as it is not involved in a full mesh relationship (and is only one way) you could take the replicated data and “fix” it so it can become the source data. 

If the items are all within a destination and not the default folder, chances are all the items in the folder are the missing items. This process will outline how to make a copy of the folder, “sanitize it”.  In this case sanitize means we will be removing any original items created in that folder by the user (not the copies from the source), remove any source Add2Exchange items (if this is a source of another relationship) and only having the destination items remain. 

Note: this will not work on a full mesh relationship.

Once this process is done, you can use the contents of the folder to be copied to the original source folder and then start syncing again. 

Use Outlook logged in as the service account – not OWA

Open the users mailbox with the destination folder we will fix and make an original.

If the recovered folder is empty, or incomplete, make it empty so when we fix the relationships with Recovery and Migration Manager to that recovered folder, it will remove all the old destination items.  Make sure the relationships are set so source item deleted is to delete destination items.

Fix the existing relationships and remove destination items

Run Recovery and Migration Tool and fix the relationships 

Let Sync, which will remove the old copied items

Optional: Removing Autoplace Text in the destination items

If you used the autoplace text in the copy process, we will need to strip that off with the Add2Outlook Toolbox

Go to an Outlook machine as the Service account – not owa

Close Outlook

Download and extract the zip file.  Right click and Install the Full A2Otoolbox as administrator

Open it

Open profile

License it

Select change items

Select the folder

Type in the find text

Be sure to use a space after the autopop, like FC:  (FC colon space)

Do not put any replacement text

Select go, do it now, not on timer

It will remove all Autoplace text

Now to “Fix” the copied folder of items to become originals

Next, on the replication server, logged in as the zadd2exchange service account, open the Blue army knife called the Add2Exchange Toolkit

Make sure it is licensed

Select Inspector General from Free side

Pick the folder within the service account mailbox

Go to the Surgeon General

Unlock

Select the checkboxes for A2E copy = T and Remove NP (not delete)

This makes the items originals

When Add2Exchange is done replicating, it should have removed all the destination items from the prior sync

Stop Add2Exchange Service

Copy all the items to the empty public folder

Start sync

This process made the copies originals, removed the autoplace text, repaired the relationships and will resync.

My holidays do not seem to be syncing to my calendar.  What can I do to fix this problem?

Answer:

Outlook has the ability to automatically add holidays to a calendar, with the calendar entries categorized with the default category of “Holidays” and those depend on the region selected. 

In order to avoid duplication for private to private relationships, we automatically exclude any appointment with the category “Holiday” from the replication process.

To enable these appointments to replicate, either remove the default category or create a custom category such as "Our Holidays" and it will replicate.

Applies to Add2Outlook, Add2Exchange Standard and Add2Exchange Enterprise edition

It is also possible on the Exchange Server that the MS Exchange System Attendant service was not started.  This could cause a failure to log on during console startup.

Another possibility may be that the account is actually locked, in which case you would want to unlock it from the Active Directory.

The issue got resolved once the server is rebooted.

Regards

Dhanushka

One of our client is running A2E Standard on SBS 2008 running Exchange 2007.We are unable to open the A2E console and getting the following error messages

Error-01

Add2Exchange AgentDirector failed to logon

Error-02

An error occurred while attempting to logon to:
Exchange Server: SH-SBS01
Mailbox: ZADD2EXCHANGE

Please verify that the account is valid and has the appropriate permissions.

Description:  [Collaboration Data Objects - [E_OUTOFMEMORY(8007000E)]]
Number: -2147024882
Location: 1
Build: 8.3.163

We followed the following KB and there is no issue with the password or the user name of zadd2exchange user.

http://support.diditbetter.com/kb/a2e_218.aspx

When we check for the registry key "HKEY_LOCAL_MACHINE/Software/Microsoft/Windows Messaging Subsystem" there is no sub key called  "Windows messaging subsystem".

Any help in resolving this issue is greatly appericiated.

Thanks

Dhanushka

When an appointment is created in the Public Folder, and invites are added, the responses are not tallied because the Public Folder doesn't have the (free busy connector) Exchange functionality to up[date itself properly when the users accept.

Solution:

This type of process is an Exchange based synchronization for meeting attendees.  That functionality is available from your own Outlook calendar, but not from the Public when an item is changed.  Outlook also warns you when saving that the responses to this meeting will not be tallied, so if it does change, it becomes unconnected to the time changes.  And because of the relationships we have in Add2Exchange, it may copy it back to the original time and date because of the type of synchronization with the two principals.

This problem only happens when you change the original time and date of that meeting from the Public.  Your current method will work fine if you don't make any changes to the appointment as far as time and date, but you can edit the details though.

However if the appointment changes, and replication has occurred, then the update might revert back to the original time and date.

This is causing an issue.  Because of such, we need to change the procedure for any appointments in which a change is made to the time and date when they were made in the Public and invited to other users.

The best practice on a time and date change of an appointment is to edit the subject and mark it "Canceled" or "Rescheduled to [date]" and then make another one at the new time and invite again.  This way the original appointments get replicate out to others with the words in the subject noting it has been canceled or moved.  If you just delete the appointment, you run the risk of someone saying the appointment was there and somehow disappeared; not knowing when it was rescheduled to.

If the appointment was rescheduled, create the new appointment in the Public Folder at that time and invite the same people using the new time.

This process ensures that everyone knows the status of a meeting, will avoid missing appointments, etc.

Adding users of course adds to the time it takes to replicate.

For Add2Outlook, it is best to add all the users at once.  

For Add2Exchange , it doesn't matter.  You can add and remove at will for nominal changes.

To be able to tell how long it will take after a sync, we would look at utility in the console for sync interval and make note of the time.

We don't recommend any time less than 10 minutes, because it will always be syncing and users may not have enough time to open it and save changes.

From there we would then go into the Add2Exchange Event Log and look at the success logs to see the time it takes for the folder type to sync.  The value and the sync intervals is at least how long it takes to replicate.

If it is busy syncing contacts, for example, and it is time for Calendars, it will queue up next when Contacts is done.

Both programs do the syncing sequentially, and it is not immediate, in order to take into account any changes.

If you open the Console or stop the service, syncing stops where it is.  When you start it again, it will then restart over.

We have an appointment on a personal calendar that will not sync to the group calendar.

Also, it seems slower now synching than it did in the past.

Answer:

If it is a tentative appointment, as an invite, it will not sync unless it has been accepted.

These messages will appear in the log:

A2ESP Replicate Due Message Replied Tentative Acceptance Status

After May 2012, no release will replicate tentative appointments.  This is a major upgrade.  We had found that users who got copies of tentative appointments and subsequently refused them would in certain circumstances, delete the original.  Upgrading to the current version creates these normal informational warnings in the Add2Exchange Event log.  They are normal.

We know that some users are relying on this functionality, and this is a major change. We feel this is a security breach and hole in the proper functioning of the product, going around the rules of replication, so this functionality is now core functionality in all the product line.

Accept the appointment and it will sync if the start date is within the recurring item date (Global Options) or within the timeframe prior and post of the relationship.

If it still doesn’t sync, recreate it and see if it does

If it does, then that non replicating item was probably a copy, and copies don't sync.

….. Or

it could be a recurring appointment outside the range of the recurring items setting in the program

http://guides.diditbetter.com/a2e-guide/recurring_appointments.htm?zoom_highlightsub=recurring

This may be relevant, but substitute Calendars for Contacts - Items missing

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=1&thread=69

Turn on Full sync on the phone:

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=1&thread=132&postid=262

As for the Slow replication:

http://support.diditbetter.com/Forums/Thread.aspx?pageid=1&mid=2&ItemID=1&thread=71&postid=182

Other less specific references but possible issues with devices and versions of software you are using to create the items.

http://www.slipstick.com/outlook/2007/outlook-2007-known-issues/#cal

http://www.networkworld.com/community/blog/exchange-outlook-calendaring-problems-lost-me

Holidays are not syncing:

http://support.diditbetter.com/Forums/Thread.aspx?thread=195&mid=2&pageid=1&ItemID=1&pagenumber=1#post389

Cheers!

 I set the prior days to 60 to include the start date of the source recurring meeting and it seems to have cleared the destination of the individual deleted occurrences

Thanks for the help

for some reason, it is not being seen as a recurring appointment

set one back and see after a sync success

...the number of days screen is for Enterprise Edition

Synch range for relationship is 365 forward, 7 days prior. I wondered if the original being outside this window had an affect?

Also, Is there a reason I don't see number of days on the global option, as shown in the guide? Or has that changed?

was that recurring appointment made in 2003 or 2007 outlook?

These are sometimes not made correctly and are misrepresented in Exchange

what is your prior date set to in the relationship

if this is the case, the appointment in question may be considered a normal appointment

in error

so you may have to set the prior days to 60 in each calendar rel and it will replicate the instance deletion

There is no option for number of days as shown in the guide. My online help shows the same thing. I thought we were fairly up to date - did that change in a recent version?

We have the default setting - Copy recurring items every synch cycle regardless of reminders.

Recurring reminder in question started on 12/10/12 through 2/1/2013 every m w f

But still don't see answer to this question: If a single event in a recurring cycle is deleted on the master, should that specific single occurrence also be deleted on the slave calendars?

Is it supported or not?

thx

The best practice is not to set recurring items up with no end date.  That way if you ever end the pattern, it does not lose the exceptions.

It is also possible you have the non default setting in the link. Set a recurring appointment to span a year and then make another one next year, that way

you do not have to set the window for years and years in the past.

Hope this helps

The recurrence series syncs successfully. But when a specific occurrence in the series is deleted on the master, that deletion does not happen on the other users calendars - the deleted occurrence remains on the destination calendar

Prior days set to 7

Delete in source = delete in destination

The recurring meeting start date was farther back than the 7 day sync period.

The recurring meetings on the destination do show the recurrence and the original start date is shown for the meeting.

Any ideas? This is a bit frustrating to the users.

thx

v 9.9 on win 2008 R2 enterprise

CDO for Exchange 2003 is included with Exchange System Manager.  The best route to fix it is to reinstall ESM from the distribution media.

If you don't have the media available, the next best option is to run the a2ediags, which are included in the Add2Exchange download as a zip file.  Extract the zip, then run A2EDiags.bat.  In the menu that presents itself, first double-click "Unregister CDO", which will run and may report nothing done if Outlook 2003 was successfully uninstalled.  Then double-click "Register CDO".  Try Add2Exchange again after that completes.

If that doesn't work, the last option is to reinstall a newer version of CDO.  We prefer that you try this last because as a rule of thumb, compatibility is usually best with the version of CDO which comes with your Exchange.  In fact, I can't remember whether the latest version of CDO will allow you to install with 2003, but it's worth trying if the other measures haven't worked.  You can find the file ExchangeMapiCdo.msi in the preinstaller folder of the Add2Exchange download.  Run it and try Add2Exchange again after.

We recently installed Outlook 2003 on our exchange server, which also has our add2exchange software installed.

We then noticed that this was causing an issue with the syncing of the mobile devices through add2exchange and uninstalled this software, but now we are unable to get into the console to partner up the users on this console. We looked into it and it mentions that we have to reregister the CDO, it gave no instructions on how to do this so we re-installed the following software on the server: http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en

We now get the following error when trying to get into the control panel:

An error occurred while attempting to logon to:

Exchange server: .....

Mailbox: .....

Please verify that the account os valid and has the appropriate permissions.

Description: [Collaboration Data Objects - [MAPI_E_LOGON_FAILED(80040111)]]

Number: -2147221231

Location: 5

Build: 9.7.175

We run through the permissions again on the account and they are all still present.

the WMI Provider Host jumps to 50% cpu and stays there. If I stop the Add2Exchange service everything calms down and returns to normal. 

Please Help.

what version are you currently running?  email me direct  Tc@diditbetter.com

Any word on this issue yet?

Cheers

I have noticed that this event appears each time a sync cycle is initiated. Is this anything to worry about?

We are running Add2Exchange Enterprise on a SBS2011 Standard server. This is a brand new server that has just been migrated from SBS 2003. Add2Exchange was not migrated and was freshly installed and configured on the new server.

The Add2Exchange version is current as of 2 weeks ago.

Here is a dump of the log file (Please note that instances of the server name and internal domain name have been supplemented with %Server% and %Internaldomain%). Please note that the name of the service account we have used for Add2Exchange is Za2eadmin

Any help you can give to explain or clear this warning is much appreciated.

=============================================================================================================

Log Name:      Application
Source:        Microsoft-Windows-RPC-Events
Date:          20/07/2012 1:28:31 a.m.
Event ID:      11
Task Category: None
Level:         Warning
Keywords:     
User:          %Internaldomain%\za2eadmin
Computer:      %Server%.%Internaldomain.local%
Description:
Possible Memory Leak.  Application ("C:\Program Files (x86)\OpenDoor Software®\Add2Exchange\Service\A2ERelMgrPgm.exe" %Server%:12071941:ZA2EADMIN:12:58:16:7) (PID: 32036) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)].  [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked.  The call originated on the interface with UUID ({f5cc5a18-4264-101a-8c59-08002b2f8426}), Method number (5).  User Action: Contact your application vendor for an updated version of the application.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-RPC-Events" Guid="{F4AED7C7-A898-4627-B053-44A7CAA12FCD}" />
    <EventID>11</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-19T13:28:31.613608700Z" />
    <EventRecordID>37662</EventRecordID>
    <Correlation />
    <Execution ProcessID="32036" ThreadID="46716" />
    <Channel>Application</Channel>
    <Computer>%Server%.%Internaldomain.local%</Computer>
    <Security UserID="S-1-5-21-2611932659-3821166724-1123600170-1194" />
  </System>
  <EventData>
    <Data Name="ApplicationName">"C:\Program Files (x86)\OpenDoor Software®\Add2Exchange\Service\A2ERelMgrPgm.exe" %Server%:12071941:ZA2EADMIN:12:58:16:7</Data>
    <Data Name="ProcessId">32036</Data>
    <Data Name="InterfaceId">{F5CC5A18-4264-101A-8C59-08002B2F8426}</Data>
    <Data Name="Method">5</Data>
  </EventData>
</Event>

=============================================================================================================

We're running a trial of Add2Exchange Enterprise. I've managed to successfully create GAL syncing to a Public cache, and then several individual relationships. They sync fine. What I can't seem to get working, is a GAL sync to a distribution group through the Group Manager. Here's what I've done:

Created a Contact Template set as a GAL relationship to sync to the Contacts.

Attached the template to a Distribution Group and applied.

When I exit the Group Manager, it doesn't seem to create the individual relationships as I understand it should.

Any ideas what would cause this?

After the upgrade, and a sync, do you still have the issue?   If so, try the above and if still an issue, please submit this so we can contact you directly and make a recommendation.  Sorry for the delay.

http://support.diditbetter.com/support-request.aspx

I have a strange problem where changes that I have made to distribution groups in RGM have resulted in duplicated names of groups and blank entries in the dropdown list. Here is a link to a screenshot I have taken of it.

http://img191.imageshack.us/img191/8100/rgmq.jpg

Is there some way I can clean this list up?

I upgraded to the latest version successfully lastnight (From 13.11.962.340) but it has not helped.

Kind Regards,

Brendon

Sorry for the late response. I was out of the office yesterday.

did you update to latest?

Also, extract and open the a2ediags.bat

and unregister cdo and reregister cdo

Be sure to use the tip to move the MMP files to a place where you can exclude them.

Then stop the A2E service, open the A2E Toolbox and from the free side, select minimize DB footprint.  It will throttle your sql memory usage for our instance to 100 MB.  Then reboot, probably, or close the Toolbox and just try to open the A2E console again.

I would be happy to a principal investigation for you.

Start here please http://support.diditbetter.com/support-request.aspx

If you are on Premier Support, we can log in remotely. If not, these are some guaranteed results options we can do immediately: http://support.diditbetter.com/premium-support.aspx

We use this technology to remote in without you giving us any login information: http://support.diditbetter.com/kb/a2e_164.aspx

also, we are on 9.4 now, and I am wondering why it has to create indexes, those should already have been applied in a new install

The version of A2E we are running is a fresh install of Version 9.2.153.  That being the case, is running the Sanitize DB routing still recommended?

 After upgrading from "4x, 5x or 6x" versions of Add2Exchange to the latest release, you should run this test. This test will solve a particular kind of issue where items don’t replicate to one (or more than one) user in the Add2Exchange Event Log, there are errors about "transaction rollbacks". http://support.diditbetter.com/kb/A2E_183.aspx - This also solves the case of creating indexes.  For these older version upgrades, you must first upgrade to the latest edition of Add2Exchange and then before (or if it doesn't open) opening up the Add2Exchange Console, run this procedure above.

[FROM HERE: http://support.diditbetter.com/kb/a2e_219.aspx]

AND then open the A2E Console again.  It should open.

IF you have any bad rows in the database, before the next synchronization, edit each relationship once in the A2E Console so that "destination item deleted" is set to recopy.  Then after a full sync, you can change it back.  If you wish, we can do it as per an incident and recertify your box  http://support.diditbetter.com/premium-support.aspx

Hope this helps

I ran into this very same with htis software whne it was installed on another server, which let to us installing the software on it's current server.

Any assistance would be greatly appreciated.

The best way to make sure a sync isn't running is to stop the Add2Exchange service prior to emptying the folder.

Best syncing,

Ted

For more information on how Add2Exchange works as an overview, see this link

Quick Steps to Off boarding users with Add2Exchange Relationships:

Tips:
Enable the account and Unhide the account from the GAL
In the Add2Exchange Console, delete any single rels and select to remove destination items
Remove users from distribution lists in Exchange, not from within the RGM (by checking and unchecking users)
Make sure Services Utility has Relman and that folder type set to some nonzero timeframe.
If you have already detached the mailbox, you could attach the mailbox again or accept the orphan copies.

Close the A2E Console and run a sync
Then you can follow your normal account termination process.

Discussion of Off boarding users with Information Sync Relationships:

Using Enterprise Edition and Relationship Group Manager (RGM):  Remove the user from the distribution group that the Add2Exchange Template (Enterprise) is attached to, and do not hide delete or detach the mailbox so the program can detect the user is not there, and successfully remove the relationship and the data it copied to or from that mailbox.

If using RGM, make sure in the Console, Select Services, Utility and make sure Relman is set ON to usually, once a Day.  Close the Add2Exchange Console and Restart the Add2exchange Service.

If using the Enterprise edition (or Standard edition)  with single relationships - go into the Add2Exchange Console and right click and select Delete for any of the single relationships to or from the user and select to remove destination items. 

Close the Console and start the Add2Exchange service when prompted. 
Wait until a success audit in the Event log shows for Relman, and one success for that folder type of relationship being removed, such as Calendars or Contacts.  There should be event log entries for what happened when removing the relationship.  Open the A2E Console and it should have removed the relationship(s).

Then, after the user no longer has relationships,  you can do whatever you want to the account.

Exceptions:
If Relationship is in alert, or if you don’t have the mailbox or account anymore  - or have done more than just disabled or hidden the account.

For those relationships to or from that account you have in alert and potentially in the trash, you can either:

Accept that A2E won’t cleanup – potentially leaving orphan items in the destination if that account was a source folder, or
Attempt to have Add2Exchange cleanup, if the mailboxes are still there and is possible and preferable to unhide the account for that brief cleanup period.

To Accept that A2E won' cleanup: Open the Add2Exchange Console, Go to Global Options, select "Empty Trash" and close the A2E Console and restart the service.
To attempt to have Add2Exchange cleanup: Make sure the accounts are accessible and run the Recovery and Migration Manager tool to try to fix the alerted relationships

If it is important for the destination items are to be removed, these orphans can be removed with the A2OToolkit.  Special Care should be used in using this tool.

If you have already deleted the account, and it was only a destination of a relationship, then you can force delete the alerted relationship and select to Empty the trash from the Add2Exchange Console Global options.  Doing this repeatedly will still have a stable system, but will create unnecessary data in the database, slowing sync times.

The best way to “terminate”  a user with an Add2Exchange Relationship

If you created clone relationships using RGM, and there are templates attached to a distribution list, JUST BY removing the user from the Distribution list(s) to which you attached the RGM Template in Enterprise Edition, this will remove the relationships and items copied.

If there are single relationships, they have to be removed from the Add2Exchange Console.

Log on as your admin to AD and Exchange
For the account in question, Set log on restrictions if desired
Change the password for the termed user
Remove the user from the managed distribution list Add2Exchange is making a template

Do not at this point hide the user from the Global Address List (GAL) – wait until Add2Exchange can “clean up” and remove destination copies and then after a success audit, for Add2Exchange, you can hide the account and do what you wish to it.   Wait for a full success audit for Calendar or Contacts.
Then log in the replication server (where Add2Exchange is installed) as the Add2Exchange Service Account.
Open the Add2Exchange Console and see if there are any single relationships for that user.  If so, select to right click and delete them.

TIP:  if the account you are deactivating had a relationship which was a source folder being copied to others, this is essential to remove destination items and desync so as not to create “Orphan Items”, or those which will never be updated again.

If there are single relationships made and they are not in alert, for either Standard Edition or Enterprise Edition, delete the relationships and select to remove the destination items and let a full sync occur before hiding or tombstoning the account.  Look for success audits in the Add2Exchange log before continuing to off board the user.

If there are templates attached to a distribution list, JUST BY removing the user from the Distribution list(s) to which you attached the RGM Template from Enterprise Edition will remove the relationships next time Relman Runs.
Restart the Add2Exchange Service to remove them. If the relationships are in alert, and they were hidden from the gal and you have unhidden them, you can delete them and select to remove the destination items and it should proceed to dereplicate correctly.

If the relationships are in alert and they were not hidden, but the accounts are deleted, you have to delete the alerted relationship and select to remove destination items, even though the system probably can't, and you would select Empty Trash.  

Then, after the Add2Exchange Full Sync/desync for that folder type, in the user’s folder will be only the source items which you may wish to move to another user or public folder so they can again become part of an active sync relationship and be synced again.  Then you can proceed to your normal off boarding process with delete or archive or hide the account from the GAL.

TIP: Make sure Add2Exchange has Success Audit logging on in the Add2Exchange Console.  To set this, log on as the A2E Service account, open the Add2Exchange Console, go to Services Utility and set Logging to Start and Stop.  That way you can tell in the Add2Exchange Event log  when it completes a full sync for that folder type. Then restart the Add2Exchange Service to kick off a full sync/desync.

General Questions Answered

If your installation is Add2Exchange Enterprise you may have both single relationships made to or from the account you are disabling or you may have a Relationship Group Manager Template relationship made.  Templates are made by including and removed by excluding from a distribution list, so removing the users from the Distribution list will automatically remove the relationship. Since the Template relationship specifies what you would like to do if the user is removed from the distribution list, editing the Template  and reviewing the second to the last tab – what to do when removed – would be good.  Normally it is remove destination copies. See the help on that page for more informational advice. 

If you have single relationships to that termed or near termed account, delete the relationships and select to remove destination items from the destination folders so it does not leave any ORPHAN copies there. If you are using the Relationship Group Manager templating system, where the relationship template is attached to a distribution group, be sure to remove the distribution groups from the user’s “Members of” before the account is being hidden from the GAL, and then cycle the Add2Exchange Service to allow for the clean-up.  After a full success audit in the log, you will see the relationship will be gone. 

TIP: If it is still there, and in alert, and the account is not hidden and still has a mailbox, and the account is part of a source relationship, where the folder within the mailbox is a source of any relationship, proper operation would be to license and run the Recovery and Migration Manager Tool to fix the relationship first so it can clean up any orphans automatically.  Cleaning up afterwards is harder to do with many relationships.  If this is your case, send a support request and consider Premier Support to assist and train on best practices.  http://support.diditbetter.com/support-request.aspx

Recovery and Migration Manager Tool          Buy Now

Add2Exchange/Add2Outlook ToolKit            Buy Now

If it is there already, it will use that folder to any new user you add to the distribution list. 

If the folder is there already, it will populate, but be careful not to step on people’s existing folders

If the folder was there, and was deleted, however, it will not REMAKE the folder if it is deleted, it will put the relationship in alert.

The easiest option in that case, If that folder is ONLY a destination folder, then you can uncheck the user in RGM, run full sync, set the Empty Trash option on in Global options, close the console, run the sync and then recheck after the full sync and the folder will be remade and repopulated.

If the folder was both a source and destination folder, recover the folder if possible and then run the Recovery and Migration Manager Tool  to fix the relationships.

Hope this helps

if they manually copied them there already, there would be duplicates after the sync.

If using Enterprise edition and Relationship Group Manager, many people create a separate distribution list

which will be set to the default folder, then attach the new template to the new distribution list.  Be sure not to put the same people in both.

That way if your devices don't support it, you can add them to that list.

Does this help?

In your case, you would make a GAL Sync relationship to that user's regular Contacts folder.  The user would receive all of the new GAL contacts in that folder while still retaining the existing contacts he already had.  Add2Exchange will simply ignore those contacts.

Ted

to perform a GAL sync to a user's primary contacts folder and not affect their personal contacts?

If some of the items appear and some don't on the smartphone, you will have to set the settings on the Smartphone  to sync farther in the past.

For an IPhone, go to Settings, Mail Contacts and Calendar Settings, then go to the bottom for Calendar settings.

Set the Calendar Sync Setting to All items.  The default setting is 1 month, I believe.

This is important because if the item not appearing is a recurring item, or an edited instance of a recurring appointment, the phone must be set to sync the first instance of the recurring appointment.  

Also be sure to check this setting in Add2Exchange to make sure you are syncing recurring appointments ever time:  http://guides.diditbetter.com/a2e-guide/recurring_appointments.htm?zoom_highlightsub=recurring. 

Tip: Be careful not to activate Default Recurring appointment  replication on unidirectional private to private relationships because the source users reminders will be rereplicated to the destination every sync cycle without the ability to turn them off.

Hope this helps.

One event won't sync over to both users ipads. It showed up in outlook but not on their third party device. I want to know if this could be related to Add2Exchange. They have Level 5 support that could be used if necessary to resolve.

Stop the Add2Exchange Services before the backup.  Use the link below,

or use NET STOP Add2Exchange Service or if on another machine SC NET STOP Add2Exchange Service.

http://guides.diditbetter.com/a2e-guide/stopping_the_add2exchange_service_during_backup.htm?zoom_highlightsub=stopping

Use any file system software to back the installed directory (by default – C:\Program Files\OpenDoor Software®)

If you need to restore Add2Exchange for any reason, you should call in and let us assist to avoid duplication.

Since the Add2Exchange database contains metadata about the information in Exchange, restoring the database may create duplication if it runs again after the restore.

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. .

It can also accidentally be caused by users who have a smartphone which loses the profile and when they are prompted to save what is on the phone or what is on the server, they almost always say save what is on the phone. If the profile is lost, it is an empty profile, and it overwrites (deletes) everything on the server, and then A2E correctly removes the source items.

First, please be sure to have the most up to date version of Add2Exchange installed on your system. You may be able to get the update for free if you have valid software under the software subscription you have in place. Use this procedure to upgrade: http://support.diditbetter.com/kb/a2e_219.aspx

I would suggest in the meantime, while you figure out if there is a political reason this happened, to change your relationships so that if the destination item was deleted, to recopy, at least temporarily.  We suggest if they are going to delete an appointment, to put “Cancelled” or “Reschedule until [date]” in the subject of the source so multiple users can follow along.

To fix this [Deleted] tag, we have a tool. You must install the Add2Outlook Toolkit program on an Outlook machine with the A2E Service Account profile.  It is available from the Downloads section of the Website under the Add2Outlook Section called Add2Outlook ToolKit Full Installation v xxxxxx.xxx. (whatever version). Copy it over to a workstation, install, and make a profile for the service account.  Buy Now

Then run the Add2Outlook Toolkit. Pick the A2E service account outlook profile you created, pick the source folder and see below.

The A2O TooKit has a trial, and you are welcome to use it, and it costs $250 to license.  It has some other functions you may want to use as well, so we make it available at a discount (125) to Premier Support members.

BTW, since you are not on Premier Support or have an incident, might we offer to fix this for you for this and any support in the future?   I believe you have the options quoted to you. 

If you are on Premier, we will log in, survey then entire situation, use the tool and recertify your machine.  We can often tell who did the deed.  To find out who did it, in Outlook, open the users mailbox from the Add2Exchange Service account Outlook profile. Look in the deleted items of the users and find out the earliest deleted calendar with the most items on or near that time.  The earliest person’s account is the culprit.

The Add2Outlook ToolKit must be installed on an outlook machine

With a profile available to the A2E service account

To fix

Back up your source folder

Then install and run the add2outlook toolkit

And you will do Change Item function

Then pick the folder

Then put in the find text “Deleted” and replace with nothing

Then process Items. 

Then after a successful process, close that program.  Then go back to the replication server and close the Add2Exchange Console and restart the Add2Exchange service when prompted.  After the next sync, all the items will repopulate without the {Deleted} tag.

Let us know if we can be of service by using this link: /support-request.aspx

First, you will have to manage this software with the Add2Exchange Service account, and no other account. The default name is "zadd2exchange" but yours may be different. Always use this account when logging in, and manipulating the Add2Exchange Console. Do not create shortcut links to desktops of other accounts like Domain admins, your account or the administrator account.

Please read the entire post so you can figure out exactly what the problem is before you do anything to modify the current status. Identifying which applies to you before you change anything will allow you to have the answer to why is it not syncing.

This link gives a more detailed explanation of what to expect HOW ADD2EXCHANGE WORKS.

Review The Add2Exchange Event Log for the specific Errors and communicate them to the support team
Either reply to your existing open incident or Open a Ticket for DidItBetter Support.

If using GAL Sync or Contact Sync or Calendar Sync, please see this important tip re group policy.

Users will report one of the following. Sync failures fall into several categories:

• Nothing is syncing. Check event log for specific errors
• End User reported no items syncing for a particular user:  Check to see if there is a relationship for that user, check to see if included in an Add2Exchange managed distribution list  - check permissions.
• Item is not changed if the tied item is changed and or it reverts back - Open Add2Exchange Console and review THAT relationship settings - Set Copied Resolution to Sync changes back to Source and set Conflict resolution to Always update Source if that is appropriate.
• The item is not being removed if the tied item is removed - Open Add2Exchange Console and review THAT relationship settings  - change to relationship settings - Delete Destination item set to Delete Source if appropriate?  [Be careful on that option]
• The item IS not copied to the destination, either the first time or subsequent times. - Change to relationship settings - set Delete Destination copy to Recopy instead of "Do Nothing"? if appropriate.
• The item is actually a copy from another relationship. - A2E will not copy a copy and you may need more relationships to go from the original source to the desired destination. See this link.
• The Source items now all have "Deleted" in the subject. Download and license Add2Outlook Toolbox. Relationship setting was set so Destination item deleted to mark Source item Deleted. - Change to relationship settings - set Delete Destination copy to Recopy or "Do Nothing" (don’t recopy if deleted).  Contact Tech Support for Premier assistance.
• Replicated Source or Destination Items are disappearing - Check the relationships, they may be too strong - Set Destination Item Deleted to Recopy instead of Delete Source? if appropriate.
• An item looks correct in the source or destination folders in Outlook, Entourage or OWA, but not on the phone, this is a phone setting. Go to Calendars setting on the phone and select to sync ALL items. On some phones you have to disable the Calendar sync in Settings and then enable again.
• Absolutely nothing is syncing or system is stopping - Check to see Event log for recent Activity. 

Things which will make the service stop syncing.

Doing updates and not rebooting after
Opening A2E Console
Stopping the A2E Service
Closing the A2E Console and selecting when prompted to log off
Logging off if not able to
Not allowing auto logging on after a reboot
Changing the password
Enabling UAC
Applying particular Group Policies  applied to this machine
Lack of Antivirus exclusions
Migrating versions of exchange without recertification

STEPS to Identify and remediate most issues

The most common reason for Synchronization inconsistency is because the Add2exchange Service is not started.  Look to the Add2Exchange Event log and note errors. Follow suggestions or follow web links to resolve.

Add2Exchange syncs as a service, but sometimes in some environments, the sync account cannot be logged off of the replication machine.   Add2Exchange Sync to some Exchange 2013, 2016 or Office 365, (with Outlook installed) the sync service account has to be logged in for it to replicate.  It can be locked, the service should be running and Outlook does not have to be open.   Add2Exchange still operates as a service, but must be logged in for the scheduled task to run, due to MS Outlook update issues Microsoft are aware of.   Open the Add2Exchange Console and close the Console, selecting NO to log off.  All systems will sync in this mode, however, in this mode you cannot log off.  If you do and the Add2Exchange Agent was in memory, stop the Add2Exchange Service.  If the Agent does not drop from memory within 30 seconds or so, you will need to either end the Add2Exchange Agent task from Task Manager or reboot the machine.  Once the Agent is no longer in memory, open the Add2Exchange Console and then close, selecting not to log off.  If your machine has been tested to be able to log off, it may still be able to, but it may not.  Changes in your environment may stop it from continuing to operate when logged off.  A review of the A2E Event log is necessary. 

if your system has  this kind of Failure Audit 6370 Add2Exchange Agent (6920) Profile Setup For  Logged On For UNKNOWN: Session EVENT FAILED With Exchange Status Of Offline - then your system is not able to be logged off.  Open the Console and close it selecting no to log off.  Be sure you have the auto log on encrypted enabled for smooth operation.  This is found in the  Diditbetter Support Menu.ps1 shortcut from the desktop – right click and run as powershell.   

The Add2Exchange Service is started and the Add2Exchange Console is open (in this or another session). Close the Console. If the Add2Exchange Service is not started,  Add2Exchange simply will not replicate. The Add2Exchange service is the timer and must be on to replicate. Start the Add2Exchange Service.

The Add2Exchange Service has to be started with the Add2Exchange service account credentials. If a password for the account is not set to never expire, enter the new pw in the Add2Exchange Services Tab.  Open the Add2Exchange Console and if prompted, enter the new pw. 
SQL 2005 Express: If yours is an older system, start the A2ESqlSErver SQL instance as the Zadd2Exchange sync service account and credentials.
SQL 2008 Express (or later):  In later versions of SQL, the A2ESqlServer SQL Service instance should be started as the network service while using and only the Add2Exchange Service needs to be started as the service account. If you do a security sweep and change the password, these services have to be updated and started manually with the Add2Exchange password on the Log on tab of the properties of the Service(s).

Tip: It would be best practices to stop the Add2Exchange Service before doing a Microsoft Update and doing a reboot afterwards. This will ensure the services Microsoft stops are started again and critical services, (like Exchange or SQL) are not shut down during a replication cycle. A reboot afterward usually cures this issue, so please make it best practices on that server to reboot after any MS updates.  Stop Add2exchange service when doing full antiviral sweeps of the exchange or replication server or doing ESUTIL integrity checks and/or Exchange Backups.

There may be a pending reboot on this machine, the CAS server or Exchange Server, your remote SQL Server if so configured, or there was a recent automatic Microsoft Update on any of these machines.  Best Practices is to Stop the Add2Exchange Service and do the MS updates and reboot afterwards.

The Add2Exchange Service may not be starting after rebooting. If possible, please set the Add2Exchange Service under properties in Service Control Manager to Delayed Start if that option is available to allow for proper start sequence.

Upgrade Add2Exchange Enterprise:  You may have an older version of the program with a fix you need.
Upgrade to the latest release can solve many issues and is often the first step. Follow the link to make sure you will get the upgrade for FREE, or if you have to renew.    TIP: Since an upgrade of Add2Exchange requires stopping the Add2Exchange Service, uninstalling the older version and installing the new update and Service, you will need to reset this delayed start setting after each upgrade.

TIP: If upgrading, it is not necessary to reboot after an Add2Exchange Update if you close the Console and Stop the Add2Exchange Service first, prior to the uninstall.  None of the Add2Exchange Settings will be lost.

Perhaps the Add2Exchange Service is not started when you log on into the replication server to begin troubleshooting. Make sure there are no other sessions open with the Add2Exchange Console open.   Start the Add2Exchange Service manually and correct any logon passwording failures.   Check and correct the Add2Exchange Service and the SQL a2ESQLSERVER Service after any passwording changes. It is best not to require pw changes on this account and/or place this in an unmanaged service account policy container in AD.

The Add2Exchange Service not starting after rebooting.
The Add2Exchange Service does not start or prompt to start when closing the Add2Exchange Console. With the Add2Exchange Console closed, try to start the Add2Exchange Service manually.

The Add2Exchange Service is started, but Add2Exchange is not syncing. The system may have done a MS update and not rebooted afterward.

RESOLUTIONS: Common Steps to Identify what issue is causing your issue

If you do these next steps in order, you can identify which applies in your case and what to do to avoid this in the future. Read the entire post first.

Before you open the Add2Exchange Console or do anything else on the replication server, you have to log on as the Add2Exchange Service account.
TIPS: This program is installed only for this service account user, and cannot be run as a Domain Admin, so do not drag shortcuts to the programs around from one user to another. You cannot hide the service account from the GAL. Do not elevate or remove permissions to the service account to troubleshoot.

If you are in a "broken" condition, before you do anything else:

Open up Task Manager so you can see the CURRENT status of Add2Exchange. This will assist you in figuring out exactly what the problem is on your server, before you change anything.

Open Task Manager – view Processes, sort by Image name
See if the Add2Exchange Service is running. If only the Add2Exchange Service is in memory, it is waiting for the next cycle.  If it is running both the Add2Agent and Add2Exchange Service programs in memory, it is currently syncing.  Check the Add2Exchange Event log for errors.

If there are two of Add2Agent programs in memory, stop the Add2Exchange Service, and wait a minute or to for Add2Agent to stop.  If they both don't stop, then end task.   To fix this kind of issue, upgrade to the latest edition of Add2Exchange.   Also, check for any scheduled task.  These are not absolutely necessary and can cause issues like this described.  Also, do not use the "Cycle Service" button in Service Control Manager.  Since the Add2Agent doesn't stop immediately, it can cause issues.

If the A2E Director is present, or the A2ESP program or Add2exchange RELMAN program are in memory, then you have an older version of Add2Exchange which has been deprecated and you must upgrade.  See upgrade procedures. 

Open the Add2Exchange Console and the Add2Agent should drop from memory and the Add2Exchange Console will open. This is normal operation. You cannot have the Add2Exchange Console and A2E Service running, as the Sync tests for the Console and will not sync (while changes can be being made to the relationships.)

Special condition: If is possible you have the Console open in another Terminal Services Session. Open Task Manager and Users Tab to verify if that feature is available to you, or go to Remote Desktop Connections Manager and log off the other session, or switch sessions and log that off. Then restart the Add2Exchange Services. Again, A2E will not replicate with the A2E Console open in this session or any other session on the machine.

If the Add2Agent program fails to drop after 1 minute, or the console fails to open, kill them manually, and look to upgrade your version. Be sure to stop the Add2Exchange Service before MS updates and reboot after.
TIP: It is best to manually control the Update settings of this server, stopping the Add2Exchange Service prior to a MS update (so we are syncing to a system which is up and not patching) and reboot after. This is best practices. To automate this, please see the article Stopping Services in the Manual on the desktop.

If none of above situations exist, while viewing Task Manager as above, open the Add2Exchange Console.

Normally, the Add2Exchange Service, Add2Agent processes stop when the Add2Exchange Console opens. If so, then this means your system is communicating well with the Services we require.

If there is only one Add2Exchange Service and one Add2Agent,  then Add2Exchange is running normally and A2E is in the middle of performing a Sync. This is normal.

Be sure to check the Add2exchange Event Log and note the last time you had a success audit. If there is a huge gap in time, it is possible one of the suggestions to modify your update procedure or close the A2E Console or start the Add2Exchange service above will help you stay syncing.

If in the Add2Exchange Event Log there are recent errors you can search for them on the Support site. We may ask you to send any errors for email support. If there are errors, and the message does not help you correct it, you can create and include the errors as part of your trouble ticket at http://support.diditbetter.com/support-request.aspx

TIP: If it is common for you to have to reboot in order for A2E to start to sync again, and then stops later on and this is common, it is possible the system has not been rebooted in 90 days or more. Before the reboot, look to see if you are starving for memory or we should limit the amount of SQL Memory you are configured to use on that box. If you are paging, look to the paging file size. Consider making optimization changes, but these are ways to optimize the system for configuration issues for greater consistency. TIP: Antivirus Active File Scanning can also cause issues. Excluding our environment can create stability as well with this bulletin: Exclude from Antivirus Scanning.

The simple solution to many issues is stopping the Add2Exchange Service, check for an upgrade to the version of Add2Exchange, upgrading if necessary, doing the MS Critical updates and rebooting afterwards.

If any of these special conditions exist, then doing what was recommended above and closing the Add2Exchange Console and starting the service should get you back syncing.

Please stay current with the current release of Add2Exchange as we make improvements constantly and releases about once a month on the 15th or so. Subscribe to the RSS FEED on the site below. Do your MS Critical updates first during your next maintenance cycle, then reboot afterward, stopping the Add2Exchange Service prior. Then you can update A2E without any reboots or interruption.

If syncing to Office 365

To Sync to some Exchange 2013, 2016 or Office 365, (with Outlook installed) the sync service account has to be logged in for it to replicate.  It can be locked, the service should be running and Outlook does not have to be open.   Add2Exchange still operates as a service, but must be logged in for the scheduled task to run, due to MS Outlook update issues Microsoft are aware of and are fixing. 

To make Add2Exchange work again
Stop the Add2Exchange Service and verify that there are only one Add2Agent in memory and it stops eventually when the Service is stopped.
Open Outlook - press Send and Receive.  Potentially do Update Outlook from within the program (File - Office Account) or from MS updates.
Go to the Outlook email profile and make sure there are no duplicate mailboxes added,  If so, remove all duplicate mailboxes.  Add2Exchange does not need them there, and the additional mailboxes are only there for your convenience, but there should NEVER be two of the same.  .   
If you can not open outlook, do the above procedure from the Mail applet in the Control Panel.
Be sure the passwording procedure tips above do not apply in your case.

If Outlook doesn't open, (as when editing the Outlook profile there is no server name specified) Note the exact name of the Outlook profile,  and delete the older Outlook profile and apply.  then remake the profile with the exact name again to maintain licensing.   Upgrade to the latest Add2Exchange Enterprise.

Need help?  Want one of our certified engineers help you remotely?  Contact CustomerCare@diditbetter.com for scheduling

If you are on Premier Support, fill out the request and specify you are on Premier Support and we will handle you with the next available appointment.  You would have Premier Support if you purchased one of our value bundles. 

If you want to escalate and start an incident or get on Premier Support, we can make much shorter work of this by remoting in with you. You don’t have to give us logins or passwords, we work together. Most incidents take about 30 minutes to resolve, and give as an opportunity to even do some "relationship therapy" and make sure the relationships do exactly what you want and suggest other ways to support your business information needs.

Benefits of Premier Support are Priority Service and discounts in a nutshell: Time never expires until you use it, no administration fees, half off on all essential tools, server optimization, speedier resolution, and a potential for training.  See this link for more details:

If you are able or unable to follow the link and purchase any of the above, please call in to schedule.　
If we have an available engineer, we will assist then or schedule.

TIP: You will be prompted at the store for your logon credentials, and please note for your security, the login to the support site is a different login than that of the store.  When you create one, it could be the same as the support site if you wish.

Please also review the Remote Support Guidelines here to prepare for your session. At your appointment time, please call in and ask for the technician assigned to your case.

TIP: If you wish to continue by Email support, please start by updating to the latest version of Add2Exchange

We are unable to troubleshoot older versions as per the release notes.　

A: They can make additions to any contact element which is NOT in AD, ie pictures, other extended fields.  If there is a field in AD which is mapped to a contact item, that field will overwrite the changed entry from the Cache entry next time GAL Sync occurs.  If there is not a field mapped to a contact, you can add all you want to it for the other Outlook contact fields. 

The rub there is that we have a special relationship, called a GAL Contact relationship which are always unidirectional, in other words, info goes from the GAL to the Galcache public folder.  The contact relationships you set up to the users from the GAL Cache are unidirectional, because you cannot edit the GAL from the public folder – that would be a security hole.  In other words, the users cannot edit their copies of items which came from the GAL and have it go back to the GalCache with a normal GAL Contact Relationship.  This is true, but you COULD make a non GAL Contact Relationship which would be bidirectional.  Then the mapped Contact fields which are in the GAL will overwrite the normal GALcache entries next time GAL Syncs, This might be confusing to users, since users may expect to be able to edit ANY of the contact item elements, even those which came from the GAL.

BTW, if you added Additional Contacts in the GAlCache, (not in the GAL) to that folder, they will sync.  But this certainly is not optimal.

Q: I was wondering if it would be better to set a 1 way sync of the global address list to a shared contact list and then syncing the shared list with the individuals that needed it.

A: Yes, that would be cleaner and more efficient. You can still have the unidirectional GAL relationship to the GALCache, and then have a separate folder which you can set up bidirectional relationships and the destination folders of both templates could go to the same folder in the user’s mailbox.

Q: If I do this, will they be able to edit the contacts in the shared contact list without the global list overriding those additions?

A: Yes because it would be a different relationship to that folder – the gal is unidirectional and the shared is bidirectional. 

Tip, be sure to add pictures to the GAL Cache entries.  Make them small and “glamor shot” types so that when the person calls, their picture shows up on the smartphone.  People seem to like that and those pictures stay there even after a new GAL Sync since it is a field which does not exist in AD.  Also, by the way, be careful of exactly what information you put into the GAL to be synced to everyone so as not expose too much personal and confidential information.

Does this help?

As I understand it, you had another product running , or the items were copied in there from a destination, right?

The toolbox is 250 if you are not on Premier Support, and if you are, it is half price.  With Premier Support you can get us to fix this for you and it would take about 30 mins or so and have plenty of time to command our attention moving forward.  It is 4 hours, never expire until you use it for only 399.  There is another option, you CAN do this by yourself, for free, but it is not the best option in my opinion.

You can export the contacts to CSV, and then reimport to a local empty folder, stripping any copy flags, and then copy to the existing (emptied) source folder, but you would have to make sure to set all the relationships to remove destination copies if source items are deleted to avoid duplication.  Your relationships are probably set that way already.  I prefer to do in place stripping because it avoids the potential for data loss, like pictures or attachments and is cleaner.

That's my build : 8.5.163.151. Is it the latest version or not ?

So I have to purchase a 250$ Toolbox's License to make that software works ?

Not a good new...

We will remote in and show you the issue.  Are you current with the current build? Use this to update if you are still on free

software updates. http://support.diditbetter.com/kb/a2e_219.aspx before we connect.

Any update, my problem stills occur...

Thx

Upgrade to SQL Express 2008 R2 with 10 gig limit - Free

Procedure

Stop the Add2Exchange Service

Run the installer which gives you the option of upgrading your existing instance. Select A2ESQLServer to upgrade.

http://www.microsoft.com/en-us/sqlserver/editions/2012-editions/express.aspx

this post outlines the straightforward process. No reboot is necessary.

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=200

You have to do the 32 bit upgrade, even on a 64 bit system, because from this matrix it would appear as though you cannot upgrade 32bit to 64bit, at least not directly.

At the writing of this article, you have to install the SQL2008 R2 upgrade on the same replication Server where Add2Exchange is installed.  In the future, you will be able to connect to a new ore existing full edition of SQL Server on another box and communicate by TCP/IP.

Run the upgrade wizard and then accept defaults

after done, restart the Add2Exchange Service with the A2e Service account credentials.

Doing this will allow for the proper cleanup of the folders and the A2E database. 

Often for calendar relationships, when deleting a relationship, the items for that private to public relationship are kept in a public folder, (or the manager folder) just for information purposes only.  They will not replicate again since the source is about to be deleted.

When deleting a private to private relationship, as was mentioned, you may want the items in some folders but not others.  If you don't care about the appointments, then select to remove. This desired effect may be different in your organization. 

If you delete the user without removing the relationship first, the source folder (or destination folder) will no longer be available for the cleanup

and the items will remain in the destinations as “orphan items”, or those which do not sync anymore.

STEPS

To remove a user, log in and change their password. Do not hide from the GAL

We suggest (for Add2Exchange Enterprise edition) remove all distribution group memberships so the Templating system will remove the destination items automatically if the template is assigned.

Log in to the replication server and open the Add2Exchange Console.

Delete all relationships to or from the user.  Specify whether you want the items left there as orphans.

Once all relationships to or from that user are deleted, close the Console and start the Add2Exchange service for it to dereplicate and clean up.

Tip:  If these are contact relationships to or from the user, do the same process above but ALWAYS select to remove destination items.  What will be left in the mailbox will be all original items.  If you wish those items to be replicated, after the complete sync where it dereplicated all copies to or from that user, you can inspect those remaining originals and select to move those desired items into a source folder for rereplication to other users or folders.

Sometimes it is necessary so the item is included to sync to relationships for changes to old recurring items.  Sometimes they are not being tagged by our separate recurring item sync routine.  This was often caused by making the appointment in older versions of Outlook.

The best thing to do for OLD recurring items is to stop the recurrence of the older items, and then make a new one for that recurrence pattern going forward.  This way it does not have to replicate so far in the past to get the master recurring appointment.

Currently, in order to connect and sync old recurring items, we had to set the prior days to replicating 2 years in the past for every relationship.

This is not optimal from a replication standpoint, because a bunch of OLD items are replicating, and most are not changing, and this strategy will work if they don’t want to edit the old active recurring meeting items, (there are probably just a few) then edit and stop the old ones on the last recurrence and then recreate new ones for the same meeting going forward.  If this was done, we could change the relationships to have a smaller date timespan and thus replicate faster.  Then they could make the exceptions to the new ones and they would all replicate within the shorter timeframe of the relationship.

Again, if they did go ahead and edit those items, stop it the last occurrence and then create new ones moving forward, we could shorten the days in the past we are replicating for every relationship and their sync times would be much shorter.

The current strategy, to lengthen the prior days of sync and widen the timespan,  will work as is, and if you want to adopt this strategy in the future, or over time, the settings could be changed then, with perhaps only a year in the past. 

If you don't use the edit and end and then recreate in the future strategy, In less than two years, when these item changes are not being replicated to everyone, you may have items which again probably don't replicate. At least you will know how to manage this.  Again to be clear, if over time you edit the old ones and recreate them in the nearer future, without missing a scheduled recurrence, we can avoid any issues moving forward and then be able to edit the relationships for a smaller timeframe.

Hope this helps!

Sorry for the delay I was out of office for few days...

In wich Timezone are you cause I'm in France (GMT +2) ?

Have to buy Premium support or not ?

Regards.

PeBoyer

With the Toolbox you would select inspector general and then surgeon general, pick the public and then select to remove a2E copy = true NP

I will help you if you wish.  If you have the value bundle or previously licensed it, then let's go!

http://support.diditbetter.com/support-request.aspx

Doing it without licensing anything, the Free way, delete the relationships and select to remove destination copies

let run a full sync

it will dereplicate

then export contacts to csv and then back in, and the named properties are gone.

The tools - deals are here: http://support.diditbetter.com/premium-support.aspx

And A2E wasn't install in this Exchange 2010 server, it's a fresh new install but Public Folder were migrated from existing Exchange Server.

Regards.

I made a Private to Public contact relation (One way sync) and I have an issue :

Only 415 contacts (on 2456) were created in my Public Folder at first sync, and no more since....

How is it possible ????

Rights are good (made with preinstaller).

Maybe a hint : when my customer was in Exchange 2003, he's got A2E with the same sync schema, it was uninstall with the new Exchange 2010 server.

So maybe others contacts are "marked" as already sync with this folder, don't you think so ?

Please need help !!!!

Regards.

Pierre

 If the service is already started, (which it probably shouldn’t be if the Console is open) the program will not ask you to start the service

If the service is not running, and it does not prompt you, the machine must be a Windows Server 2008R2

And yes, that is a known issue.  This is the only real incompatibility with Win Server 2008R2 and this issue will be fixed very shortly with a maintenance release.

In the meantime, you can use two net start helper applications and you can set a desktop shortcut

They are installed where A2E is installed and explained here:

Make a shortcut to the desktop for these programs on the desktop of the Add2Exchange Service Account.  Unlike the Add2Exchange Console, these are just “glorified” net start and net stop utilities which can orderly start sql and can also stop the A2E Service and then the A2ESQLServer, orderly as before a MS update.

http://guides.diditbetter.com/a2e-guide/stopping_the_add2exchange_service_during_backup.htm?zoom_highlightsub=stopping

In the short run, before the fix, you just remember to start it when you Close the A2E Console,

Or you can use these programs as a temp fix for Windows 2008 R2.

Or you could even put a scheduled event to start add2exchange service.

If you subscribe to the RSS feed on the website, you will be notified automatically:  http://www.diditbetter.com/feeds.aspx

Please note to stay current. 

The most recent changes released (today) to Add2Exchange are big, for speed and reliability, and some fixes so go get current please using these instructions.  http://support.diditbetter.com/kb/a2e_219.aspx

For the current list of changes: http://support.diditbetter.com/kb/A2E_150.aspx. Be sure to find your version number and see what has been done after that.  If there have been mandatory changes since your release, then upgrade soon for reliability.

Hope this helps.

Are Outlook categories are also transferred when folders are synced.

Essentially, we are trying to create a category master list so that contacts are categorized the same on everyone’s computer. Will the software do this?

Answer:

Yes, all Add2Exchange and Add2Outlook products sync categories.

But in order for the destination users to use the categories, the master list of categories must be made on the destination folder the same as they are on the master source folder (including Case).

All of our products also sync colors, but if you are using Outlook 2003, they may not be shown because O2003 does not support the category colors. They can be seen from an Outlook 2007 or 2010 client, and if the mobile device supports categories and colors, then they will sync there as well.

Often people want to sync only items of specific categories, and as of yet, this is not supported.  This can be gotten around by setting the relationship up a certain way.  If you syncing all the existing items and set the relationship for that user so that if a destination item is deleted, it never gets recopied, you get the same effect.  This is very easy to do, if you view the destination folder items by category and then delete those you do not wish to have.  (Be careful not to delete personal items) The next Add2Outlook or Add2Exchange sync, if that relationship is set to do not recopy deleted destination items, then only new ones will sync. We call this the pruning option of a relationship.

Most AD fields are represented (mapped) to a field in the Outlook contacts.  Any field mapped from AD to the Outlook Public folder GAL Cache will be overwritten from the GAL each sync cycle. Gal Cache has it's own timer and definable interval.  

There are more Outlook fields than there are in GAL and if you add data to those fields, the data you enter which is not an AD GAL mapped field will stay there and sync. One of the fields in Outlook which is not in AD is an attachment for a picture, so you can add pictures to the GAL Cache public folder and it will sync out to the phone.

TIP: Make the pictures small png or tiffs so the size of each contact remains relatively small.  Tip2:  Female secretaries like the glamour shots, not the Monday morning with no coffee pictures.  Tip3: Finally, be prudent in what you add to the AD  records because this information will be available to those with relationships.  Cell phone numbers and home address may or may not be advisable, depending on your business situation.

Then you make the special kind of A2E Contact Relationship from public to private called GAL relationships. You can make single relationships or use the RGM Templating to make a template and attach to a distribution list.  These relationships are also only one way, unidirectional on information flow.  Users can edit the GAL Cache contact, but only the fields which are not mapped from AD.  As a result of a relationship, users can not edit their GAL Cache contact copy in their personal folders and have it write back to the GAL Cache or AD. This restriction maintains security and makes sure AD and the GALCache are the master copies.  Gal relationships can be set to recopy if the destination item is deleted or it can be set not to be recopied, but most GAL relationships are usually set to recopy.