Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO

new Windows R26.15 - breaks online downloads

New version R26.15 transaction downloads (Direct Connect) is broken. I had to revert to the previous version, which works fine.
The quite useful Release Notes information? Fixes various bugs.
I wonder what the real problem is?

Comments

  • leishirsute
    leishirsute Member ✭✭✭✭
    How do you revert to previous version?
    Quicken Deluxe Subscription; Windows 10 Pro 64-bit
  • splasher
    splasher SuperUser ✭✭✭✭
    -splasher  using Q since 1996 -  Subscription  -  Win10
    -also older versions as needed for testing
    -Questions? Check out the  Quicken Windows FAQ list
  • splasher
    splasher SuperUser ✭✭✭✭
    I reverted and restored a backup from prior to the update and both Discover Card and Discover Bank still fail with OL-295-A.  Chase CC and Edward Jones work without error.
    I don't think it is a R26.15 as something else has changed since R26.14 fails also.
    I will be upgrading back to R26.15.
    -splasher  using Q since 1996 -  Subscription  -  Win10
    -also older versions as needed for testing
    -Questions? Check out the  Quicken Windows FAQ list
  • markus1957
    markus1957 SuperUser, Windows Beta Beta
    edited April 2020
    It's happened to me a few times, this is not the first time.

    Discover Bank and Card (and a few other direct connect FIs) use a newer process called secure ofx.  The patches can sometimes break the connection information that makes it work.  The information gets updated often but if you have already run OSU and then install the patch, Quicken has a way of including the older method connection information in the patch.

    Look for a file called fidir.ini and change the date to a week earlier.  Save the file, close and open Quicken, run OSU again.

    C:\ProgramData\Quicken\Inet\Common\Localweb\Banklist
  • GeoffG
    GeoffG SuperUser ✭✭✭✭✭
    I updated to R26.15 yesterday and all connect without issue (DC & EWC). PNC CC still is blocked by PNC, but that has nothing to do with the update.
    user since '92 | Quicken Windows Premier - Subscription | Windows 10 Pro version 20H2
  • leishirsute
    leishirsute Member ✭✭✭✭
    Thanks.  Finally I realize how to get earlier mondo version.
    Steps I used:
    Get version number needed at:
    https://www.quicken.com/support/subscription-release-quicken-windows-release-notes
    Then copy current mondo patch link from "Download the US Mondo Patch Update" :
    https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product
    Paste the link in my browser and replace the latest release number with the my desired release number and submit.
    A window pops up to download the older version.

    Quicken Deluxe Subscription; Windows 10 Pro 64-bit
  • splasher
    splasher SuperUser ✭✭✭✭
    Thanks.  Finally I realize how to get earlier mondo version.
    Steps I used:
    Get version number needed at:
    https://www.quicken.com/support/subscription-release-quicken-windows-release-notes
    Then copy current mondo patch link from "Download the US Mondo Patch Update" :
    https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product
    Paste the link in my browser and replace the latest release number with the my desired release number and submit.
    A window pops up to download the older version.

    It is easier to just download and save them locally as they are released.  You can't count on them always being there in the future.  I have a large collection of them.
    -splasher  using Q since 1996 -  Subscription  -  Win10
    -also older versions as needed for testing
    -Questions? Check out the  Quicken Windows FAQ list
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    These kinds of problems seldom have to do with the patches, especially Direct Connect, because since the protocol doesn't change, there isn't any need for a change in Quicken.

    The problem is most likely instead the pushing of the financial institution list or other such "data" which happens much more often.  The default is to check for these kind of changes every 4 days.

    As such it can look like the patch caused the problem just because they both happen about the same time.

    Note I just updated to R26.15 and all of my downloads are working fine.
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
  • :) I just updated to R26.15 this morning. All FI connections work fine, including Discover Card/Bank.
  • markus1957
    markus1957 SuperUser, Windows Beta Beta
    edited April 2020
    @Chris_QPW regarding direct connect, if you look at the connection log you will find that there is a new method (ofx-secure-plus) of direct connect being utilized for some FIs.  Discover is one of them.

    This patch and others before it are sometimes getting loaded with incorrect connection configuration information that tries to connect using the older direct connect method.  If you have already run OSU that day with the previous version, the incorrect data will not get updated.

    I have found if I back date fidir.ini about a week, close/open Quicken, OSU will run successfully.   Otherwise, you have to wait for a day (or so) until the configuration information gets automatically updated as it periodically does. 

    Users then think Quicken fixed the connection issue for their FI, but all that really happened is that Quicken downloaded the configuration data that should have been included in the patch.

    Failed connection log entry after applying R26.15 Mondo patch-
    20200417 11:44:35: Marketing session sending to: https://msa.intuit.com/banking/fimkt/basic/QWBasic.ini
    20200417 11:44:35: QFN: Beginning get from https://msa.intuit.com/banking/fimkt/basic/QWBasic.ini
    20200417 11:44:35: QFN: End get from https://msa.intuit.com/banking/fimkt/basic/QWBasic.ini, netstatus 0
    20200417 11:44:35: QFN: Beginning send to https://ofx.discovercard.com
    20200417 11:44:35: ***QFN kQFFinished: returns 67305875
    20200417 11:44:35: The application has been denied access to the server. Try again now, or wait and try later.
    20200417 11:44:35: QFN: End send to https://ofx.discovercard.com, netstatus 15

    Successful connection log entry after back dating fidir.ini-
    20200417 11:46:57: Marketing session sending to: https://msa.intuit.com/banking/fimkt/basic/QWBasic.ini
    20200417 11:46:57: QFN: Beginning get from https://msa.intuit.com/banking/fimkt/basic/QWBasic.ini
    20200417 11:46:57: QFN: End get from https://msa.intuit.com/banking/fimkt/basic/QWBasic.ini, netstatus 0
    20200417 11:46:57: QFN: Beginning send to https://services.quicken.com/ofx-secure-plus/7101
    20200417 11:46:59: QFN: End send to https://services.quicken.com/ofx-secure-plus/7101, netstatus 0

    adding- 7101 is the numeric designation for DiscoverCard in fidir.txt
  • leishirsute
    leishirsute Member ✭✭✭✭
    The latest update is working for my downloads from  Citicards, Fidelity, Vystar, and Capital One.
    Quicken Deluxe Subscription; Windows 10 Pro 64-bit
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    @markus1957 That's interesting.  I didn't really think that they might send the financial institution data file in the patch, since they already have a system for sending it outside of the patches.  But from what you are saying, they are.  They really need to get their act together when they build their patches, or remove that file from the patches.

    It does though confirm what I was saying, and that wasn't a "program" change that caused the problem.
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
  • GeoffG
    GeoffG SuperUser ✭✭✭✭✭
    Chris_QPW said:

    It does though confirm what I was saying, and that wasn't a "program" change that caused the problem.
    Except to the average Quicken user it's all one in the same.
    user since '92 | Quicken Windows Premier - Subscription | Windows 10 Pro version 20H2
  • keithcnj
    keithcnj Member
    I tried that and it didn't work. Whatever they pushed in 26.15, it broke the TIAA downloads. I can't find anywhere that shows how to backout to 25.21. I tried typing in a URL in the same format as the one for the 26.15 mondo patch (replacing 26.15 with 25.21) but that doesn't work either. I recall that at some point they kept a list of the past few mondo patches. Anyone know what happened to that? If not, where can I get it?
  • Greg_the_Geek
    Greg_the_Geek SuperUser, Windows Beta ✭✭✭✭✭
    Quicken Subscription HBRP - Windows 10
  • keithcnj
    keithcnj Member
    Thanks, I tried that, but first found one of my PCs that didn't have the 26.15 update yet and tried the file download. No good, so the earlier comment that the Financial Institutions info file is what changed, and what broke TIAA is still true. When this happened before I had to open up tickets with both TIAA and Quicken. Eventually they sorted it out. I guess I will again.
  • To answer the "how did you question": I restored from backup.
    To comment on whether or not its a program vs other issue: This is 2020, not 1963. Users should not have to deal with back dating files, or any other such nonsense in order to "make the program work". Quicken should check to ensure that all input required to make Quicken work properly, is checked.
    It's not rocket science folks.
  • FYI: the previous version restored was R25.21. I think this may have been the test fix version from the previous time this failure was encountered as I don't see it listed in the release notes. It however has it's own issues with Express Web Connect lately (error CC-899, which I have no idea what that means).
  • Thanks Markus, that worked for Direct Connect. However, EWC is still not working properly. It times out with CC-502 this time. I recall having to fix this before (last year) and did that by turning off EWC, then turning it back on. I'll try that and see if it restores functionality. If not, I'm hosed.
  • The RESET didn't work either. SOL.
  • markus1957
    markus1957 SuperUser, Windows Beta Beta
    For the EWC account(s), have you tried Update Now from the gear icon in the account register?  Other than that, I'd submit a problem report from the Help menu link that identifies the EWC FIs that are having issues.  Is it all EWC accounts or just some?
  • That's just the usual way to update, sure I've been trying that for the last few hours (and many more days). I also tried the Reset Account function.
    It's all EWC accounts (just two). The DC accounts work now.
    I've submitted to problem reports recently (one last week, one today). So far, no response from whom ever receives those reports.
  • Reset of one account seems to have Reset ok, but still does not work when I update. I'm trying to reset the other account now (same bank) and see if that helps.
  • The communications process takes an very long time. It should be very quick. I suspect the servers at the other end are part of the problem. My connection speed is very good (> 170Mbps down, 20Mb up).
  • markus1957
    markus1957 SuperUser, Windows Beta Beta
    Update Now from the gear icon in the account register is not just the normal way to update. For EWC accounts it makes a fresh call to the FI server rather than just to the aggregation server as happens in a normal OSU.

    Also from your description, it sounds like only one financial institution with 2 accounts is involved.  So it's more likely an issue with the FI that the EWC team will have to sort out rather than the software update.
  • Scooterlam
    Scooterlam SuperUser ✭✭✭✭✭

    ....This patch and others before it are sometimes getting loaded with incorrect connection configuration information that tries to connect using the older direct connect method.  If you have already run OSU that day with the previous version, the incorrect data will not get updated.

    I have found if I back date fidir.ini about a week, close/open Quicken, OSU will run successfully.   Otherwise, you have to wait for a day (or so) until the configuration information gets automatically updated as it periodically does. 

    Users then think Quicken fixed the connection issue for their FI, but all that really happened is that Quicken downloaded the configuration data that should have been included in the patch.....

    FWIW.

    I updated QW HBR to R26.17 yesterday afternoon and my Fidelity Investments direct connection broke straightaway.  OL-295-A error.   I had already run a scheduled update earlier that morning.   

    This morning, I found and backdated the FIDIR.INI file as @markus1957 describes, restarted Quicken and my Fidelity connection is again working. 

    Thanks @markus1957

  • splasher
    splasher SuperUser ✭✭✭✭
    I wonder what would have happened if you had not changed the fidir.ini file and just waited until today.  Would it have updated the fidir.txt file and run successfully without your intervention because it won't do the fidir.txt file check more than once a day.?
    -splasher  using Q since 1996 -  Subscription  -  Win10
    -also older versions as needed for testing
    -Questions? Check out the  Quicken Windows FAQ list
  • drbfrog
    drbfrog Member ✭✭
    I have the same problem after updating - my process just locks and times out. OSU worked perfectly prior to the update. I tried the idea to reset the date but that did not work. I had a long help desk session last night which eventually ended with the agent checking with another support team and stating that this is a known problem - wasting hours of my time. I emailed Eric Dunn (CEO) and he responded stating that her will have US based customer care contact me Monday. Quicken India based support is not helpful, they always think the problem is a corrupt data file....and never have info on current problems being investigated...
  • drbfrog
    drbfrog Member ✭✭
    UPDATE - it worked once, took a long time but all processed. I tried again and back to hanging...
This discussion has been closed.