This discussion was created from comments split from: Lincoln Financial Connection Issues: OL-290-B.
@Quicken Kristina I am also having a problem with Lincoln Financial Group. I am getting an OL-292-B error when trying to update for several days now. I am on version R69.53 so it may not be related to the problems with R70.20. I have submitted a report a problem multiple times now with no response.
I followed the suggested workaround and reinstalled version R69.25, but still got the same OL-292-B error when trying to use direct connect for Lincoln.
Hello @MarkL18 & Rob,
Thank you for taking the time to visit the Community to report this issue, though we apologize that you are experiencing this. I moved your posts to a new discussion because the error you're reporting is different from the error reported in the discussion you initially posted to.
We have forwarded this issue to the proper channels to have it further investigated. In the meantime, if you haven't done so already, please navigate to Help>Report a Problem and submit a problem report with log files attached in order to contribute to the investigation.
While you will not receive a response through this submission, these reports will help our teams further investigate the issue. The more problem reports we receive, the better.
When you send a problem report with log files attached, please post to this discussion to let me know!
We apologize for any inconvenience! Thank you.
(CTP-19340)
I've submitted the problem report with log files as requested.
Are there any updates on this problem? I have been getting this error for almost 1 week now. I have reported the problem with log files.
I tried updating to the 70.21 patch that was just released, but I continue to receive the OL-292-B error.
Quicken has not offered me the 70.21 update yet. I am still on R69.53 and still getting OL-292-B error for LFG.
Quicken hasn't offered me the 70.21 update yet either, but I was able to manually download and install. But as Mark said, it didn't fix any issues with LFG. The patch notes said it fixed connection issues with several financial institutions, but I still cannot connect to my Lincoln Financial account for probably about 10 days now.
@Quicken Kristina do you have any updates on this issue? Thank you.
Hello @romtoss & @Rob,
The ticket is open, but there are no updates yet.
The latest update, R70.21, is currently in staged release. If you haven't been prompted to update, you can manually install it using this article: https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product . However, the update is a hotfix for the OL-290 issue and likely will not fix this issue with Lincoln Financial Group.
Thank you!
So on the original thread I started about Lincoln Financial, we were told that issue was part of a larger issue and to see the other thread. Now a patch has been released to 'fix' the larger issue that Lincoln Financial was supposedly a part of. But after people are reporting this didn't fix their Lincoln Financial issue we are told that the patch will not fix the Lincoln issue. So why were we directed to use the other thread for the fix? And what is being done to address and fix the Lincoln Financial issue? I'm confused.
Update: I am on 70.20 and this morning my Lincoln Financial did connect. I wasn't offered 70.21 yet and I'm not touching that if everything else is working. So I don't know what happened behind the scenes, but magically it started working. Hopefully it will continue after I get 70.21 offered (along with everything else.) Because one of the institutions listed was Wells Fargo, yet my Wells Fargo never stopped working and really hope it continues with 70.21.
Update: Mine started working WITHOUT updating. Running 69.53. Looks like they plugged the server back into the wall.
Good news. My LFG account also updated this morning with no issues. I am still on R69.53. I will wait for R70.21 to be offered before updating.
Thank you Quicken for whatever you did to fix this.
I'm on 70.21 and can also confirm LFG was able to connect this morning.
Thank you for the follow-up,
I'm glad to hear it's working now!
If you need further assistance, please feel free to reach out!