Overview
This article provides the steps to identify and solve an issue you may encounter when the Outlook Connector fails to synchronize.
Error: "(FB) GetBulkDetailedMessages() - An entry with the same key already exists.)"
Information
The Outlook Connector fails to synchronize. To identify this known issue:
- Check and confirm that the server uses Firebird-based Archive Stores.
- The debug logging on the server from the same time frame when an Outlook Connector sync failed aligns to the sample flow shown below:
ASPNET/UI 2013-11-26,14:52:26,803,1,"#00005E54","#0000000D","info ","WSOutlook","GetMessages: startDate 11/26/2012 2:52:26 PM, endDate 11/26/2013 2:52:26 PM, userId 33236c5e4a619741a3017729303d4f36, databaseId 917458cb-c134-4081-b48c-04c4019c8071, timeStamp 8211, ceilingTimeStamp -9223372036854775808" 2013-11-26,14:52:39,017,1,"#00005E54","#0000000D","error ","WSOutlook","Error: GetMessages failed.
The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server to send the exception information back to the client or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
" STORE 2013-11-26,14:52:27,427,1,"#00002FA4","#00000017","info ","EmailMessageMapper","GetDetailedMessages start[8211] maxCount[100] txIdTimeFrame[30] startDate[2012-11-26 14:52:26] endDate[2013-11-26 14:52:26]" 2013-11-26,14:52:38,924,1,"#00002FA4","#00000017","error ","EmailMessageMapper","error: GetDetailedMessages - QueryFailed" 2013-11-26,14:52:38,924,1,"#00002FA4","#00000017","error ","EmailMessageProvider","error: (FB) GetBulkDetailedMessages() - An entry with the same key already exists." 2013-11-26,14:52:38,924,1,"#00002FA4","#00000017","error ","ErrorsDal","error: (FB) GetBulkDetailedMessages() - ;message: An entry with the same key already exists. Notes: Outlook Connector side debug logging does NOT allow to properly identify this known issue.
Process
To fix this issue, upgrade to MARC2014 build 20140616 or later.