Zimbra Connector for Outlook on Windows 8 throws "One or more changes you made cannot be saved" "This action could not be completed"
Posted by rbTech Staff, Last modified by rbTech Staff on 27 August 2015 04:03 PM

 Zimbra Connector for Outlook on Windows 8 throws "One or more changes you made cannot be saved" "This action could not be completed"

The title pretty much describes the issue:

Windows 8, or 8.1, Office 2010 or 2013, x86 or x86_64.  Zimbra Network Edition 8.0 through 8.6.

We had 4 separate sites that were experiencing this issue, and it had Zimbra support stumped for months (I wish I was kidding).

We build a lab environment, and began our usual 'isolate one variable at a time' testing methodology.  It took a couple days, but our testing uncovered that were were unable to open the Windows8 Credential Manager.

After some Google-fu on the Microsoft site, our tech determined that there was an update for the credential manager that conflicted with another piece of software commonly in use on Zimbra sites: Samba.

KB3000850 is the cumulative update for Windows 8.  Among other things, it breaks backward compatibility with Samba 3 domains (e.g. NT4 style domains).  Which are in place at all 4 of the sites were were having trouble with.

Uninstall KB3000850 check that the credential manager is working properly and launch Outlook, and Voila!  Connection success.  Outlook may fail the first time you open it. Open it in safe mode if it asks, let it sync, then close and reopen outlook and it should be working.

Follow up from Hollend:
I have it narrowed down to three updates. KB3000850, 3038562, 2992611. Any one or all of these need to be un-installed from windows 8 machines on samba domains. The tell tale sign is that windows credential manager won't work (Credential Manager in the metro screen), and fails with an error on launch. After the un-install it should work. Then you will be able to authenticate zimbra against the server. 

If you are unable to uninstall the updates there is a registry fix that will solve the issue as well.  Open the registry editor and make the following path change on the local machine.


add this registry entry or modify it if it already exists

You will need to make sure you set the "decimal" value to 00000001 which will in turn set the hex value.  Restart the machine and then check that the credential manager is working properly.




Credit where it's due:  Hollend Ritondale [email protected] owned this one through resolution, and deserves credit for finding the ultimate resolution.

(1 vote(s))
Not helpful

Comments (1)
Jonnie Kennedy
26 February 2016 04:27 AM
You a total life saver. worked like a dream with Windows 10, MS Office 2016 giving the above error.
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).