July 6, 20205 yr I noticed sync errors across my Windows/iOS devices and was given the message, "Password of data on <redacted> is required." After multiple failed attempts to recover, I completely deleted my data and created a new sync. That worked only for a few minutes (I was able to sync one other device), then all of my devices started giving the same error again, even the one that created the sync.
July 6, 20205 yr Author Realized that this forum (which is where we are directed when selecting 'Support Forum' from the Help menu in the Windows app) is a little off the beaten path. This is a know issue with no current fix as mentioned by the Dev team here: https://discussion.enpass.io/index.php?/topic/17195-sync-lost-password-of-data-on-onedrive-is-required/page/3/
July 7, 20205 yr Hi @Bergnificent, Sorry for the trouble you are going through. We regret the inconvenience and understand that you’re facing issues with OneDrive sync. Please follow the below steps to restore the sync: Take a manual backup of the data on both the devices. Disconnect the sync on all devices. Remove the folders Enpass and Enpass1 on OneDrive account. Log in to the site https://account.live.com/consent/Manage with the same Microsoft account and delete all the permissions for Enpass. Re-set up the sync with OneDrive on all the devices and check. If the issue persists, please let us know.
July 30, 20205 yr Author Your workaround seems to be working. One thing to note. My Enpass folder used to be in the root of my OneDrive. At some point, an App folder was created which contained Enpass and Enpass1 folders.
July 31, 20205 yr Hey @Bergnificent Thanks for notifying us. However, we are already aware of it. To know more, please refer to this link and let us know if you have any queries. Thanks.
August 18, 20205 yr I do have the exact same issue since recently on all my devices. I will try the workaround – but I hope you can find out what caused this error in the first place.
August 18, 20205 yr Hi @cma, Sorry for the trouble you are going through. Our team is working on this issue. Hopefully, the fix will be available soon. Meanwhile, please follow the troubleshooting steps and revert to us if the issue persists.
Create an account or sign in to comment