Vanguard vs Fidelity NetBenefits

skhipp

Okay, for the last several weeks, I'm having a ping pong connection. Either Vanguard works and Fidelity NetBenefits does not, or Fidelity NetBenefits works and Vanguard does not.

When Vanguard doesn't work, I'll go in and have to deactivate and then reactivate the connection to get it to work. Once done, the connection works fine - and then the Fidelity NetBenefits connection fails. The same happens in reverse.

This is the strangest thing I've ever seen!!!

NotACPA

Please elaborate upon "doesn't work".  Describe what's happening.  Are you getting any error codes or messages?

AND, what Q product are you running and what BUILD of that product?  Do HELP,
About Quicken for this info.

And, as an aside, the G in Vanguard isn't commonly capitalized.

skhipp

Error code is OL-362-14

2020 Quicken Deluxe
R30.10
27.1.30.10

NotACPA

See this other thread re: OL-364 https://community.quicken.com/discussion/comment/20134102#Comment_20134102

Also, spelling correction made.

skhipp

Wow, I appreciate you spellchecking my post. You must be busy monitoring all these posts for spelling!! ;-)

AWinTx

When downloading transactions to my Fidelity account, I now get the following error:
OL-362-A Your financial institution has downloaded data for an account that does not exist in your Quicken data file

It worked fine this morning before the update. Validating the data file did not fix this as has been suggested on other similar threads.

Build 27.1.30.14

AWinTx

Resetting an account in Vanguard gets it to Update Transactions successfully and then resetting an account in Fidelity gets it to Update Transactions successfully but then Vanguard breaks. This was mentioned in the folllowing thread which was getting an OL-362-14 error:
https://community.quicken.com/discussion/7884147/vanguard-vs-fidelity-netbenefits#latest

So that is a short-term solution if you have to download transactions but is in no way a viable long-term solution.

AWinTx

<a rel="nofollow" href="https://community.quicken.com/profile/skhipp">@skhipp<;/a> - I am experiencing a similar issue, as well, but with R30.14 and OL-362-A error. Resetting one account does the same behavior as what you described (ping pong).



I posted here if you want to monitor it:
[Removed- Self-Referencing] 



<a rel="nofollow" href="https://community.quicken.com/profile/skhipp">@skhipp<;/a> - I think <a rel="nofollow" href="https://community.quicken.com/profile/NotACPA" title="Link: https://community.quicken.com/profile/NotACPA">@NotACPA<;/a> was not being snarky but must have had a spelling error in their original post that they fixed. They have no means to edit your post. That solution (Validate/Repair) had no effect for me.

NotACPA

"They have no means to edit your post."

Actually, SuperUsers CAN edit the posts of other users.

And, @AWinTx , did you try the SuperValidate also?

AWinTx

@NotACPA - just performed a Super Validate and Updating transactions still returns the OL-362-A for Fidelity and Vanguard.

AWinTx

In addition, Deactivating the accounts and then setting them up again to be downloaded had the same effect as Resetting the account in my previous thread.

AWinTx

... and now happening with E-Trade....

NotACPA

OK, for both of you I believe that you need to:

1) take a backup of your data

2) UNinstall  Q using QCleanUI (a windows uninstall isn't sufficient)  https://www.quicken.com/support/using-qcleanui-uninstall-quicken

3) Reinstall Q.

Since the "data validation" processes (i.e.,"data clean") aren't  working,  the next thing to look into  is program corruption ...by deleting and re-installing.

AWinTx

@NotACPA - before trying the uninstall, I re-read the post about performing the Super Validate. I didn't remember closing the app after this finished and then re-opening it before performing an Update. This seems to have corrected the issue. Thanks for your input.