Getting started - Online banking problems (Vanguard / Citadel FCU)

[David Reiser]

On 23 Aug 2007, at 9:43:57 PM, Shawn Poulson wrote:

>
>
>> -----Original Message-----
>> From: David Reiser <dbreiser at earthlink.net>
>>
>> My Vanguard IRA works correctly, but I've seen one case where it
>> looked like Vanguard had 401K transactions signed backwards. I'd have
>> to look at the ofx logs to be sure though.
>>
>> Sounds like you may not be getting a completed connection. If you set
>> the environment variable AQOFX_LOG_COMM to 1, then aqbanking will
>> keep a log of ofx sessions in /tmp/ofx.log, and you can look exactly
>> what citadel is sending back to you.
>>
>> Don't leave AQOFX_LOG_COMM set all the time, because your password
>> will most likely be present as plain text in the log.
>>
>> The quickest way to check the ofx parameters is to borrow some time
>> in front of quicken, run a connection attempt with dummy account info
>> (unless you really want to have real data lingering in your friend's
>> copy of quicken), and then read quicken's ofxlog file.
>
> I ran with this variable and it returned the below log.  It appears  
> I don't
> get a response.
>
> As for the Quicken angle, I own a copy of Quicken.  This is how I  
> got the
> necessary OFX/FID/URL combinations.
>
> In any case, does this log tell you anything in particular?  Thank  
> you for
> the quick response.
>
> Sending:
> -------------------------------------
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20070823213658.000
>
> <OFX>
> <SIGNONMSGSRQV1>
> <SONRQ>
> <DTCLIENT>20070823213658.000
> <USERID>196829
> <USERPASS>91704
> <LANGUAGE>ENG
> <FI>
> <ORG>Citadel Credit Union
> <FID>231380104
> </FI>
> <APPID>QWIN
> <APPVER>1200
> </SONRQ>
> </SIGNONMSGSRQV1>
> <SIGNUPMSGSRQV1>
> <ACCTINFOTRNRQ>
> <TRNUID>20070823213658.000
> <CLTCOOKIE>1
> <ACCTINFORQ>
> <DTACCTUP>19691231
> </ACCTINFORQ>
> </ACCTINFOTRNRQ>
> </SIGNUPMSGSRQV1>
> </OFX>
>
Getting no OFX response suggests to me that you didn't hit the ofx  
server. Double check the web address for typos. Also make sure you're  
using the address for the data server and not the 'branding server'.  
The branding server is the first connection Quicken makes, the  
branding server sends the data server address back in its response,  
then quicken logs into the data server to retrieve your data.

There is another debugging variable available -- (from the gwenhywfar  
README):

"GWEN_SSL_DEBUG"
----------------

If this environment variable exists the SSL code will append data  
received
via an SSL connection to "/tmp/read.bin" and append data sent via an SSL
connection to /tmp/written.bin".

--------end of gwen doc quote

Those two files will give you more of the SSL conversation that might  
tell you why no OFX comes back.

Dave

--
David Reiser
dbreiser at earthlink.net