AbleCommerce Shopping Cart Software

I am having difficulty capturing payments this morning. It gives me the message, "Signature Credential arguments cannot be null". I am using Paypal as my payment processor.
Could this have anything to do with installing the latest patch last night?

Hi,

Can you look in the error log and see if there is a more detailed error message?

Thanks
Katie

Here is one:

Provider threw exception in DoCapture.
Exception: Signature Credential arguments cannot be null Stack Trace: at PayPal.SOAP.MerchantAPICallPreHandler..ctor(Dictionary`2 config, IAPICallPreHandler apiCallHandler, String apiUserName, String accessToken, String tokenSecret) at PayPal.PayPalAPIInterfaceService.PayPalAPIInterfaceServiceService.DoCapture(DoCaptureReq doCaptureReq, String apiUserName) at CommerceBuilder.Payments.Providers.PayPal.PayPalProvider.DoCapture(CaptureTransactionRequest captureRequest) at CommerceBuilder.Payments.PaymentEngine.a(CaptureTransactionRequest A_0, Boolean A_1)


And another:

An error has occured at https://www. contractors-solutions.net/ProcessPayPal.ashx
Exception: Object reference not set to an instance of an object. Stack Trace: at CommerceBuilder.Payments.Providers.PayPal.IpnProcessor.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Is this the first order you've attempted to capture since 9/09/2015?

Paypal has issued a number of changes which affect server configuration, we have confirmed this issue is NOT a result of the patch.

Not sure if you get daily PayPal orders, but the last successful capture would be good to know as well.

I had no problem yesterday. It wasn't until this morning that I had any problems. That's why I thought it might have something to do with the patch I installed last night. It is the only changes I have made to the website.

Ok, we figured out how to get it working. Paypal must have changed something on their end. If you enter all information for the API credentials, we can get the capture to work.

-API username
-API password
-API signature

Once this information is setup on the configuration page, standard Paypal capture is now working.

The only problem this creates is that Paypal Express checkout is enabled when this information is entered. If this is not a Payment option that you wish to use, then we will need to provide a way for you to turn it off.

I'd sure like to hear what Paypal is saying about this change. They have been making recent updates but from all the announcements, it appeared that it had to do with them upgrading their certificates to SHA-256.

I'll have the developers look into the API guide and see if the requirements for capture have changed. In the meantime, you can add your API credentials and this should start working again.

I am working on that.

Just now, I tried testing through the checkout, and shipping methods don't work. You can't get past the shipping step to complete checkout.

No shipping method shows up on the back end either. I can't enter sales manually.

This is unrelated to Paypal. When was the last order that had shipping?

My last sale was yesterday afternoon. I have had no sales today because nobody can checkout without a shipping method. I have had no problems at all until I installed that patch last night.

This is probably a long shot, since I'm way back on R5, but if your shipping setup screens are still correct, is there a chance that TLS 1.0 (client) got disabled on your server? I was testing yesterday because Microsoft has an update to RDP that allows it to use TLS 1.2, so I disabled TLS 1.0 (server) and TLS 1.1 (server). Everything worked fine. However, when I tried disabling TLS 1.0 (client), AC couldn't connect to UPS' or FedEx's rate servers.

The registry key (Windows Server 2008 R2) to make sure TLS 1.0 Client is enabled is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client
with values:
DisabledByDefault : DWORD : 0
Enabled : DWORD : ffffffff (hex)

Also, I've fiddled with my cipher suite settings, so maybe this has nothing to do with your problem.

Did you set a new encryption key after applying the patch? The shipping, tax, and payment providers all use encryption for their gateway data. Even though we did a lot of testing with encryption and specifically tested the gateway parameters, I am wondering if the information for your shipping provider is working.

No, I did nothing with any encryption key, other than upload the new EncryptionKey.aspx file included withy the patch.

kwikstand wrote:No, I did nothing with any encryption key, other than upload the new EncryptionKey.aspx file included withy the patch.

Can you please confirm by looking at your configured shipping and payment provider that all account details are readable and correct? You may also want to enable debug mode on shipping provider then check whats being returned from server under App_Data/Logs/your provider.log file when you attempt checkout.

From what I'm being told, as soon as you install the patch and access the site, the encryption.config file in the app_data folder is automatically changed. It isn't required to create a new encryption key for the patch.

Here are some things you can try.

1) confirm the encryption.config file was modified after the patch. You can even compare with the backup that was taken before applying the patch. They should be different.

2) As Mazhar stated above, look at your shipping gateway configuration page and make sure it still has the API credentials still entered.

I checked m y UPS configuration and the shipper number was blank, so I entered it. The User Id and Access Key aren't available to enter anything. Somehow, this info got wiped out.

Shipping still does not work. My encryption.config file properties says: ‎Tuesday, ‎September ‎22, ‎2015, ‏‎8:52 PM

Also, my Paypal configuration was missing the PayPal Account, so I reentered that.

Recycle your app pool and check the configurations again. Check if they have correct values or still blank.

Nope, Mazhar. I recycled and still no change. I am losing sales. None so far today.

Update: This situation occurred when the encryption.config file was renamed prior to applying the SR1 patch. We have code written to look at the encryption.config file and use that to re-encrypt the file. When the encryption.config file is invalid or missing, then ALL gateway credentials (payment, tax, shipping) are unavailable. This essentially broken the checkout process.

To fix the issue, we restored the encryption.config file and re-entered all the gateway credentials.