T.Rowe Price update getting OL-332-A
Getting the OL-332-A error when trying to update T.Rowe accounts this morning. Login info is correct and still works to log into their website.
Comments
-
I validated password is correct by logging in to the web site. It has not changed, and TRP Brokerage has been fine in Quicken up until today.
I get this:
Clicking the FixIt button does not good, that goes to a bad page!
I also tried adding the Brokerage account to a new data file, and I get the same error - bad password. Can anything be done?
0 -
Similar —- not recognizing login and asked me to set up account. Comments on password not being correct.
0 -
Same with me - but this happens every once in a while and then corrects in a few days. Unfortunately it's annoying.
0 -
Hello All,
First, please review this support article regarding error OL-332.
We will also be forwarding this issue to the proper channels to have this further investigated. However, we request that you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation. It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.
While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.
We apologize for any inconvenience in the meantime! Thank you.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
I'm also experiencing this same T. Rowe Price connection problem today with a TRP Brokerage account. It had worked fine as of a few days ago. I have also confirmed that my login credentials still work fine when I go directly to the TRP website.
0 -
Working for me now!
0 -
Trying this morning it appears to be fixed.
0 -
@Don Awalt & @jbrown08322 Thank you for providing an update! I'm glad to hear the issue has been resolved for you both. 🙂
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0