CGI-Central installed aMember on my new server a couple of days ago. Most features seem to be working okay. However, when I test a credit card purchase on the default signup page (/cc_core/cc.php) I get an error message ... Payment failed: Error running pfpro script, result returned: Appareantly something is preventing the execution of the pfpro script located at /plugins/payment/payflow_flow/payflow_pro.inc.php. However, the only functions disabled in /etc/php.ini are: disable_functions =dl,system,passthru,proc_open,posix_uname Attempted signups create a record for the new member that can be seen in the aMember control panel. Name, login id, email, password are created, address information is not recorded. What could be disrupting the execution of the processing script? Also, where is the login and password information stored (in aMember)that the php script needs to access my PayFlow Pro account? thanks, -zthomasz
There is a problem with script configuration. Have you followed all steps described at aMember CP -> Setup -> PayFlow Pro?
Yes Alex, I followed the configuration steps. However, I just checked the apache error logs and got this: Wed Feb 28 12:50:52 2007] [notice] Digest: generating secret for digest authentication ... [Wed Feb 28 12:50:52 2007] [notice] Digest: done [Wed Feb 28 12:50:52 2007] [notice] LDAP: Built with OpenLDAP LDAP SDK [Wed Feb 28 12:50:52 2007] [notice] LDAP: SSL support unavailable [Wed Feb 28 12:50:52 2007] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads. [Wed Feb 28 12:50:53 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Wed Feb 28 12:50:53 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Wed Feb 28 12:50:53 2007] [notice] Apache/2.0.54 (Fedora) configured -- resuming normal operations sh: /pfpro.sh: No such file or directory I was surprised that SSL support was unavailable, so I ran a search on the error message "LDAP: SSL support unavailable" That's a message from mod_auth_ldap - it means there isn't a valid CA certificate to authenticate the LDAP servers certificate against. It looks like this new server & the process require an SSL certificate to work. I talked with Thawte about a quick re-issue of our current cert (on the old server) but that would leave the old server without a cert until we complete the move to the new server. That's not an option due to credit card processing requirements for the "old" server. So, I just ordered a certificate for the new server. Once it's approved and installed, I'll update this thread and let you know if the new SSL certificate solves the problem. It looks like it should. thanks, -Thomas zthomasz
Thomas, these messages in the log (all but latest) are not related to aMember and PFpro at all. We are working on updated pfpro plugin that will keep these problems you are experiencing in past. Please contact us via helpdesk.
I was getting the "Payment failed: Error running pfpro" error even after I've chmod it to be executable(755). After a full day of research I figured out the issue. So for anyone here having a problem with the paypal(previously know as verisign sdk package), this may be your solution. Access to linux command line. First change into directory where your pfpro.sh is located and type in the following command: Code: dos2unix -vi pfpro.sh Hope this helps.