PDA

View Full Version : Office 2016 update kills CommitCRM


sapsford
October 24th, 2016, 05:33 PM
Hi all, a heads up, latest Office 2016 updates stops CommitCRM from being able to email out

It crashes CommitCRM and doesn't send the email

5 computer here were on over the weekend and 5 weren't. The 5 that were on pulled down and installed the latest update.

Rolling back office didn't work, only a complete uninstall and reinstall of an older version worked

We have set all computers not to update office in the meantime

Lost a day sorting it out, so hopefully it helps someone else

ta

Steve

northwestmsp
November 4th, 2016, 05:47 PM
Confirmed it's an issue here too.

sapsford
November 6th, 2016, 07:14 PM
new office updates have come out but haven't resolved it on effected computers

Support Team
November 9th, 2016, 10:41 PM
UPDATE: Good news - a patch that fixes this is now available. In case you face the same problem please contact us at support@... to obtain it.

Background: This issue is caused by of a recent Windows and Office 2016 updates. The patch bypasses this configuration and everything work as expected.

jnahon
November 18th, 2016, 08:39 AM
I am trying to get this update also and have emailed support twice but no response

Support Team
November 18th, 2016, 08:49 AM
@jnahon thank you. We have replied to you with it several days ago, maybe our reply was filtered - have a look. Besides, we've just replied to your other email - in case you won't see it please post here. Thanks.

northwestmsp
December 1st, 2016, 01:35 PM
We applied the patch that was given to us and we're still having confirmed issues with Outlook 2016.

Support Team
December 1st, 2016, 01:49 PM
Thank you for the update. Do you mean that RangerMSP crashes when trying to email/sync?

In the meantime this patch has been sent to plenty of customers that have received the latest Office 2016 and their configuration with it has caused this issue and it has been working great everywhere.

I recommend that you will try to reapply the small patch and give it another try. In case it will not work for you please email us your most recent log files as well as a detailed description of what isn't working exactly. This will allow us to check whether you've been facing something different than what this patch tries to solve.

Hope this helps.