Even when Riva On-Premise is correctly synchronizing data, an Exchange 2007 EWS hosted service provider might report excessive logging, as in the following example.
18.104.22.168 ExchangeServicesClient/14.00.0650.007 200 0 0
2010-12-21 16:16:11 W3SVC1 10.192.30.12 POST /EWS/Exchange.asmx - 443 - 22.214.171.124 ExchangeServicesClient/14.00.0650.007 401 1 0
2010-12-21 16:16:11 W3SVC1 10.192.30.12 POST /EWS/Exchange.asmx SoapAction=SyncFolderItems;Version=1;RpcC=6;RpcL=15;LdapC=0;LdapL=0; 443 sdncom\DSSuite 126.96.36.199 ExchangeServicesClient/14.00.0650.007 200 0 0
The connection editor tests the EWS connection against all the users successfully but fails in three ways.
The error is caused when creating the EWS connection in the Riva application, specifically by using the email address of the connection account as provided by the service provider instead of using the NT LAN Manager (NTLM) or user principal name (UPN) of the user. Riva Exchange connections need to authenticate using the NTLM or UPN for the AD account that owns the Exchange mailbox for the connection account. With on-premises Exchange systems, the UPN and email address are usually the same. For hosted Exchange service providers, they are usually different.
Modify the EWS connection to use the UPN of the connection account. The UPN can be one of the following:
To prevent the excessive logging error:
Article ID: 294
Last updated: 15 Jun, 2016
Also listed in
Riva On-Premise - CRM Sync -> Manage Riva On-Premise (Admin Guides) -> Email Systems -> Exchange (EWS) -> Hosted Exchange