Fifth Third OL-332-A Error, cannot log into bank account for downloads
I have a situation where I cannot log into my bank account at Fifth Third after a long history of no issues. I'll try to simplify the facts but essentially I get a "Your log in information is incorrect" OL-332-A error. This started several weeks ago after I opened a new business account at the bank and the banker adjusted my online access to include all business and personal accounts. In doing so, he provided a temp password. However, since all accounts showed on my phone app, he said not to use it and it expired. Now, even though I have the same browser password, Q won't connect. By the way, access via Q was set up on Direct Connect but using the same PW I used to log into the browser access. I have spent a total of 4 hours with Q support and 1+ with the bank. The following has been attempted:
---Fifth Third Bank
1. Cleared all security blocks
2. Checked times of access by Q to confirm contact
3. Multiple password resets (both to my old PW and using a very different PW)
---Quicken Support
1. Accessed Direct Connect (DC) from multiple methods, i.e. Tools-Account List, Tools-Add Account.
2. Complete erasure of all Q stored PW.
3. Installed a "test" Q file that was completely clean and got the same error.
4. Restored a back up from 1-2 months back that was a working copy and got the same error.
5. Uninstalled Q and reinstalled clean version.
All with the same error.
Update: while writing this I tried again using my current MyQuickenData file and, guess what, it worked. Once. I was able to restore all 5/3 accounts up to this date (7/22/20). However, I did not save the PW in the Vault, so, when I went to save the PW in the Vault, Q informed me that Quicken did not allow PW over 12 characters. It then accepted the PW in the vault and promptly gave me the same error.
Last piece: the last Q tech I was on with informed me that I needed a separate and distinct Direct Connect password. That I cannot use the same PW that I was to get into my browser bank access. Side note: we did try using the web express mode and that did not work.
Any help?