How to fix Vanguard Investment Account Download?

Midwest_Engineer

Of all of my investment and banking accounts, my Vanguard Brokerage (only) investment account fails one-step update on QL-293-A every single day when I do the update. However, if the account is then "reset" within Quicken, the one-step update succeeds (with no other changes having been made). Any subsequent one-step update immediately afterward also succeeds. Yet the next day, the cycle repeats with QL-293-A again, for this one account. This pattern has persisted for months, without change. In desperation, I turned off the one-step update for this one account, then turned it back on again. All to no effect -- the pattern still repeats every day. Please advise how this behavior can be ended.

miklk

It is an ongoing problem with Vanguard.
You can work around it by using gear icon on top right and do Update Transactions which usually works without error.

Look at this thread:
https://community.quicken.com/discussion/comment/20130770/#Comment_20130770

DJW

> @Midwest_Engineer said:
> Of all of my investment and banking accounts, my Vanguard Brokerage (only) investment account fails one-step update on QL-293-A every single day when I do the update. However, if the account is then "reset" within Quicken, the one-step update succeeds (with no other changes having been made). Any subsequent one-step update immediately afterward also succeeds. Yet the next day, the cycle repeats with QL-293-A again, for this one account. This pattern has persisted for months, without change. In desperation, I turned off the one-step update for this one account, then turned it back on again. All to no effect -- the pattern still repeats every day. Please advise how this behavior can be ended.
>

I have the same issue with Vanguard\Quicken.
It has been ongoing for months. The error occurs consistently on the scheduled update. If I manually update only the Vanguard account generally the error does not occur, the fail rate is ~15%.

I have been running the 'Report a problem' wizard in One Step Update on each occurrence since the beginning of the year. <crickets>

Is there a way to follow up on a 'report a problem' filing?

DJW

Issue with Vanguard\Quicken.
I am running the latest subscription version.

This error has been ongoing for months. The error occurs consistently on my daily scheduled update. If I manually update only the Vanguard account generally the error does not occur, the fail rate when done manually is ~15%.

I have been running the 'Report a problem' wizard in One Step Update on each occurrence since the beginning of the year. <crickets>

Is there a way for a user to follow up on the status of a 'Report a problem' filing?
Is there an open ticket on this error?

Quicken Francisco

Hello @DJW

Thank you for reaching out on the community and telling us about your issue. I do apologize for the issue you're having. We are currently experiencing issues with Vanguard returning a 293 error when trying to update accounts. We're currently do not have an ETA as the error is a direct connect issue. Some others have had luck with the 293 error article so I'll leave that down below for you. I do apologize for any inconvenience this has caused. 

https://www.quicken.com/support/error-when-using-quicken-online-services-ol-293-or-ol-294

Thanks,

Quicken Francisco

DJW

> @Quicken Francisco said:
> Hello
> @DJW
>
> Thank
> you for reaching out on the community and telling us about your issue. I do apologize for the issue you're having. We are currently experiencing issues with Vanguard returning a 293 error when trying to update accounts. We're currently do not have an ETA as the error is a direct connect issue. Some others have had luck with the 293 error article so I'll leave that down below for you. I do apologize for any inconvenience this has caused. 
>
> https://www.quicken.com/support/error-when-using-quicken-online-services-ol-293-or-ol-294
>
>
> Thanks,
>
> Quicken
> Francisco

Thank you for the prompt response,
I have tried all the items suggested in the link above.
Vanguard refers users experiencing the problem to this Quicken page;
https://community.quicken.com/discussion/7881217/vanguard-account-gets-a-ol-293-a-error/p1
This Vanguard referenced Quicken page does not contain a solution and was locked sometime late last year.


What is the Quicken mechanism for a user to follow up on the status of a 'Report a problem' filing?

Is there an open ticket on this OL-293 error with Vanguard? The ticket number will be helpful when I speak with Vanguard.
Dan

Quicken_Tyka

Hello @DJW

Thank you for the response and the additional details. The Report Problem forms will not receive a response and are different than contacting support, I apologize for the confusion.

Vanguard refers users experiencing the problem to this Quicken page;
https://community.quicken.com/discussion/7881217/vanguard-account-gets-a-ol-293-a-error/p1
This Vanguard referenced Quicken page does not contain a solution and was locked sometime late last year.

This post is still open and active, there are several pages you will need to navigate to the last page to see the latest comments. You will find a ticket number on that post, CTP-1144 however this is a ticket number for Quicken and will not be meaningful to Vanguard.

We are actively working with Vanguard on fixing this issue, unfortunately, it is currently still ongoing with no exact ETA however we are working closing with Vanguard and have made contact with them recently to move towards a solution.

I hope this helps to clarify!

-Quicken Tyka

[Edited]

DJW

> @Quicken_Tyka said:
>
> We are actively working with Vanguard on fixing this issue, unfortunately, it is currently still ongoing with no exact ETA however we are working closing with Vanguard and have made contact with them recently to move towards a solution.
>
> I hope this helps to clarify!
>
> -Quicken Tyka
>
> [Edited]
Tyka,
Thank you for the response,
I spent ~30 minutes with Vanguard Level 2 Quicken support yesterday.
(Took ~60 minutes to get there...)
I did not receive any joy...

markus1957

I'm not convinced this is a Vanguard problem; it looks more like a Quicken/Intuit issue or at least one that Quicken could fix.

Once or twice a week Vanguard completes successfully.  100% of the time, the successful OSU shows in the Connection Log that the Branding server is contacted first.  The unsuccessful OSUs all begin with the "Marketing session" skipping the Branding server contact.

If Quicken forced a connection to the Branding Server each session, Vanguard downloads would always be successful; barring other unrelated issues.  This can be verified by manually forcing a Branding update in Tools>Online Center before running OSU.  Setting the flag to force a Branding update before running OSU always results in a successful Vanguard download.

Successful Vanguard OSUs always begin with this Branding update being logged in the Connection Log-
20210122 08:32:35: QFN: Beginning send to https://ofx-prod-brand.intuit.com/qw2800/fib.dll

20210122 08:32:35: QFN: End send to https://ofx-prod-brand.intuit.com/qw2800/fib.dll, netstatus 0

20210122 08:32:35: QFN: Beginning send to https://vesnc.vanguard.com/us/OfxProfileServlet

20210122 08:32:35: QFN: End send to https://vesnc.vanguard.com/us/OfxProfileServlet, netstatus 0

Unsuccessful Vanguard OSUs always begin directly with the Marketing session-

20210121 22:55:54: Marketing session sending to: https://msa.intuit.com/banking/fimkt/basic/intuit_BASICmac.ini

20210121 22:55:54: QFN: Beginning get from https://msa.intuit.com/banking/fimkt/basic/intuit_BASICmac.ini

20210121 22:55:54: QFN: End get from https://msa.intuit.com/banking/fimkt/basic/intuit_BASICmac.ini, netstatus 0

20210121 22:55:54: QFN: Beginning send to https://vesnc.vanguard.com/us/OfxDirectConnectServlet

20210121 22:55:55: ***QFN kQFFinished: returns 67305972

20210121 22:55:55: We’re sorry, the server is experiencing an internal error. Try again now, or wait and try later.

20210121 22:55:55: QFN: End send to https://vesnc.vanguard.com/us/OfxDirectConnectServlet, netstatus 30

Quicken Sarah

Hello @markus1957

Thank you for sharing your thoughts and feedback on this ongoing issue.

Our teams are communicating and working with Vanguard directly and believe they may have traced this issue back to a session cookie in Vanguards system, which is why the second attempt at updating is most often successful for users.

We'll continue to update the ongoing Alert for this issue as more information becomes available and in the meantime, I hope this additional information is helpful.

Sarah

Larry Nichoalds

I have been affected by this Vanguard since the beginning, months ago now. I see that markus1957 has documented the issue quite nicely, but I have never seen a response to his research efforts. If his analysis is correct it seems that Quicken could fix this by forcing a branding update. So why is this not happening?

Chris_QPW

Larry Nichoalds said:

but I have never seen a response to his research efforts. If his analysis is correct it seems that Quicken could fix this by forcing a branding update. So why is this not happening?

Did you read Quicken Sarah's post right above yours?

DJW

FYI: This morning my scheduled update with Vanguard was successful.

Carl S

I have had problems with downloading from Vanguard for years and they don't seem to want to fix it. Last time I called their tech support, they confirmed it by remotely connecting to my computer and the tech said they need to trouble shoot it further and would get back to me a about a month! NEVER DID! It's been a year.

KatMom

I've been having problems downloading either through Quicken or directly from the Vanguard website since July 2020. I've spent so much time on this! Very frustrating!

PBK77

Followed 2/17 fix posted by Quicken Sarah. It worked for me.

markus1957

The changes made broke something else. It might work for one account login set, but if you have two or more Vanguard login sets of accounts in your data file, it will fail with OL-220.

For me, the fix is a step backward. Try Again was easier than having to close Quicken and reopen it to get the failed login to run using update now in the account register. One user in another thread has 4 logins for Vanguard and needs to close/open Quicken and run one set at a time.  This points to the session cookie fix causing more problems than it solved.

BK

@Quicken Sarah and Quicken team,  I would like to echo what @markus1957 wrote in both comments.  Having multiple Vanguard account logins, I had gotten used to clicking on "Try Again" for over a year and worked like a charm and took only 5 seconds.  Now I don't have that option after this fix/change and therefore I have to close and open Quicken multiple times and update Branding for every Vanguard account.  What used to be a 5 second one-click workaround has now turned into minutes of involved painful process unfortunately.  Thank you for your continued effort to investigate and resolve this.