Updates went from minutes to hours ??

In the middle of last week one step udpates that used to take a few minutes all of sudden went to hours, or me having to abort it.

I don't think I changed anything on my end, so I' wondering if anyone else is seeing anything like this.

Right now its been running for 10 mintes, the top entry (Amex) says "Updating financial instituion information...", all the other are "waiting..." So it seems like the delay might be coming from the Quicken servers.

When I've stopped it and restarted, most of the time it didn't help, and eventually it seemed to update most of the accounts.

Any thoughts?

Thanks

Reply to
TM
Loading thread data ...

"TM" wrote

Or just as likely, based solely on the info you provided, is that the problem is with the Amex servers.

You didn't specify your Quicken version, release, or operating system.

I've just done a One Step Update for many accounts at multiple financial institutions (none with Amex though) with Q2010 RPM R10 and Q2011 RPM R8 running under Windows XP Pro SP3. I experienced no problems.

I would uncheck Amex from the OSU financial institutions selected for downloading and try another OSU.

If that works normally, you could try doing an "Update Now"* for Amex.

[* "Update Now" is in the "Account Actions" drop down for an account (in Q2010 and later). The "Downloaded Transactions" tab should also have an "Update Transactions" button that does the same thing.]
Reply to
John Pollard

If it is, it's over. I just updated my American Express account and it took 12 seconds from the time I clicked update.

Reply to
nobody

Thanks for that idea... tried OSU now without Amex, everything updated in under a minute, but then tried Amex by itselfand that went quickly as well, so I'm not sure I proved anything.

Will try again in the morning when I normally do updates, see if that is more definitive. This morning's udpate finally finished 2 1/2 hours later, but the time stamp on most of the updates was at the very end, which would support the thesis that Amex is the bottleneck.

BTW, its Q2011 R8, Windows server 2003.

TM

Reply to
TM

"TM" wrote

If you used "Update Now" (or "Update Transactions") to update Amex, the process is not exactly the same as a One Step Update.

One Step Update aggregates your update request with the OSU requests of other users, so its easier to overload the financial institution's servers.

"Update Now" sends update requests individually; no aggregation.

But since at least one other user has successfully done a One Step Update with Amex after you reported, I'm thinking that one way or the other, you should be ok.

Reply to
John Pollard

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.