nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Trouble connecting to First Command Financial Planning

rperry3146

For many years I have downloaded my financial transactions with First Command Financial Planning. Last Wednesday (12 Oct 22), I received a OL-297 error when attempting my daily download. I have tried everything on the page that discusses this error to no avail. I have tried to deactivate/reactivate the accounts with no success. My Quicken is up to date with the latest updates. I am able to update my accounts with other my financial institutions using Quicken. It appears that Quicken is unable to reach the FCFP website. I have called First Command and they told me that they have not changed anything on their end. Any suggestions???

Find more posts tagged with

Accepted answers

UKR

Did you install a Windows Update on that day (10/12/22)?
There was mention of a Windows Update causing this particular kind of problem. Try uninstalling that Windows Update.

All comments

Quicken Jasmine

Hello @rperry3146,

Thank you for contacting the Quicken Community, though I do apologize that you are experiencing this error with your First Command account(s).

I have located a support article that discusses some troubleshooting steps to take when presented with an OL-297 error. You may follow this link to access that FAQ. It is recommended to save a backup before proceeding (just in case).

I hope this helps!

UKR

Did you install a Windows Update on that day (10/12/22)?
There was mention of a Windows Update causing this particular kind of problem. Try uninstalling that Windows Update.

rperry3146

UKR - thanks for the tip. I uninstalled the Windows update that was installed on 12 Oct, I am now able to download all my First Command data. Thanks!!

Neil W

Is anyone working to to find and resolve the conflict? Pausing Windows Updates is only a temporary solution for this issue. Also, will the issue persist with Windows 11?