3008 : The Vendor or Vendorname format is invalid.

[janeread]

If you are using Protx in test mode, then the encryption passsword value should be 'testvendor' and not the actual encryption key. That is why Actinic was telling you the format was incorrect.

This seems very different from what everyone else has said - including support - anyway I've stayed in test mode and changed to 'testvendor' in the pl and ini files, but still get the same error message.

[RuralWeb]

This seems very different from what everyone else has said

But it is correct

[janeread]

Jane,
We have found it always worthwhile reminind people that there are in fact 2 OCCPROTXScriptTemplate.pl files within Actinic.

Thanks, Fergus, I am aware that there are two files and I've tried various combinations to try to get this to work - changing both, changing the site one changing the main one, but nothing seems to work.

[janeread]

I am slowly going bonkers.

Protx say the reason I am getting this error message is because “Actinic is set to live mode.”

Can I please tell you what I have done because I believe I am in test mode and so does Actinic support:

Going via the Actinic software in Business settings I have put in my vendorname – the same one I use to get into the admin panel) – and the secret key and set the radio button to test mode.

In the Program Files/Actinic V8/ OCCUpgrade/ Common OCC OCCProtxScriptemplate.pl it says:

######################################################################
# PROTX VPS Specific constants here
######################################################################

my $sPassword = 'testvendor';
my $sConfirmationEMail = 'test@test.com';


Similarly in the site version of this file it says the same thing.

I have incremented the OccUpgrade.ini several times because at one point I was using apparently erroneously my encryption password in the OCCProtxScripttemplate.pl, but presumably this won’t make any difference.

Any help would be very much appreciated.

[fergusw]

Going via the Actinic software in Business settings I have put in my vendorname – the same one I use to get into the admin panel) – and the secret key and set the radio button to test mode.

In the Program Files/Actinic V8/ OCCUpgrade/ Common OCC OCCProtxScriptemplate.pl it says:

######################################################################
# PROTX VPS Specific constants here
######################################################################

my $sPassword = 'testvendor';
my $sConfirmationEMail = 'test@test.com';


Similarly in the site version of this file it says the same thing.

I have incremented the OccUpgrade.ini several times because at one point I was using apparently erroneously my encryption password in the OCCProtxScripttemplate.pl, but presumably this won’t make any difference.

Hi jane,
I'm a little confused here
You wrote

my $sPassword = 'testvendor';
my $sConfirmationEMail = 'test@test.com';

and I wondered why you had testvendor here - I am assuming that this is just an example because you should not be seeing testvender in either of the 2 OCCProtxscriptTemplate.pl files!

Rather than try and get my head around all the variations you have been trying, all I really think i can do is to explain the "normal" procedure with PROTX in the hope that you can find a solution or even start again!

1. Enter Merchant ID and secret key into Actinic's payment method screen
2. In same screen set to TEST mode
3. Enter Encryption password, and relevant email address, into your site1's OCCProtxScriptTemplate.pl
(NOTE - this would be in Program Files/Actinic V8/ Sites/Site1/CommonOCC.OCCProtxScriptTemplate.pl - ignore the 'master' one AND avoid incrementing the OCCUpgrade.ini number for now)
4. Update website
5. Try test order to PROTX payment page
6. Call PROTX - get them to check site in test mode and approve your carts integration
7. Get confirmation from PROTX - they switch you live
8. Change to production mode in the Payment method screen (from step 1)

skipping the step of changing teh master OCCProtxScriptTemplate.pl and NOT updating the OCCUpgrade.ini file simply removes an extra, complicating step. Note, however that if you subsequently change the OCCUpgrade.ini number then the site1 OCCProtx.... file would be overwritten by the 'naster' OCCProtx.... file and you would have to reapply the settings.

See how you get on.

Top Tip: Check, double check and triple check the secret key and encryption password. It has to be EXACT - one tiny uppercase/lowercase or numeral one instead of l or capital I instead of l can cause problems.

We had an occasion where the last character of the encryption key for our client's PROTX script file was lowercase instead of uppercase. The transactions all seemed to go through surprisingly, however it caused a very strange issue on the card page on PROTX - missing addresses etc


Hope this helps - Good luck

[janeread]

thanks for trying to help me, Fergus.

Earlier in this string Bruce says that in test mode it should say testvendor in the OCCProtxScriptTemplate

In fact I've tried both options.

In Actnic itself I have cut and pasted the merchant ID and secret key and also typed them. My partner has stood and watched me too.

The latest communication from Protx says this:

As mentioned above, and as you can see from your VSP Admin Area, we are not receiving anything on our Test Servers.

If you/Actinic are able to manually alter the URL to which you are POSTing, you could either try simply entering the VSP Form Test URL, or enter our Showpost URL, which will enable us to view exactly what you are sending.

VSP Form Test URL: https://ukvpstest.protx.com/vspgatew...m-register.vsp

but when I try to place an order this is the URL that shows when I get the 3008 error message.

I have emailed them to tell them this.

Jane

[janeread]

Well the problem is finally solved, and I thought I would post what happened in case it is of any use to anyone in the future.

My web host has been taken over by another company and today the site that I'm having this problem with was down. I phoned them and they said it wasn't anything they'd done (how often have we heard that!!), but anyway I should migrate the site over to the new server. When I tried to do this Actinic threw up all sorts of error messages.

At first their support told me this was because Actinic couldn't be put on a Windows server (it's on a Windows server because of other stuff that is on this site). I explained that it had been on a Windows server for several years. Eventually I managed to find a helpful support guy who worked with me to get it moved to the new server, and hey ho not only did I have the site back up but the Protx 3008 error was no longer happening.

I don't know enough to understand why that solved this particular problem, but I've tried to include as much info as possible in cae it helps someone with that Protx 3008 error in future.

Cheers

Jane

[Duncan Rounding]

Great news Jane. Glad you've got it sorted.

[janeread]

It appears that I spoke too soon!

I said we had migrated the online shop to a new server and that appeared to have solved the problem, but I spoke too soon. What I hadn't realised was that it had reverted to test vendor settings everywhere so this is why it apeared to be fine. As soon as I entered the vendor name etc. I got 3008 message again.

[TraceyHand]

Jane...if you're testing in test mode you SHOULD be using the test vendor settings.

You shouldn't be using your vendorname until everything is LIVE.

I'm still confused about what settings you are using and why?

[janeread]

so are you saying that using Protx in test mode I should not put my vendorname and secret key in Actnic Business settings?

I am just getting more and more confused, so I may be missing something that is obvious to everyone else.

[fergusw]

Jane,

You have definately done something wrong.

Your PROTX bounce page in Actinic is showing

<INPUT TYPE=HIDDEN NAME="Vendor" VALUE="lwp1947">

in the source code.

Normally this value holds the vendor name. i.e. something like "businessname"

e.g.

<INPUT TYPE=HIDDEN NAME="Vendor" VALUE="teclan">

Your vendor code looks a little like a secret key and not like a vendor name that PROTX would issue you.
This would point to the wrong info being entered into the Configure Method screen for PROTX in Actinic.

If this information looks correct then it may be worthwhile checkout your vendorname and details with PROTX again in case of any mix up at their end perhaps?

[janeread]

Hi Fergus

I think you must be looking at http://www.healthandgoodness.com and I have Protx working fine on that.

The one where I am struggling is http://www.lifeworkpotential.com

Jane

[fergusw]

OK - just checked the lifeworkpotential.com and it went across to PROTX as test vendor quite happily. I Did not proceed and enter card details though.....

[janeread]

Just had Protx phone me (which is very nice of them) and they've said I need to put proper vendor name and password encryption in even though I am at the testing phase.

She talked me through it telling me exactly what to put where, but still got the 3008 error again so waiting to hear back from them

I really appreciate how much everyone is trying to help me solve this.