Vanguard Error Code 16503 - AGAIN (QMAC)
This was an issue for weeks and weeks earlier this year and I thought it had been corrected however I got the Error Code 16503 again this morning. Please tell me this isn't going to be an ongoing issue
Comments
-
This issue has resurfaced this morning:
Vanguard
There was an unknown error trying to update this connection. Please try again later. (16503)
Server Message: HTTP-400 Error from Vanguard0 -
the vanguard error is back. 16503. i kind of thought it was odd that we did nothing and error went away. guessing they backed out the previous security change when they could not find a solution for third parties to connect. now they have put that security change back in. hoping there is a solution for third parties to connect.
0 -
Same - Vanguard error is back "There was an unknown error trying to update this connection. Please try again later. (16503)".
0 -
Ditto - same: "There was an unknown error trying to update this connection. Please try again later. (16503)".
0 -
Ditto
0 -
Hello All,
Thank you for letting us know that the issue has returned!
We will 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.
(CBT-623)-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
I have been getting this error all morning on 3/28/25. I hope Vanguard is taking steps to prevent these frequent disruptions. My confidence in Vanguards technological abilities is quickly fading. I'm glad I have some funds at Fidelity as a backup.
1 -
having same error
There was an unknown error trying to update this connection. Please try again later. (16503)0 -
Hello All,
There is now a Community Alert for this issue:
Though we do not currently have an ETA, you can bookmark the alert linked above to get updates when available and to know when the issue is resolved. If you do not see the bookmark icon at the upper right, please make sure you are logged into the Community.
Thank you!
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
This is a New error; not the one we were experiencing in the last couple of months.
Quicken Mac Subscription - iMac - Quicken Mac user since 19940 -
Hello @newcastlelinda,
Thank you for letting us know you're also impacted by this issue. I merged your discussion with the active discussion on this issue. There is already a Community alert out for this issue. I recommend bookmarking it to track the status of this issue. You will find the link in my earlier post (linked below).
Thank you!
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
This is a New error; not the one we were experiencing in the last couple of months.
@newcastlelinda If you look at the top of the screen shot you posted, you will see that the error message at the top is 16503, the same error code as before. The "new" HTTP-400 error is just a message from the Vanguard server basically saying "I hear you, but I cannot respond because there's something wrong with your request." The 16503 is the internal Quicken error code for when Quicken doesn't receive the data it expects from the financial institution. So it's really the same "no one's home" message as before. 😉
My guess (with no inside knowledge or insight) is that Vanguard took their Direct Connect connection offline again to do further updates or fixes to their code or configuration. Hopefully this downtime will be short-lived.
Quicken Mac Subscription • Quicken user since 1993-1 -
Here we go again…
0 -
In less than a month, the issue with Vanguard has resurfaced for the second time. I am not sure where the problem lies, but this situation is definitely aggravating.
Quicken (Mac) is showing an error code 16503 not sure what that means.
0 -
Same. Error code 16503. Two days now.
0 -
Same issue again here. I hope the fix will be quick in (Quicken?) arriving and not require us to delete a pile of newly-added redundant or incorrect d/led transactions like last time.
0 -
Add me to the lists getting the 16503 error on Mac.
0 -
Same here. 16503 for 3 days. Reported to Quicken
0 -
I too am in the 16503 purgatory level of Dante's [Removed - Language]. First it began with the Citibank reconnect earlier last week. Then it morphed into Vanguard no longer connecting. When I try to reestablish the Vanguard connection, I see the Mac version 16503 OFX error. So as of today, I can no longer connect with Citibank or Vanguard. Has anyone found a viable alternative to Quicken that can import the data? After 30 years I've able had it with Quicken. Thank you.
1 -
Getting error again. PLEASE FIX.
0 -
I had this starting yesterday. I called Vanguard this morning and the rep checked and he said it hadn't been reported. He made a report. I also uploaded data to Quicken support. Very frustrating!
0 -
Very frustrating. I don't care whether this is a Quicken or Vanguard issue, both of their reputations get hurt, so they need to work together better to get this permanently fixed.
0 -
Still an issue as of March 31, 2025. Now the underlying cause is different: "HTTP-400 Error from Vanguard". Anyone working on this?
0 -
Hello All,
If you are still encountering issues connecting with Vanguard, please post to this discussion to let us know exactly what issue you're seeing. Additionally, please navigate to Help>Report a Problem and send a problem report with log files attached so that we can further investigate the issue.
Thank you!
Quicken Kristina
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
I will send the report separately but still getting the 16503 error on Mac.
1 -
Exactly the same as the last three days, error code 16503
1 -
This issue was reported several days ago (just look at the date of the first post here) and has not been resolved. Was working fine before last Friday for me.
0 -
Error code 16503 on MACOS. Getting the error for multiple files and accounts. As others have noted, worked fine until last Friday.
1 -
I'm still getting the 16504 on 3/31/25 at 8:02pm EST.
0 -
I'm continuously getting the same error code 16509 the last three days on multiple accounts. I began receiving this code on Friday, March 28th.
0
