Quicken Mobile refuses to enable a bank: Returns invalid password error even when using correct PW

cdeutsch

Hello. In trying to set up Quicken Mobile, I run into consistent password errors with one of the financial institutions. I know for certain that my login password for the bank is correct; however, when I go to Quicken Mobile & Web and attempt to update my enabled accounts, it continually returns an error that the bank doesn't like the password.

This makes no sense. One Step Update works fine, so why doesn't Mobile with the same password? This particular bank does use multi-factor authentication, but that should not be why it's returning an error that my password is no good.

What am I doing wrong? Quicken desktop version is Windows 32.12; Mobile app running under iOS 14.4.2.

Thank you.

Quicken Anja

Hello @cdeutsch,

Thank you for reaching out to the Community to tell us about your issue, though I apologize that you are experiencing this.

If you haven't already, I suggest resetting your cloud data from your Quicken desktop program and see if that may make a difference. However, before doing so, first, verify that the Dataset name and the File name match each other identically by navigating to Edit > Preferences > Quicken ID & Cloud Accounts (see below). 



If they do not match, please click Edit dataset name and change the Dataset name to match the File name exactly the same (do not copy the file extension: ".QDF"). 

Then, click OK in the preferences window and proceed to save a backup (just in case). From there, please follow the steps below to reset your cloud data.

1. Sign out of your Quicken Mobile/Web app(s)
2. On your desktop program; navigate to Edit
3. Preferences...
4. Mobile & Web
5. Make sure sync shows it's ON and click on Reset your cloud data 
   
6. Wait for the sync reset to finish
7. Navigate to the Mobile & Web dropdown menu 
8. Select Cloud Sync to resync your data and to make sure no errors occur
9. Wait for it to finish syncing 
10. Sign back in on your Quicken Mobile/Web app(s)

Once that is done, see if the issue still persists.

Let us know how it goes!