Protx Error after V8 to V9 Upgrade

[grantglendinnin]

Hello.

I just upgraded our site from v8 to v9, did a full upload, and Protx now crashes out when redirecting through after entering the customers details.

The error given is as follows:

This transaction attempt has failed. We are unable to redirect you back to the web store from which you were purchasing. The details of the failure are given below.

Status: 	INVALID

Status Detail: 	5030 : Unable to decrypt the request message. This might be caused by an incorrect password or invalid encoding.

Any idea how to fix this, I've made sure the Protx configuration inside the Actinic software is correct, re-uploaded and the issue persists. For now, I've had to start accepting Paypal payments, which, frankly, I wasn't really ready for, but hopefully it'll help not lose too much custom.

Your help is much appreciated!

Thanks

--------------------------------------------------------------

Edit: Ahh, just noticed in the footer of the V8 to V9 Upgrade manual the small paragraph regarding Protx. I've now edited the OCC Protx file and payments are now going through fine (I hope! haha). Just thought I'd let anyone else with the same issue know the solution.

You need to enter your merchant info and e-mail info into the OCCProtxPayment file in the Site1>Common OCC folder.

Thanks

[marke]

Have a look in your OCCPROTXScriptTemplate file. I found that Actinic overwrote my protx username and password during the upgrade and was getting the same error. I simply changed the above file back to what it should be and the problem was fixed.

[Darren B]

Grant please search the forum, this is a regular topic and there is a sticky.

SECRET KEYS need to be redone

[grantglendinnin]

Yeah, I got it, hence why I edited my original post a few minutes after I posted it. I didn't find the solution for this in v9, as most issues I've found with v9 haven't been covered in <v8.

Unfortunately Actinic seem to have a complete lack of support for v9 versions, other than standard 'Catalog'. The manual presented has no reference whatsoever to the extra features Business Plus has, which, IMO, is pretty shocking, especially for software with such a price tag as Actinic. For example, setting up the Payment provider details. We have set Protx as the 'website' payment provider, and Paypal as 'Fallback' (in v9 BP), yet Paypal is set as the default in the drop down list at the checkout. Doesn't this defeat the entire meaning of 'fallback'? Then again, due to a complete lack of communication and documentation, said queries have to be brought up, one way or another.

Over and out.

[Darren B]

Maybe True

Perhaps Bruce could update his sticky to say V8 & V9 protx

D

[cdicken]

Unfortunately Actinic seem to have a complete lack of support for v9 versions, other than standard 'Catalog'. The manual presented has no reference whatsoever to the extra features Business Plus has, which, IMO, is pretty shocking, especially for software with such a price tag as Actinic.

Hi Grant. I think there might be some confusion here. Everything in the help is relevant to all versions of Actinic. That's why we use the term 'Actinic' to describe the software rather than 'Actinic Catalog' or 'Actinc Business'. The only time 'Actinic Catalog' is mentioned is when we say a feature is not available in Catalog. With regards to the specific features that are specific to Business Plus, the multi-site features are talked about in 'Application Settings > Licensing Actinic Sites' though I appreciate this doesn't mention Actinic Business Plus specifically, I'll raise a bug for this. Multi-User features are in the 'Connecting Multiple Users' section.

For example, setting up the Payment provider details. We have set Protx as the 'website' payment provider, and Paypal as 'Fallback' (in v9 BP), yet Paypal is set as the default in the drop down list at the checkout. Doesn't this defeat the entire meaning of 'fallback'?

'Fallback' simply means that the payment method will always be offered to all customers - and is only really required if you are limiting payment methods by location. If you aren't doing this, you don't need to select 'Fallback'. 'Fallback' also has the effect of making the payment method the default one, so it sounds like it is definitely not required by you in this case.