Payflow Pro transaction error log failure

Hi, I am having issues with the latest payflow pro module (1.3.8a)

I've got everything set up, but when I attempt a transaction, in test mode, I get the following back:

1366 Incorrect integer value: '' for column 'ref_id' at row 1
in:
[insert into pubs_credit_card_log (orders_id, ref_id, trans_result,trans_auth_code, trans_message, trans_amount,trans_date) values ('-1','', '','-', 'failed for cust_id:[email protected]:','123.00',now() )]

The debug info I get emailed to me as a result is:
(Payflow Pro Debug Codes... is the subject)

 test-payflow.verisign.com 443 "TRXTYPE=S 
&TENDER=C 
&USER=***** 
&PWD=***** 
&VENDOR=***** 
&PARTNER=***** 
&VERBOSITY=MEDIUM 
&ACCT=5105XXXXXXXX5100 
&EXPDATE=0808 
&CVV2=001 
&AMT=123.00 
&CURRENCY=USD 
&COMMENT1[6]=( 1 )  
&COMMENT2[92]=FREE SHIPPING! (Free Shipping Only)0  ZenSessName:zenid
ZenSessID:vmte1ghkodejloj3sfujj4qv14 
&INVNUM=Cust:1 Order:1 
&CUSTREF=Order:1_Cust:1_Time:0.31349300 1216999158 
&NAME[11]=PAUL KAISER 
&LASTNAME=Kaiser 
&STREET=123 Any St. 
&CITY=Champaign 
&STATE=IL 
&ZIP=61820 
&COUNTRY=United States 
&SHIPTOFIRSTNAME=Paul 
&SHIPTOLASTNAME=Kaiser 
&SHIPTOSTREET=123 Any St.  
&SHIPTOCITY=Champaign 
&SHIPTOSTATE=IL 
&SHIPTOZIP=61820 
&SHIPTOCOUNTRY=United States -- PHP/COM Test Transaction --" 30
test-payflow.verisign.com



 
& 
&
-1
Array

It seems to me the transaction is failing, and zenCart is trying to log the failure, but is erroring when just trying to log it.

I am on Windows Server 2003, IIS6, PHP5.2.6, I have verified that CURL + SSL work, I'm using zenCart 1.3.8a

For testing, I used the Mastercard test cc number, and 001 for the CVV.

Any ideas? I feel like we're SO CLOSE!

Thanks,
Paul

I didn't think that the v1.3.8 version of the module even used the "pubs_credit_card_log" table for logging ... which makes me wonder if you're really using the module you think you are.

Granted, I'd have to look at the code to confirm, and I don't have that code handy at the moment.

You could try turning off the debug mode and/or Enable Database Storage option in the module's settings in your admin area ... if it's really an error in that, then turning it off should let you complete a test at least.