Vanguard Error Code: 16503 (QMac)
Answers
-
Ditto - same: "There was an unknown error trying to update this connection. Please try again later. (16503)".
0 -
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
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 -
Today it's back.
"There was an unknown error trying to update this connection. Please try again later. (16503)"
3 -
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 -
Issue started occurring again this morning for Q Mac
3 -
Likewise. This cropped up again, after being fixed for several weeks. Error 16503
2 -
Me Too. My Q Mac program reported the old error again after being fixed since early March
3 -
Similarly I am getting an error downloading from Vanguard today after the earlier fix.
This time the error is slightly different . the message reads…
There was an unknown error trying to update this connection. Please try again later. (16503)
and in the details it shows
Server Message: HTTP-400 Error from Vanguard
RoadBiker
2 -
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 -
Quicken & Vanguard are aware of the problems occurring today:
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 -
This 3/28/2025 Quicken Support post says, "You may see… errors 15500 or 2003 in Quicken for Mac."
I'm getting error 16503 in Quicken for Mac.
1 -
Yep, I'm getting error 16503 also.
Quicken Mac Subscription • Quicken user since 19940 -
This issue just reared its ugly head again, JFC, Vanguard, get your shite together .
0 -
"There was an unknown error trying to update this connection. Please try again later. (16503)" Same error as weeks ago. Disappointing.
Quicken Mac Subscription.
1 -
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 -
Error persists for 2 days now. I was hoping it was a maintenance issue and would be resolved by now. I don't understand why Vanguard customer service won't tell its customers what the situation is. Not a good way to keep customers.
1 -
FYI: In a QWin thread on this latest Vanguard issue, several users are now reporting that as of this morning the issue appears to be resolved since they were able to reestablish downloading, again. Hopefully, this is an indication that the issue is now resolved for QMac users, too, or soon will be.
Quicken Classic Premier (US) Subscription: R61.20 on Windows 11 Home
1 -
Thank you for letting us know that the Vanguard issue seems to be resolved for QWin users,@Boatnmaniac.
Unfortunately, in QMac I'm still getting, "There was an unknown error trying to update this connection. Please try again later. (16503)"
1 -
On the Mac I got price updates end of day yesterday as usual. I'm still getting the error however. No new transactions downloaded.
Seems different than last time.
… Jeff
1 -
@JTS Price updates for securities — alll securities — come from a third-party data provider; it's a completely separate process from connecting to a financial institution to download transactions.
Quicken Mac Subscription • Quicken user since 19931 -
Last time QWin users were getting the OL-295-A error code. This time QWin users were getting the OL-301-A error code. This indicates that the two issues (at least for QWin) are different. In fact, the Moderators split the OL-301-A comments off into a separate thread from the OL-295-A error code, again, indicating that the two issues are different.
I'm assuming that it is different this time for QMac users, as well, but why then is the same error code used for both? IMO, this makes it much more difficult to have a meaningful discussion regarding the issues since there is no clear differentiation between the two. I'm just hoping that whatever started working for QWin users today will start working for QMac users, as well, very soon.
Quicken Classic Premier (US) Subscription: R61.20 on Windows 11 Home
2 -
The error from Vanguard is different. Last time we got…
Error 404 Not Found is an HTTP status code that indicates that the server could not find the requested webpage. This typically happens when:
• The URL is incorrect or has been mistyped.
• The webpage has been moved or deleted.
• The server is not configured properly to handle the request.
This time we're getting…
HTTP 400 Bad Request is a status code that indicates the server cannot process the request due to a client-side error. This can happen for several reasons, including:
• Malformed request syntax – The request was not formatted correctly.
• Invalid request parameters – Missing or incorrect data in the request.
• Large request size – The request is too big for the server to handle.
• Corrupt or outdated cookies – Stored cookies might interfere with the request.
2 -
I don't know if this is relevant, but yesterday when I tried to manually log in to the Vanguard website, I get a message along the lines of:
"You can’t log in using a script. For your security, we stop any logins that act like bots. Stop running your script before trying again."
The next time I tried, I got in OK. Maybe Vanguard has added some extra security that is stopping Quicken for Mac?
1
