Failed: Item retrieval failed on the server
In the IIS logs
2014-06-24 09:03:24 192.168.103.127 GET /EnterpriseVault/FullSync.aspx Slot=07b647d1-2450-45eb-ba55-9100bc59efa3&SeqNoLow=0&ArchiveID=19175CE8AC1F8A74F8BCE19BC0F9B3D551110000apdchnev.S5010.COM&SeqNoHigh=741 443 S5010\gsp 192.168.109.24 EnterpriseVaultOutlookExt-V11.0.0.1351 200 0 0 2948
2014-06-24 09:03:53 192.168.103.127 GET /EnterpriseVault/Slot.aspx ArchiveID=19175CE8AC1F8A74F8BCE19BC0F9B3D551110000apdchnev.S5010.COM&Slot=07b647d1-2450-45eb-ba55-9100bc59efa3 443 S5010\gsp 192.168.109.24 EnterpriseVaultOutlookExt-V11.0.0.1351 200 0 0 15
2014-06-24 09:04:04 192.168.103.127 GET /EnterpriseVault/clienttest.gif - 443 S5010\gsp 192.168.109.24 EnterpriseVaultOutlookExt-V11.0.0.1351 200 0 0 0
2014-06-24 09:05:22 ::1 POST /evindexing/velocity.aspx v.app=api-soap& 80 - ::1 - 401 2 5 0
2014-06-24 09:05:22 ::1 POST /evindexing/velocity.aspx v.app=api-soap& 80 S5010\evadmin ::1 - 200 0 0 31
2014-06-24 09:05:45 192.168.103.127 GET /EnterpriseVault/Slot.aspx ArchiveID=19175CE8AC1F8A74F8BCE19BC0F9B3D551110000apdchnev.S5010.COM&Slot=07b647d1-2450-45eb-ba55-9100bc59efa3&release=true&MSt=0&CSt=300&Ls=
2014-06-24T09:00:08&Ci=152&Td=8741 443 S5010\gsp 192.168.109.24 EnterpriseVaultOutlookExt-V11.0.0.1351 200 0 0 31
2014-06-24 09:05:45 192.168.103.127 POST /EnterpriseVault/DeleteJob.aspx - 443 S5010\gsp 192.168.109.24 EnterpriseVaultOutlookExt-V11.0.0.1351 200 0 0 15
2014-06-24 09:05:46 192.168.103.127 GET /EnterpriseVault/clienttest.gif - 443 S5010\gsp 192.168.109.24 EnterpriseVaultOutlookExt-V11.0.0.1351 200 0 0 0
2014-06-24 09:05:46 192.168.103.127 GET /EnterpriseVault/ClientDiagnostics.aspx P=2&MSt=0&CSt=301&Ci=152&Td=8741&Fa=0&Host=ISD-PC-
as per this MSt=0&CSt=301 it was failing on the DB file CC_FAILED_NEXT_DBBUILD (301)CC_FAILED_FIRST_DBBUILD +
In the client trace
24/06/2014 04:26:49.219[3392][M]: CONTENT:DWNL:REG: Current date and time is '20140624-095649'
24/06/2014 04:26:49.219[3392][L]: CONTENT:DWNL:REG: ~CCBITSRegistry::GetCreationDateTime: 0x0
24/06/2014 04:26:49.220[3392][L]: CONTENT:DWNL:REG: CCBITSRegistry::SetJobState: 0x0
24/06/2014 04:26:49.220[3392][L]: CONTENT:DWNL:REG: ~CCBITSRegistry::SetJobState: 0x0
24/06/2014 04:26:49.220[3392][L]: CONTENT:DWNL:REG: ~CCBITSRegistry::CreateBITSRegistry: 0x0
24/06/2014 04:26:49.221[3392][L]: CONTENT:DWNL: ~CCBITSSupport::CreateBITSJob: 0x80200049
24/06/2014 04:26:49.253[3392][L]: CONTENT:BUILD: ~CCDownloadContentCache::CreateDownloadJob: 0x80200049
24/06/2014 04:26:49.284[3392][L]: CONTENT:BUILD: ~CCDownloadContentCache::StartJobRunning: 0x80200049
24/06/2014 04:26:49.284[3392][L]: CONTENT:BUILD: ~CCDownloadContentCache::StartFullDownload: 0x80200049
24/06/2014 04:26:49.285[3392][L]: CONTENT: ContentCacheImpl::IssueFoundRetryLater
24/06/2014 04:26:49.285[3392][H]: CONTENT: RETRY logic started reason '301
Hex Code returned in client trace means BG_E_TOO_MANY_JOBS_PER_USER (0x80200049)
BITS Return Values
http://msdn.microsoft.com/en-us/library/aa362823%28v=vs.85%29.aspx
BitsAdmin /list provides the following output:
BITSADMIN version 3.0 [ 7.5.7601 ] BITS administration utility. (C) Copyright 2000-2006 Microsoft Corp.
BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.
{64CDA8A7-E93B-4A9B-AF92-E489647BA13F} 'Microsoft Outlook Offline Address Book 3176d2382e986b4e81eeaec7fe1f82e4' ERROR 0 / 1 0 / UNKNOWN {AE35ECF3-2BFB-430F-973C-E27F3DAD764A} 'Microsoft Outlook Offline Address Book 3fcd0a69f77f0a4f8a49d0ef98924bb2' ERROR 0 / 1 0 / UNKNOWN {EACA4819-A5C4-4BFC-8140-7FAE8D835E52} 'Microsoft Outlook Offline Address Book 3176d2382e986b4e81eeaec7fe1f82e4' ERROR 0 / 1 0 / UNKNOWN Listed 60 job(s)
The BITS job count for the user has exceeded the per user job limit set by the MaxJobsPerUser Group Policy setting causing the Enterprise Vault Outlook Add-in to fail when trying to create a new download job for Vault Cache.
This issue is related to BITS and it is not caused by the Enterprise Vault Outlook Add-In. Microsoft should be engaged to determine a probable cause for this behavior. The following steps can be used as a workaround for this issue:
Workaround: