dealing with an ol-221-A
in [Quicken]
|
Prev: QD2010 R3 available with Overwriting Backup fix available BUT....
Next: Upgrade to Quicken 2010 deleted all of my pending downloaded transactions
From: Bernie Cosell on 13 Nov 2009 12:57 I have a Quicken visa card that was doing direct-connect just fine until the end of October. But for the last several *weeks* now, it is getting nothing but OL-221-A. All my other accounts update just fine. I just spent a half hour with someone at Chase [who issued the Quicken Visa] who was completely unhelpful and seemed not to know much about what was going on. Is there any way actually to sort out what the problem is or do I just have to sit and wait until it somehow [hopefully??] magically fixes itself... [this with Q2009/r6] Thanks! /b\ -- Bernie Cosell Fantasy Farm Fibers bernie(a)fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--
From: JimH on 13 Nov 2009 13:53 Bernie Cosell wrote: > I have a Quicken visa card that was doing direct-connect just fine until > the end of October. But for the last several *weeks* now, it is getting > nothing but OL-221-A. All my other accounts update just fine. I just > spent a half hour with someone at Chase [who issued the Quicken Visa] who > was completely unhelpful and seemed not to know much about what was going > on. > > Is there any way actually to sort out what the problem is or do I just have > to sit and wait until it somehow [hopefully??] magically fixes itself... > [this with Q2009/r6] > > Thanks! /b\ When I have problems like this, I remove the account online services, and then set them up again.
From: John Pollard on 13 Nov 2009 16:16 Bernie Cosell wrote: > I have a Quicken visa card that was doing direct-connect just fine > until the end of October. But for the last several *weeks* now, it > is getting nothing but OL-221-A. All my other accounts update just > fine. I just spent a half hour with someone at Chase [who issued the > Quicken Visa] who was completely unhelpful and seemed not to know > much about what was going on. > > Is there any way actually to sort out what the problem is or do I > just have to sit and wait until it somehow [hopefully??] magically > fixes itself... [this with Q2009/r6] Here's the faq for OL-221 https://quicken.custhelp.com/cgi-bin/quicken.cfg/php/enduser/std_adp.php?p_faqid=4141 Lately when Intuit responds to questions about 221, they almost invariably say it's bad data from the fi (#2 in the faq). Apparently, Quicken used to permit certain invalid OFX data in the downloads, but Intuit decided to start having Quicken reject much of that invalid data relatively recently. I'm not certain whether the new Quicken editing rules for OFX data went into effect in Q2009 or not, but I'm thinking they did. I suspect that in many cases, the OL-221 error may seem to go away on its own. as the fi's discover that their downloads are being rejected and change things at their end. -- John Pollard
From: Bernie Cosell on 14 Nov 2009 16:38 "John Pollard" <8plus7isf(a)gmail.com> wrote: } Bernie Cosell wrote: } > I have a Quicken visa card that was doing direct-connect just fine } > until the end of October. But for the last several *weeks* now, it } > is getting nothing but OL-221-A. } } Here's the faq for OL-221 } } https://quicken.custhelp.com/cgi-bin/quicken.cfg/php/enduser/std_adp.php?p_faqid=4141 } } Lately when Intuit responds to questions about 221, they almost invariably } say it's bad data from the fi (#2 in the faq). thanks! The best part of that is telling me about the OFXLOG file -- didn't know [but hoped] quicken could tell me more about what its problem was with the server than just "error". } I suspect that in many cases, the OL-221 error may seem to go away on its } own. as the fi's discover that their downloads are being rejected and } change things at their end. I'll try doing the download again, and then I'll save the OFXLOG file and then, depending on what it tells me, I'll try again [probably uselessly again, sigh] to talk to someone at Chase about the problem. THANKS! /bernie\ -- Bernie Cosell Fantasy Farm Fibers bernie(a)fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--
From: R. C. White on 15 Nov 2009 13:32
Hi, Bernie. You are not alone! I don't know if that news is comforting or not, though. I've only recently (6 months ago?) started downloading from Broadway Bank, based just 50 miles away in San Antonio. It took a few months to work through their username/password/PIN/"What's your Grandpa's first name?" setup. Just when things were working smoothly, OSU suddenly started giving me a red flag on that FI. Several voice calls to their "Online Banking Specialist" - and MANY attempts via Quicken to Set Up the account (Yes, I "deactivated" it in Quicken am trying to activate it again) - later, I'm still getting OL-221-A and occasional OL-221-8 errors. The messages always suggest to "Try again later." I'll probably be on the phone again tomorrow to see if "Becky" can figure out if there is a switch that she must flip to enable this account - again. RC -- R. C. White, CPA San Marcos, TX (Retired. No longer licensed to practice public accounting.) rc(a)grandecom.net Microsoft Windows MVP (Using Quicken Deluxe 2010 and Windows Live Mail in Win7 x64) "Bernie Cosell" <bernie(a)fantasyfarm.com> wrote in message news:ln8uf59rqgs2cvjt3bkm0950ivr03pr8u9(a)216.168.3.66... > "John Pollard" <8plus7isf(a)gmail.com> wrote: > > } Bernie Cosell wrote: > } > I have a Quicken visa card that was doing direct-connect just fine > } > until the end of October. But for the last several *weeks* now, it > } > is getting nothing but OL-221-A. > } > } Here's the faq for OL-221 > } > } > https://quicken.custhelp.com/cgi-bin/quicken.cfg/php/enduser/std_adp.php?p_faqid=4141 > } > } Lately when Intuit responds to questions about 221, they almost > invariably > } say it's bad data from the fi (#2 in the faq). > > thanks! The best part of that is telling me about the OFXLOG file -- > didn't know [but hoped] quicken could tell me more about what its problem > was with the server than just "error". > > } I suspect that in many cases, the OL-221 error may seem to go away on > its > } own. as the fi's discover that their downloads are being rejected and > } change things at their end. > > I'll try doing the download again, and then I'll save the OFXLOG file and > then, depending on what it tells me, I'll try again [probably uselessly > again, sigh] to talk to someone at Chase about the problem. > > THANKS! /bernie\ > -- > Bernie Cosell Fantasy Farm Fibers |