The online FAQ database contains hundreds of answers to frequently asked questions, articles on using our
web server applications and other related technologies, and resolutions to common problems. If you are seeing
an error message, be sure to try searching on the error message or error number that you are seeing.
|
| |
| |
| |
| |
|
I cannot get transactions to process using the Verisign PayProFlow interface. I keep getting errors I cannot figure out how to fix.
|
|
|
When you receive an error message, always be sure to copy and paste the text into your inquiry to make it easier for the person answering your questions to give you a more specific answer. Verisign PayProFlow utilizes software that must be installed and configured properly on the web server. If you using an ISP hosted server, you might need to contact your web host for help. The following information is geared towards those who are managing their own web server. The first step is to always review the Verisign documentation in detail and make sure you followed all the steps precisely during the installation.
The first thing to check when trying to diagnose a problem with the Verisign PayProFlow software, is to use the xcDiag utility to see if the web server is at least recognizing that the Verisign software is installed. If it is reporting that it is not installed, double-check the Verisign installation instructions and try re-installing. If you need to re-install, be sure to run the uninstall procedure, then reboot the server before attempting to install the software again. Once installed, try the xcDiag utility again to make sure that the web server is recognizing that the Verisign software is installed.
If you see an error message like the following:
1 (User authentication failed)
This error typically indicates that you may have a typographical error in the Partner, Vendor, User or Password settings. Double check all your settings and make sure these match exactly.
If you see an error message like the following:
-31 Certificate Chain failed to Validate, no local certificate found CERT Path = CERTS: Working directory: c:\WINNT\system32
There are two possible resolutions. First, be sure to follow the Verisign documentation exactly and set the environment variable PFPRO_CERT_PATH to the path where your certificate files are to be stored on the web server. This folder must have read access by the Everyone group in order for the web server to read the certificate files.
If that does not seem to help, then despite what the Verisign documentation says, move your certificate directory to the folder listed in the error message. The folder will probably be the same as shown above, but can differ if your Windows installation was installed to a different path.
|
|
|
|
| |
