Principal Connectivity Issue

BTBT

Hello,

I have been having issues with Quicken connecting to Principal for the last 2 months. It seems like it is the same issue as brought up in:

https://community.quicken.com/discussion/7943380/connectivity-issue-principal-funds

It is the OL-332-A error. I tried the troubleshooting at https://www.quicken.com/support/message-when-using-online-services-ol-332-or-ol-330/ and verified my customer id, username, password, and account are correct. That site says to contact the financial company if my information is correct, but they just redirect me back to Quicken since I can log in to their site without problems.

Is anyone else seeing this? It is pretty much exactly what happened last year at about this time as well. There was never a post about the resolution, but it started working after about 3 months after a Quicken update.

Quicken R60.15

Build 27.1.60.15

Any ideas on troubleshooting?

Thanks!

Quicken Anja

Hello @BTBT,

I am sorry to hear that you are experiencing this issue again, and thank you for letting us know that you have already tried the troubleshooting in the corresponding support article.

To confirm and avoid repeating, did you also try the troubleshooting provided to you in the older thread again?

Check back and let us know! Thank you.

BTBT

Hello @Quicken Anja ,

Thank you for the reply. I have not had time to try the troubleshooting from the older thread yet. I should have time in the next few days. I will try it out and respond.

Part of the reason for the post was to see if I was the only person seeing this with Principal or if there were others, so that I could get another data point with troubleshooting.

Thanks,

Brian

BTBT

Hello @Quicken Anja ,

The Principal updates worked today. I haven't done anything different. So, something must have changed on the Principal side or the Quicken side to get it working again.

We can close this ticket.

Cheers,

Brian

Quicken Anja

Hello @BTBT,

Thank you for the update! I'm glad to hear the Principal updates are now working as expected.

If you encounter any further issues, please don’t hesitate to reach back out—we’re here to help!