Hi all. I upgraded to Sage CRM 2017 R2 and I get the same error with one user only. Not using Outlook for Mac but Office 365. This is the only user that is not synching. I called into Sage and had them look at it and they removed and had Tomcat reinstall itself. It seemed to work on that day (on the 24th of July 2017) and now it has stopped again.

ERROR [http-apr-11009-exec-9]: 25-Jul-2017 07:46:59.345 [keith] ewsUrl: outlook.office365.com/.../Exchange.asmx, operation: syncFolderItems, error: javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error: unexpected element (uri:"">schemas.microsoft.com/.../types", local:"DoNotForwardMeeting"). Expected elements are <{schemas.microsoft.com/.../types& javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error: unexpected element (uri:"">schemas.microsoft.com/.../types", local:"DoNotForwardMeeting"). Expected elements are <{schemas.microsoft.com/.../types&

...

There is a bunch more lines.

Hi

I have exactly the same issue, any response from Sage ? Do you know how they reinstall Tomcat ?

We have the same problem since 13 june 2017

ERROR [http-apr-10009-exec-7]: 28-Jul-2017 13:31:02.862 [xxx] error: com.sage.scrm.syncengine.exchange.ews.service.error.SageExchangeServiceException: javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error: unexpected element (uri:"">schemas.microsoft.com/.../types", local:"PersonalNotes"). Expected elements are.....

CRM version 7.3 sp2

Exchange online

Mac users

Thanks for a response

Sage tech is still looking into the issue. Sorry Stanislas, I was not watching them. They spent 2.5hours on the server/workstation. They got it to sync that day but it stopped working again the next day.

Any news on this problem ?

Sage Support France says that this problem is maybe related to an update of Office for Mac. But there was 1 update since and the error still occurs.

Well we do not use Office for Mac. We use Office for Windows. None of my users are synching now. Calling Sage. Will let you know what they say.

Any News ? It become critical!

Spoke with Sage. They had me try to update a table and remove some duplicate entries but that did not fix the issue so back to them it goes.

Hello Everyone,

Issue is caused by updated schema from Exchange 365, issue is not appearing when customers are using their own exchange server.

They add new elements which is "PersonalNotes" and "DoNotForwardMeeting".

As our schema doesn't include this elements, sync engine is not able to process them.

There is a lot of cases escalated already and developers are working on this issue.

We have a new case of this problem. Windows only.

Problem appears following to an update of Exchange.

Sage R&D have to take a close look on this !!

Thank you Dawid for the update (cross post)

Thank you Dawid.

There is a KB article in the sage website for this 37250 Ask sage article, hopefully it will get updated.

Hi folks,

The issue was caused by an update to the Exchange Online types definition; essentially, it's sending on fields to us in our GetItems request which we have not requested, and for which we have no local definition. A fix is in test at the moment, with hotfixes to be delivered asap. Since the issue is caused by an update on the Exchange side we'll be hotfixing all supported versions.

Thanks,
Rob

Hi,

Just another quick update. A fix is being put through by Microsoft at the moment - I can no longer reproduce the issue with an un-customised copy of 2017 R3 as of this morning. I was getting an issue with the DoNotForwardMeeting element in my install.

With the fix being delivered on the EWS side of the integration, we shouldn't need to make any changes to any existing release of Sage CRM (we weren't the only product affected by this). The issue was caused by the addition of new functionality to Exchange Online.

Current status is that the fix is 87% complete, with an estimated completion time of 1 to 2 days. I'd take this with a small pinch of salt - an attempted fix was put into production a few days ago, and was then reverted, so it looks like it might be a fairly complex fix. No further action is required in your installs to get them working - they should just work once the fix is deployed.

Thanks,

Rob

Thank you for the update Robert. So are you saying there will be no patch to install for Sage CRM and it should just work again?

Hi again folks,

The issue is tagged as resolved by the Office 365 team, and looks fixed from my side (the messages that we're getting back from Exchange Online appear to be back in-spec).

If these unmarshalling errors persist for anyone, can you please follow up asap with your local CRM support team? We'd be interested in particular in getting the CXF logs in addition to the regular CRM logs. CXF logging is described in KBA 492-16921 on this site, but a Sage technician should be able to help you generate these if needed. These logs contain the messaging between our synch engine and the Exchange endpoint, and so are needed in order to confirm if there's an issue with what we're being given by Exchange Online.

Thanks,

Rob

Yep, there should be no further action required on your side, aside from just re-enabling the integration. The issue was with the XML data that we were being supplied by Exchange Online.

Hi, I still have 2 mailboxes not synching properly. Same unmarshalling error about: Personal Notes

I have stopped the sync and restarted it and it still cannot pick up those 2. The other mailboxes are now synching properly.

OK so it is in the contact sync - when I do not sync contacts then the mailboxes sync properly. Now to find out which contact has "personal notes". None of the users remember putting personal notes on a contact. *sigh*

Hi Rob,

Do you have update on this as of today?

Hi,

We have still problems on some users mailbox

ERROR [http-apr-10009-exec-9]: 15-Aug-2017 21:36:49.385 [jak] error: com.sage.scrm.syncengine.exchange.ews.service.error.SageExchangeServiceException: javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error: unexpected element (uri:"">schemas.microsoft.com/.../types", local:"PersonalNotes"). ...

Best regards

Hi,

sorry folks, I didn't get the email alerts from this thread. Support contacted me regarding this this morning.

You're right in saying that this appears to affect the Contacts synch only. I haven't reproduced this, but have an open case with Microsoft regarding this issue.

I'll post updates as I get them - I assume that this is closely related to the earlier issue.

Thanks,

Rob

Hi, try disable the "sync contacts" and see if you still get the error. It does not error out when you say "no" to "sync contacts". I am sending log files to Sage about it. Will keep you posted.

Hi folks,

We have an ongoing case with Microsoft. If you're affected by this issue, please raise a case with them via the admin portal and ask to be linked to the following incident reference:

#30126-6219954

Further updates as I get them.

All the best,
Rob