----------------------------------------------------------------------------------
@MSGID:
<2ae12290-3509-423e-81da-c1ab45128f91n@googlegroups.com> c84065fb
@REPLY:
<2320546b-fa6c-43c7-b355-8f5158e061c2n@googlegroups.com> 50e694e6
@REPLYADDR John Pollard <8plus7isf@gmail.com>
@REPLYTO 2:5075/128 John Pollard
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<8rgefi5f5ee5m15ps1f1isdpba9rjqse61@4ax.com> <73cddabe-a636-423f-9933-08d58b712bc7n@googlegroups.com>
<d4fe823d-e971-455b-b9d6-7de002e53006n@googlegroups.com> <v40ffilatk7icjjnkrspkjaepft8dckmku@4ax.com>
<288d9d86-16a7-4fdb-81b5-4bcf983aff09n@googlegroups.com> <48d5bd7e-c345-4bf3-8be3-2757713cad45n@googlegroups.com>
<sb7ffi1pouhgnmf1fmqjdbimfrfe40pso0@4ax.com> <r52hfih3djmlvb37si40chiape586rb5t0@4ax.com>
<8cc0a10f-b9e2-4776-bdd4-6271dc0565c4n@googlegroups.com> <778hfidrrnu4p6qcv1movmdnet1v9ds7st@4ax.com>
<2320546b-fa6c-43c7-b355-8f5158e061c2n@googlegroups.com>
@RFC-Message-ID:
<2ae12290-3509-423e-81da-c1ab45128f91n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Wednesday, September 6, 2023 at 12:56:39 PM UTC-5, John Pollard wrote:
> The last resort I can think of is to
> Restore the most recent backup from
> a QDF file that did not experience the problem.
Tonight (09-06-23) @ 20:08 CDT time I did a One Step Update.
I have checking, savings and investment accounts at Schwab -
plus accounts with multiple other financial institutions, including
BofA, Discover, Chase, American Express, Vanguard and Fidelity.
My OSU hung and I finally used Task Manager to kill Quicken.
The Schwab updates did not complete; the others did -
it appears the Schwab update was what was preventing
the OSU from completing.
I had done an OSU earlier today (at around 13:00 CDT) and
everything seemed to work ok. The OSU completed on its
own; the accounts that had activity available for download
(including Schwab) received their expected transactions.
So when I responded in this discussion earlier today, it did not
dawn on me that there could be a problem with Schwab. But after
my experience tonight, I`m thinking there is something going on
with Schwab.
[Note: I have had no "conversions" of non-Schwab accounts to
Schwab accounts (nor created ANY "new Schwab accounts) for
many months, so today`s issue does not appear to be related to
transferring holdings to Schwab.
Or creating ANY new Schwab accounts for downloading.]
Sometimes when OSU hangs, and Quicken must be aborted; it`s
just one financial institution that is causing the problem.
In those instances, it is may be possible to use "Update Now"
(or "Update Transactions") to update the non-problem financial
institutions individually - while waiting for the problem financial
institution`s problem to get fixed.
I don`t know whether that will help in your situation,
but it may be worth a try.
[My everyday Quicken release is R50.16 which is the release
I referenced for all my earlier posts in this discussion.
Tonight I also tested an OSU with R51.12; and it did not exhibit
the same problem. My OSU completed without a hitch.
Since I don`t try to keep my test file up to date, so I can`t be
certain that everything downloaded - but the fact that Quicken
did not hang is interesting to me.]
Sorry I`m not up to digging any further into this at the moment.
You may want to monitor the Quicken Community (as I will) to
see if there are any others having the problem, and to see
whether there is any acknowledgement from Quicken.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441