Two factor authentication stops OSU update progress

Andrew snipped-for-privacy@invalid.com wrote in news:rfhhth$585$ snipped-for-privacy@gioia.aioe.org:

I had this proboem with my mother's checking account. The solution was to convince the bank that 2 factor authenticatiuon for Quicken OSU was a bad idea. (Threatening to close the account and move to a different bank helped)

Well, I turned it on because I think having two factor authentication when some 'computer' tries to access my credit union's account *is* a good idea. The implementation within Q could be beefed up a bit to (a) not freeze the other information from being updated and (b) use a little mulitprogramming to allow the end user to continue to work o Q accounts that are 'finished' in the OSU cycle as we once we allowed to do.

Just uncheck the account in the OSU settings. After the OSU is complete, select account in the account list and download manually.

So i finally posted this in the Quicken community today, and received the piece of advice from "Quicken Julio":

"If you haven't already, I would recommend validating the file.

This can be accomplished by going to File > File Operations > Copy. Make sure you do not choose Year End Copy for this procedure. Leave all settings default and hit OK. Once copy is complete, select Open New Copy.

In the New Copy, go to File > File Operations > Validate & Repair > Validate File to ensure there are no lingering issues with the data in this file. If you have issues with Investment account(s) slowness or other data issues with an investment account, be sure to also select Rebuild Lots during this procedure.

After the Validation process is finished, review the Data_Log.txt for messages pertaining to the quality of your data and resolve any that are advised with instructions you should follow.

If you receive the message "Damaged data block" in the Data_Log after the Validation completes, the file is not repairable. We recommend restoring a backup from prior to the date listed on this message."

So I'll give this a shot tomorrow, and see what happens. I certainly am NOT going to restore from a backup since I've had this issue for months and can not forward merge all my additions since I first saw this issue, and indeed perhaps it's just me. We'll see, and I'll report back....

Did the Validate and Repair thing, no joy (although the file size did go down signifantly from 198meg to less than 90meg...ought to keep the new one once I verify it is 'ok' and nothing was dropped from the original good one.

Hi Andrew,

I didn't think that the problem you mentioned about accounts with 2FA messing up a OSU doesn't really have anything to do with a corrupted database. So I'm not surprised. Quicken support always mentions Validate and Repair - it's in their flowcharts. I think it's just a matter of the multithreaded OSU being a little smarter when one download task takes a detour.

John

Andrew wrote:

Did the Validate and Repair thing, no joy (although the file size did go down signifantly from 198meg to less than 90meg...ought to keep the new one once I verify it is 'ok' and nothing was dropped from the original good one.

John, absolutely agree. Just like "reboot" used to be the standard line in early (current?) Windows issues! I'm just not sure how far I want to push this with them, I've got other issues that are more important. Just an annoyance.

And your point about multi-threading also goes to my secondary "Complaint" about not being able to edit accounts (like was able many releases ago) that have already been updated while an OSU is still being done. That too could be some multi-threading and lock contention issue as well depending on the implementation used.