3008 : The Vendor or Vendorname format is invalid.

[janeread]

I am running Protx in test mode on one of my sites and get this error message when I try to place a test order:

3008 : The Vendor or Vendorname format is invalid.

I contacted Protx support and got this message:

The error message you have provided indicates that you are either using the incorrect VendorName, or are posting transactions to an incorrect server, for example, to the Live server when you only have a test account.

Now, as far as I'm aware, the only place I put my vendor name is in the Merchant ID field when I configure Protx in the Business Settings. I have cut and pasted it there to make sure I didn't make any typos.

help!

Jane

[Bruce]

Hi,

Can you check in 'Network settings' if you have 'Use relative cgi-bin url's' selected. Turn it off update the site and let me know if the test works.

Kind regards,

[janeread]

Just looked, Bruce, and the box is not checked.

Any other thoughts?

Jane

[janeread]

If anyone can help me with this, I would really appreciate it.

Today i redid all the Protx steps with my partner reading the instreuctions and watching what I was doing. He couldn't see anything that I was doing wrong.

I've approched Protx again, but they say it's an Actinic problem!

I'm getting very fed up and frustrated. :confused:

Jane

[TraceyHand]

Jane,

Have you checked the OCCProtxScriptTemplate to ensure it still has your details as per THIS POST (http://community.actinic.com/showpost.php?p=173386&postcount=9)?

[janeread]

Hi Tracey

Thanks for your suggestion. I had checked it several times already, but I checked it again and it apperaed to be OK. I wasn't sure if I had had Actinic open when I did the incrementing the version step so I re-did that.

On the PC I have been using the problem is still the same. I still get the same message. I wondered if Cookies(????) could be involved in some way so decided to try it on my laptop and hey ho everything went correctly.

I then tried it on my partners laptop and the message about this is running in test mode and to click on the next button was there (as with all the others) but I couldn't see the 'next' button, so I couldn't tell if I would have got the error message from there.

Could some of you guys see if you can get to the credit card page (choosing 'Testing Do Not Use' from the payment options)

Here's a page to use:

http://www.lifeworkpotential.com/acatalog/Updating_Earlier_Kits.html

thanks

Jane

[TraceyHand]

no "next" button here either...you may need to add it in (there is info on the forum about this somewhere, I believe)

[janeread]

the next button is appearing on the other two computers. On my partners machine and presumably yours I think the 'next' button is 'under' the right nav.

I'm not so worried about this, as I had it with another site on some machines, but once Protx went live the automatic bounce took care of it.

But it does mean, of course, that you can't get to the Protx page at the moment!

Jane

[janeread]

I have now spoken to Actinic support about this Protx problem and they suggested I upgrade from 8.5.0 to 8.5.2 and that should solve the problem.

I've done that and it hasn't. I'm still getting the same error message:

3008 : The Vendor or Vendorname format is invalid.

Anyone any ideas please

Jane

[wjcampbe]

After checking that you have the correct vendorname etc in the PROTX OCC script, did you remember to increment the version number in OCCUpgrade.ini?

[janeread]

yes, Bill. In fact I've done this about 6 times - replacing the encrypotion password and incrementing the version. Typing in the password, copying and pasting it, pulling out my hair and then pasting it (the number not my hair!), banging my head on the table then upping the number all to no avail.

But thanks for trying to help me.


Jane

[TraceyHand]

Jane, presumably the encryption number is still there each time you're checking?

Although it's not giving the same error as you'd usually get for the key being wrong.

In your Business Settings > Payments > Protx (configure method)

Have you checked your vendorname? (merchant id)
It should be the MAIN vendor name that you type in the TOP box when logging in, not the user name.

It might be worthwhile checking it with Protx themselves to ensure it is exactly correct (and the password)

[janeread]

hello Tracey,

a couple of times the encryption number got overwritten by 'testvendor' but not always, so that can't have been the problem.

I tried logging into the vendor panel with the vendor name (just in case, although I imagine all these details are generated automatically within Protx's system) and it worked fine. So I'm using the same word for the top field in the Protx admin login pannel and the merchant id in configure payment methods within Actinic. Is there anywhere else I should be putting this?

[Bruce]

Hi Jane,

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.

If you are using the actual key, switch it to production mode in Actinic and then update the site and test using the Protx test credit card details.

Kind regards,

[fergusw]

Jane,
We have found it always worthwhile reminding people that there are in fact 2 OCCPROTXScriptTemplate.pl files within Actinic.
Occasionally we have seen confusion over which one to change and what happens when you upgrade the OCCUpgrade.ini file. This can lead to problems.

The master OCCPROTXScriptTemplate.pl is located
C:\Program Files\Actinic v8\OCCUpgrade\CommonOCC

whereas the 'site' one relevant to the site, and the one Actinic uses when creating the checkout scripts etc is located
C:\Program Files\Actinic v8\Sites\Site1\CommonOCC

The standard protocol is to change the master script, increment the OCCUpgrade.ini file, then when Actinic next re-opens it overwrites the 'site' script with the new master one.

We always suggest you check the site file and make sure it is stating the correct info.

[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 saidBut 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:o
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/vspgateway/service/vspform-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.

[leehack]

I have nothing constructive to add Jane, but it's like reading a horror story this thread. Do yourself a favour and go for HSBC, it will probably setup quicker than PROTX. PROTX are past their best - HSBC, Barclays and Worldpay are far better solutions IMO.

I'm pretty sure what Bumpsy said is true, but they are now telling you the opposite, incredible, it really is.

[janeread]

I don't agree, Lee.

I have Protx running fine on another site, and I'm very happy with it there.

I do have merchant services already on the problem site where I process stuff offline, but many people don't like this as it is not that secure, and I think it is in breach of best practice, because even though the online encryption is secure, you then process them down an unsecure phone line from your office.

WorldPay etc. seem very expensive compared with the merchant service chrages I am paying and often you don't get access very quickly to your money.

What's that expression: what doesn't kill you, makes you stronger.

Jane

[leehack]

It's all down to opinions i guess as long as you are happy, that is all that counts. There are 20 PROTX problems to every 1 from the others I mentioned though, that is for sure. Maybe with PROTX it either sets up perfectly or you have a real pig of a job, so people either love or hate them etc.

So much IME is about who you get on the other end of the phone when you have a problem. It's even stranger if you have one site working and one not, that would lead me to compare the sites on all accounts.

As many of them seem to use the same system, perhaps you need a new secret key, that solved a number of Worldpay problems.

Can you do anything to try the details from your working site into the non working site or vice versa and confirm the problem lies with PROTX?

[TraceyHand]

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.
yeh, sorry..I misunderstood as it sounded like you were putting your details into the "testvendor" area..not in Actinic itself.

[fergusw]

TBH - I wish PROTX would rewrite their PSP integration toolkit for Actinic to include all 4 fields in the "configure Method" screen instead of having to amend this screen AND the script template perl file.
If they did this then the whole process would be much, much simpler IMO, and would eliminate possibly 80% of PROTX integration problems we see.

[leehack]

Correct the email problem also and have a set procedure to adhere to when actinic users ring up, WHOEVER you get on the phone will then know how to help. Now that would be a 'serious' PSP provider for actinic.

[fergusw]

Correct the email problem also and have a set procedure to adhere to when actinic users ring up, WHOEVER you get on the phone will then know how to help. Now that would be a 'serious' PSP provider for actinic.
It really should be straight forward if the PSP toolkit for Actini is developed by PROTX properly.

1. Register with PROTX
2. They send; vendorname, secret key, encryption password
3. Bang details, along with email address, into configure method screen and "PSP test mode" on
4. Email PROTX to check and wait for all clear
5. Switch to PSP "live mode" and bob is your...... palindromic uncle

Foolproof :rolleyes:;)

[leehack]

There should be no need whatsoever to go anywhere but the payments tab in actinic to setup a PSP IMO, period. If you have to, then frankly that is so 1990's.

[janeread]

I hope you are all sitting down to read this. Protx have now told me that the vendorname they gave me was too long!!!!!!!!

Is this worth posting prominently so that other people avoid the fiasco I have been through?. I also intend to write to the powers that be at Protx. It seems totally daft that their system allows someone to generate a vendorname that won't work because t's too long.

It has been shortened and the 3008 problem has gone, but now I'm getting error message 4006 TxType which is I understand about deferred payments. I don't want to accept deferred payments - does anyone know how I switch that off please?

[leehack]

Their incompetence has no boundaries it would appear, sheesh Jane, crap like that does nothing to make you stronger, all that does is scare the begeebers out of me. WTH are they playing at, yet another nail in their coffin from my side.

The setting you wish to change is on the configuration screen where you put in your secret key etc. You select pre auth or direct payment. Switch that and upload, hopefully that sorts it for you.

Glad you are on the road to correction anyway, you must be exhausted.

[janeread]

I thought it would get you going, Lee!

But I can't follow your instructions - when I go into Actinic Configure Method it gives me fields for vendorname and secret key plus two radio buttons for test mode or live.

Am I in the wrong place??

Jane

[leehack]

Sounds like you are in correct place to me but seeing different options, have you ran over a black cat lately Jane? Screenshot of what i see is attached below.

[TraceyHand]

that setting only appears in 8.5.2, Jane.
If you're not on 8.5.2, then you won't find it.

[leehack]

Well deduced Tracey Clueso, had me beat. What a dilemna, upgrade or stay on payment method you don't want. Stick with the payment method IMO. You'll be on pre-auth by law in the not too distant future anyway Jane.

[janeread]

The nice man from Protx phoned me this morning to see if it was sorted and I told him the problem I was having with the deferred payment error message.

He sent me instructions how to sort it, so i thought I'd post it in case anyone eles has the problem. The instructions are for changing to deferred payments, but I needed to change DEFERRED to PAYMENT rather than the other way round. Here's the instructions:


Actinic requires you to amend code in your shopping cart setup to use the DEFERRED transaction type.

Currently your TXType that you send to us will be 'PAYMENT'

If you wish to use 'DEFERRED' you will need to change the TXType in your OccProtxScripttemplate.pl file in your Actinic directory from:

'PAYMENT' to 'DEFERRED'



Amend your OCCProtxScriptTemplate.pl file

The OCCProtxScriptTemplate.pl file is located in the commonOCC folder in the OCCUpgrade folder within your Actinic directory. Open the file in an editor like notepad and search for 'TxType':

$sHiddenValues .= "INPUT TYPE=HIDDEN NAME=\"TxType\" VALUE=\"PAYMENT\">\n";

You will need to change the TXType from PAYMENT to DEFERRED

$sHiddenValues .= "INPUT TYPE=HIDDEN NAME=\"TxType\" VALUE=\"DEFERRED\">\n";

Then save the file.


Amend the OCCUgrade.ini file

The OCCUgrade.ini file located in the root of the OCCUpgrade folder in your Actinic directory. Open the file in an editor like notepad.

At the top of the file are the lines that look like this:

[Version]
Number=1045 (for example)

Increment this Number (so if it was 1045 for example, you will need to change the value to 1046) by 1 and save the file.


Open up Actinic

You should get a message informing you that a change has been made to your Payment Provider data and that it has been.

When you amend your Actinic code to use a certain transaction type, all your transactions will then be processed as that transaction type.

[Bruce]

Hi Jane,

Just to comment on Is this worth posting prominently so that other people avoid the fiasco I have been through?. I also intend to write to the powers that be at Protx. It seems totally daft that their system allows someone to generate a vendorname that won't work because t's too long.

It has been shortened and the 3008 problem has goneIf you take a look at http://techsupport.protx.com/actiniccartguide.asp you will see under the FAQ section that the answer to the TxVendorCode error has 'The encryption password is the 16-character string that will look something like:' so cant understand why they advise that when it should be 15 instead.

Regards,

[janeread]

Hi Bruce,

it's not the encryption password that was wrong, it was the vendorname - this was given to me by them and was 16 characters long. When they shortened it to 8 charcaters all that problem disappeared immediately. On a subsequent conversation I asked the Protx guy how many characters was maximum and he said 15.

Jane