Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
Can't connect to Wells Fargo Asset Management account

Yesterday when I updated accounts, this account didn't update and I received a message that said "Incorrect Customer ID or Password/PIN. When I clicked the "Set Up" button and reentered the username & password, I got the same message. I visited the Wells Fargo website using the same username & password and was able to log in. Today I'm getting the same message. So I deactivated the connection and tried to set it up again. I'm getting the same message in Quicken but I can log into their website.
It may be worth noting that when I opened Quicken yesterday that there was a notice to update Quicken to version 6. I did that before I attempted to update accounts.
Using Version 6.0.0 (Build 600.37019.100)
macOS 10.15.7
Using Version 6.0.0 (Build 600.37019.100)
macOS 10.15.7
Quicken Mac Subscription • Quicken user since 1994
Tagged:
0
This discussion has been closed.
Comments
So it is being worked on.
Would you be able to check with the connectivity team and get an update on this?
Thanks for reaching out! I checked the status of the ticket and it is still "in progress" with no ETA on a resolution available yet.
Our teams, service providers and the financial institutions are working together to resolve this as quickly as possible, but I suspect the Thanksgiving holiday may have added some extra delay as well.
I'm following the ticket and will share any updates and/or resolution to this error as they become available.
Thanks again,
Sarah
(CTP-1307)
Thanks for the update and ticket monitoring.
I just tested this morning to see if it would connect and SUCCESS. Seems to be fixed even though Quicken Sarah hasn't updated us.
<!-- ***** SEND to https://financialdataaggregation.api.intuit.com/soap/api at 12:50:59 on 20201221 ***** -->
CCLogonRequest : Request ID 1051759380 for BID 20 (Abri Credit Union)
I'm on Windows running version 30.14 build 27.1.30.14.
I'm running Windows version R30.21 build 27.1.30.21.
It's time to get this fixed.