I'm having problems getting payflow pro working on a site, and I suspect it is because it is running on IIS. Attempting to complete a checkout results in 2 entries in the watchdog log:

  1. an empty entry from uc_payflowpro
  2. a warning entry from uc_payment with the message "Payment failed for order XX: Received blank response from the PayFlow Pro gateway."

There is no record of the transaction at https://manager.paypal.com/. If I deliberately use a bad password in the API Credentials, I get the exact same results. Sounds like nothing is getting sent in the first place.

I have no problem getting the same configuration working just fine on a LAMP setup. I'm now trying to track down just where the process is failing on the WIMP setup..

Comments

cjdavis’s picture

cjdavis commented

I've tested the example code available from
http://developer.paypal-portal.com/pdn/board/message?board.id=payflow&th...

Aside from a minor logic error in handling $_REQUEST on Windows, it runs just fine everywhere I tried it - Windows, Linux, and OSX.

Now I need to figure out the difference between the example code and uc_payflowpro.

kwinters’s picture

kwinters commented

Chances are any issues with the code are in the curl_setopt section.

In particular, make sure the .pem file is accessible and in the correct place, etc. because the examples from paypal don't use it at all.

cjdavis’s picture

cjdavis commented

Thanks, access to the .pem file was/is the problem. Much like 99% of problems running Drupal on IIS, it is permissions. I've disabled the .pem file check while finishing up the site configuration until I can fix them. I'll post the correct IIS permissions once I do.

The actual source of the problem was masked by the watchdog() call having the old D5 syntax, which broke it. Once I fixed that the error returned was very clear. I've submitted that as #517402: old syntax for watchdog() call

kwinters’s picture

kwinters commented

Alright, I'll make a note of your findings in the README once you have everything straightened out. Thanks!

kwinters’s picture

kwinters commented
Component: Code » Documentation
Status: Active » Fixed

Documentation change, appears abandoned. If anyone wants to provide any IIS-specific install instructions I'd be happy to include them, but for now I'm just going to close this to cut some clutter.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.