ソリューションが必要です
Not sure if slow is the right word - retrieving an archived message with the add-in is nearly instantaneous. In OWA, sometimes it fails, sometimes it comes up immediately, and sometimes after it fails and you "clear" the error message and click view item it succeeds. Some messages never get retrieved. It nearly always succeeds in Outlook 2013 with a long delay.
Anyone else run into this? The control-shift inside of Outlook 2013 only yields two lines (same thing every time and completely meaningless) and in OWA I get this a lot:
EVOMA (TRACE) 15:33:38.121: Making EWS call to find item with restriction : <t:IsEqualTo><t:ExtendedFieldURI PropertyTag="0x10F3" PropertyType="String" /><t:FieldURIOrConstant> <t:Constant Value="1A5494EB40A62EC4591C4C3EBB6F0245A1110000evmbx01!201311285596919.201310281445430000.Z.00010A912E6A6480D687C8CF503287A1.eml" /></t:FieldURIOrConstant></t:IsEqualTo>
EVOMA (TRACE) 15:33:38.251: EWSFindAssociatedItem.onEwsRequestComplete()
EVOMA (TRACE) 15:33:38.253: ItemViewer._isCanceled()
EVOMA (TRACE) 15:33:38.255: EWS call to find item returned successfully
EVOMA (TRACE) 15:33:38.257: Item count = 0
EVOMA (TRACE) 15:33:38.258: EWSFindAssociatedItem waiting, retries remaining: 38
EVOMA (TRACE) 15:33:39.278: EWSFindAssociatedItem.invoke()
EVOMA (TRACE) 15:33:39.280: EWSRest_RestoredItem.getSoapTag()
EVOMA (TRACE) 15:33:39.282: EWSRest_DistinguishedFolderId.getSoapTag()
Seems to be retrying and eventually "finding" it but I'm not sure where to begin troubleshooting. Since it sort of "works" I thought it was a performance issue of some sort but even when everything is pretty much at 0% CPU on all of the systems involved it behaves about the same - I'm at a loss.
Dan