Add2Exchange Event ID and Resolution Dictionary 

Use: This page is designed as a support.diditbetter.com starter index. It includes a searchable Event ID table and seeded detail sections for the first resolution families reviewed so far. If your page editor strips JavaScript, the page still displays all content and site search / browser Find can still locate Event IDs and keywords.

How to use this page

  • Search by Event ID, keyword, source, dictionary section, or likely cause category.
  • Use the linked Event IDs to jump to seeded detail sections below.
Event ID Type Source Dictionary Section Canonical Message Likely Cause Category Resolution Status
1164 Failure Agent Main dictionary Main Process Synchronization to server / service account EVENT FAILED.    
1166 Failure Agent Main dictionary Relationships Synchronization EVENT FAILED confirmation(s).    
1168 Failure Agent Main dictionary Template Validation Members Clone EVENT FAILED. Permissions; clone state; folder path / store resolution; migration relationship confirmation Run Permissions manually: give account a supported license; unhide from GAL
1174 Failure Agent Main dictionary Synchronization EVENT FAILED.    
1321 Success Service Main dictionary Agent process audit EVENT ENDED successfully.    
1390 Failure Service Main dictionary Service setup / timer validation EVENT FAILED. Outlook / MAPI profile; service account; Autodiscover; registry current profile Agent Stuck in memory, Stop Add2Exchange Service and reboot, monitor
1430 Error Agent Main dictionary Application Event Exception. Moved folders / stale store IDs; mailbox access; permissions; MAPI exception family Seeded from operator notes
1440 Error Agent Main dictionary Application Event Exception during Relationship Process / RecordsetClass.Open.    
1504 Informational Service Normal informational IDs Agent process audit EVENT STARTED.    
1644 Termination Agent Stop / termination appendix Relationships Process EVENT PROCESS STOP Requested.    
1648 Termination Agent Stop / termination appendix Relationship Process Template Validation EVENT PROCESS STOP Requested.    
1654 Termination Agent Stop / termination appendix Relationship Process Synchronization EVENT PROCESS STOP Requested.    
1656 Error Service Main dictionary Application Event Exception in service setup / timer / licensing processing. Unknown; setup / timer processing Placeholder / needs review
1672 Success Agent Main dictionary Relationships Process Synchronization EVENT PROCESS ENDED successfully.    
1673 Success Agent Main dictionary Relationships Process Synchronization GAL EVENT PROCESS ENDED successfully.    
1674 Success Agent Main dictionary Relationship Process Template Validation EVENT PROCESS ENDED successfully.    
1680 Success Agent Main dictionary Relationship Process Synchronization item EVENT PROCESS ENDED successfully.    
1855 Informational Agent Normal informational IDs Relationships Process Synchronization EVENT PROCESS STARTED.    
1856 Informational Agent Normal informational IDs Relationships Process Synchronization GAL EVENT PROCESS STARTED.    
1857 Informational Agent Normal informational IDs Relationship Process Template Validation EVENT PROCESS STARTED.    
1863 Informational Agent Normal informational IDs Relationship Process Synchronization item EVENT PROCESS STARTED.    
1913 Informational Service Normal informational IDs Restart event.    
2071 Termination Agent Stop / termination appendix Relationship Process Template Validation EVENT PROCESS TERMINATED.    
2077 Termination Agent Stop / termination appendix Relationship Process Synchronization EVENT PROCESS TERMINATED.    
2079 Informational Service Normal informational IDs Main service EVENT PROCESS STARTED.    
2081 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2082 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2083 Success Service Main dictionary Process Queue / Timer Initial Process EVENT COMPLETED.    
2084 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2085 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2086 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2087 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2088 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2089 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2129 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2130 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2131 Success Service Main dictionary Process Queue / Timer Initial Process EVENT COMPLETED.    
2132 Success Service Main dictionary Process Queue / Timer Initial Process EVENT COMPLETED.    
2134 Success Service Main dictionary Process Queue / Timer Initial Process EVENT COMPLETED.    
2135 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2136 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2137 Success Service Main dictionary Process Queue EVENT COMPLETED.    
2138 Success Service Main dictionary Process Queue EVENT COMPLETED.    
9270 Success Service Main dictionary Main service EVENT PROCESS ENDED successfully.    
10000 Success Agent Main dictionary Add2Exchange PowerShell added Office 365 permissions successfully.    
10001 Error Agent Main dictionary BatchResponse argument was null. Permissions grant path; authentication; environment change; Office 365 / on-prem permissions workflow Seeded from operator notes
10002 Success Agent Main dictionary Add2Exchange database backup completed successfully.    

Seeded Event Detail Sections

These are the first operator-reviewed resolution entries. Everything else remains available in the index above and in the CSV seed for later enrichment.

Event ID 1168

Type
Failure
Source
Agent
Dictionary Section
Main dictionary
Canonical Message
Template Validation Members Clone EVENT FAILED.
Notes / Exception Detail
Dominant observed pattern: clone not created because member folder path is set/invalid. Additional observed variants include Get Address Entry failures and delegate mailbox-store delete failures.
Likely Cause Category
Permissions; clone state; folder path / store resolution; migration relationship confirmation
Potential Causes
Missing or changed permissions; migration relationship confirmation issue; stale clone state; bad member folder path; moved or unresolved store/folder; older build behavior.
First Checks
Review full event cluster around the failure; confirm service account can open Outlook; verify affected member mailbox and folder path; verify permissions; check whether migration / relationship confirmation recently changed.
Common Resolutions
Fix permissions; verify migration relationship confirmation; open Outlook as the service account; resolve the broken clone before recreating the clone; update the build; stop the Add2Exchange service, reboot, and monitor.
Escalation Trigger
If the folder path resolves, permissions are correct, the clone was rebuilt, and the failure still repeats.
Confidence
Medium
Resolution Status
Seeded from operator notes
Search Keywords
1168 template validation members clone clone not created store get folder path permissions migration relationship confirmation
Back to top

Event ID 1390

Type
Failure
Source
Service
Dictionary Section
Main dictionary
Canonical Message
Service setup / timer validation EVENT FAILED.
Notes / Exception Detail
Observed variants include: registry current application profile key failed; timer service elapsed - relationship(s) process table(s) exist failed.
Likely Cause Category
Outlook / MAPI profile; service account; Autodiscover; registry current profile
Potential Causes
Bad Outlook profile; invalid current application profile key; service account password issue; Autodiscover failure or stale profile configuration.
First Checks
Log onto the replication server as the service account; open Outlook and confirm the intended profile loads cleanly; verify the current application profile; confirm the service account password is current; test Autodiscover / remembered credentials.
Common Resolutions
Repair or rebuild the Outlook profile; correct the current profile selection; update stored credentials; resolve Autodiscover issues; confirm the service account can open Outlook and OWA without prompts.
Escalation Trigger
If the profile is clean and the event still repeats after credential and Autodiscover checks.
Confidence
Medium
Resolution Status
Seeded from operator notes
Search Keywords
1390 profile setup registry current application profile key service account password autodiscover outlook profile
Back to top

Event ID 1430

Type
Error
Source
Agent
Dictionary Section
Main dictionary
Canonical Message
Application Event Exception.
Notes / Exception Detail
Dominant observed pattern: Relationship Template Validation Members Clone failed with 'Clone Does Not Exist Active Member Store Get Folder From Path' and MAPI_E_NOT_FOUND opening the message store. Additional observed patterns include MAPI network errors, SQL/MAPI table execution errors, unknown entry ID, ODBC text-driver query errors, and null-reference errors. Top observed detail: Application Event Exception | MESSAGE: Error in IMAPISession::OpenMsgStore: MAPI_E_NOT_FOUND | DATA: System.Collections.ListDictionaryInternal | SOURCE: IRDOStore.get_IPMRootFolder
Likely Cause Category
Moved folders / stale store IDs; mailbox access; permissions; MAPI exception family
Potential Causes
Moved or missing folder; stale store ID; lost mailbox access; missing permissions; broader MAPI store lookup failures.
First Checks
Capture the full exception text and nearby event cluster; inspect LAST PROGRESS STATUS; determine whether the failure is folder resolution, store open, mailbox access, or another subfamily; confirm the service account can open the mailbox / store.
Common Resolutions
Default playbook should point first to moved folders or stale store IDs, then evaluate mailbox or permission loss; repair the relationship target; verify mailbox availability and permissions; refresh the affected relationship after corrections.
Escalation Trigger
If the same exception family repeats after store / folder / permission corrections or if the subfamily is not recognized.
Confidence
Medium
Resolution Status
Seeded from operator notes
Search Keywords
1430 application event exception MAPI_E_NOT_FOUND openmsgstore IRDOStore get_IPMRootFolder moved folder stale store ID mailbox permissions
Back to top

Event ID 1656

Type
Error
Source
Service
Dictionary Section
Main dictionary
Canonical Message
Application Event Exception in service setup / timer / licensing processing.
Notes / Exception Detail
Observed variants include: profile setup to server via user name failed; timer service elapsed - Add2Exchange Service Setup failed; timer service elapsed - Add2Exchange Console Closed failed; application licensing SQL execution errors; communication link failure in RecordsetClass.Open / ConnectionClass.Execute. Top observed detail: Application Event Exception | MESSAGE: Communication link failure | DATA: System.Collections.ListDictionaryInternal | SOURCE: RecordsetClass.Open or ConnectionClass.Execute
Likely Cause Category
Unknown; setup / timer processing
Potential Causes
Needs more clustered event context to classify confidently.
First Checks
Collect the full event text plus 5-10 events before and after; note whether this occurred during startup, timer processing, or setup validation.
Common Resolutions
What is this error response - leave this as text we can update later.
Escalation Trigger
Any repeat occurrence until the message family is classified.
Confidence
Low
Resolution Status
Placeholder / needs review
Search Keywords
1656 application event exception setup timer processing what is this error response
Back to top

Event ID 10001

Type
Error
Source
Agent
Dictionary Section
Main dictionary
Canonical Message
BatchResponse argument was null.
Notes / Exception Detail
Raw message: Cannot bind argument to parameter 'BatchResponse' because it is null.
Likely Cause Category
Permissions grant path; authentication; environment change; Office 365 / on-prem permissions workflow
Potential Causes
Failure to grant permissions to on-prem Exchange or O365 due to retired server, incorrect password, MFA introduction on the account, or SSO changes.
First Checks
Identify whether the failure occurred in an on-prem or O365 permissions workflow; verify current credentials; check for MFA or SSO changes; confirm the target server / authority still exists and is reachable.
Common Resolutions
Correct credentials; adjust for MFA / service-account auth changes; resolve retired-server references; re-run the permissions workflow after authentication and connectivity are fixed.
Escalation Trigger
If auth and target environment are valid but the permissions action still fails.
Confidence
Medium
Resolution Status
Seeded from operator notes
Search Keywords
10001 BatchResponse argument was null permissions grant o365 on premises retired server incorrect password mfa sso
Back to top

 

 

|

Website and materials copyright 2008-2014, all rights reserved DidItBetter.com Software. US: 800-837-8636 Intl: 001-813-977-5739

DidItBetter.com Software specializes in Exchange Sync and Hosting, Outlook Task Management and CRM solutions.