Connecting to BoA (California)

Lincoln A Baxter lab at lincolnbaxter.com
Fri Oct 25 06:07:17 EDT 2013


I believe Bank of America requires that you register for Quicken
access... they may charge a monthly fee for the service.  If you have
not registered, that might be why you cannot connect.

Lincoln


On Fri, 2013-10-25 at 09:11 +0800, Christopher Singley wrote:
> Looks like you're connecting to the server, but failing OFX signon.
> 
> Definitely worth trying whatever FID they self-report in .qfx downloads.
> 
> Sometimes FIs get touchy about client versions they're willing to support
> (I think it's an Intuit licensing cost issue)... is there a knob in GnuCash
> to tweak the APPVER to the latest & greatest for APPID QWIN?  What are they
> up to now, APPVER=2200?
> 
> You might also be getting stopped out if BofA's server is failing parsing
> because GnuCash is sending straight OFX without the private INTU XML
> attributes... try sending APPVER=Money, APPID=1600 (although that's getting
> pretty damned long in the tooth & may no longer be supported)... but MSFT
> did use plain-vanilla OFX for their product.  Worth a shot.
> 
> (BTW not that it's relevant, but does anybody know why BofA is flying
> colors ORG=HAN?  Usually mismatched tags indicate legacies from M&A, but
> Manny Hanny went to Chemical & thence to JPM, not BofA ... is HAN some OFX
> server software vendor?)
> 
> 
> On Fri, Oct 25, 2013 at 2:27 AM, G. Paul Ziemba
> <pz-gnucash-user at ziemba.us>wrote:
> 
> > soccupiesla at gmail.com (S Angeleno) writes:
> >
> > >I would provide logs, but I googled and tried to follow advice about
> > >setting the AQOFX_LOG_COMM environment variable to 1 to enable logging
> > >and I couldn't figure out how to get that to work. Does anyone have any
> > >suggestions? Perhaps I should be asking the aqbanking mailing list?
> >
> > The syntax for csh-like shells would be:
> >
> >     % setenv AQOFX_LOG_COMM 1
> >     % gnucash
> >
> > for sh-like shells, you could use
> >
> >     $ AQOFX_LOG_COMM=1 gnucash
> >
> > This should cause your OFX communications to be logged to /tmp/ofx.log.
> >
> > This file WILL CONTAIN YOUR OFX USERID+PASSWORD, so handle carefully.
> >
> > The error messages in the responses in this file can sometimes
> > be useful in pinpointing the problem.
> > --
> > G. Paul Ziemba
> > FreeBSD unix:
> > 11:31AM  up 14 days,  2:12, 15 users, load averages: 0.99, 0.92, 0.90
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> >
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 





More information about the gnucash-user mailing list