TestNow Messages and Troubleshooting Tips
The following table includes the status messages generated during Testnow for HTTP and AS2. Following the table are additional troubleshooting tips to assist you in getting your trading partner profiles up and running.
Outcome | Message | Explaination/Action |
---|---|---|
Checking Profile | ||
Success | Profile <profile name> is active | None |
Failure | Profile <profile name> is not active | Verify profile is enabled. Enable the profile on the Trading Partner > Advanced > Profiles list or search results. |
Checking Delivery Channel | ||
Success | <delivchan_delivery_channel_name> is active | None |
Failure | <delivchan_delivery_channel_name> is not active | Verify delivery channel is enabled. Enable the channel on the Trading Partner > Advanced > Delivery Channels list or search results. |
Checking Certificates | ||
Success | None | |
Failure | Certificate Information not valid | Expired certificate building outbound message. Check signing and exchange certificate used in organization profile. |
Failure | Error: decryption-failed | Receive MDN test warning (MDN received but with errors). Expired certificate when parsing MDN. Check signing and exchange certificate used in partner profile. |
Checking Transport | ||
Success | <transport_transport_name> is active |
None |
Failure | <transport_transport_name> is not active | Verify the transport is enabled. Enable the transport on the Trading Partner > Advanced > Transports list or search results. |
Checking HTTPClientAdapter | ||
Success | HTTPClientAdapter is enabled | None This verifieds that the default HTTP Client adapter configuration is enabled. |
Failure | HTTPClientAdapter NOT enabled | Verify the HttpClientAdapter is enabled. Enable the default HTTP Client adapter configuration shipped with the application (this is the configuration used by TestNow). This indicates that the default HTTP Client adapter configuration has been disabled somehow. Go to Deployment > Services > Configuration, and list the HTTP Client adapter configurations in the system. In the results, check Enabled next to the default HTTP Client adapter configuration, which is named HTTP Client Adapter. |
Checking Contracts | ||
Success | <contract name> is active | None |
Failure | <contract name> is not active | Verify contract is enabled. |
Proxy Connection | ||
Success | Completed successfully | None |
N/A | Not configured to use a proxy | Indicates that no proxy server was defined in the profile. |
Failure | Unknown Host | Verify the host information entered in the Firewall Proxy field of the configuration, and that the format of that field is <host address – mandatory>[,<port – optional][,<user>,<psw>] There are four possible values, separated by commas. The last two, if specified, are used for basic authentication. Examples: localhost localhost,80 localhost,80,authuser,authpsw |
Failure | 401.Unauthorized | Invalid basic proxy authentication. Check username and password used for proxy basic authentication |
Failure | Error | Check status report and the Application logs for more information. The logs are located in the logs folder beneath the Application <install_dir>. In particular, you may want to check the system.log, Perimeter.log, and httpclient.log |
Failure | Unknown host - <transport proxy | adapter proxy | global proxy>: <proxy name> Example: Unknown Host – transport proxy: invalid.proxy.name |
Verify the proxy host specified in either the transport, adapter, or global proxy. |
SSL Connection | ||
Success | Completed successfully | None |
N/A | Not configured to use SSL | Indicates that SSL was not selected during profile configuration. |
Failure | Unknown Host | Indicates a problem with the host information specified in the endpoint. |
Failure | SSL Handshake Failure | The profile is configured to perform SSL but could not establish an SSL connection, possible causes include: The server is not configured to do SSL Problem with the security credentials Problem with certificates used with SSL |
Failure | Error | Check status report and the Application logs for more information. The logs are located in the logs folder beneath the Application <install_dir>. In particular, you may want to check the system.log, Perimeter.log, and httpclient.log |
Failure | Server may require SSL | The client was not configured to perform SSL, but the server is expecting it. Verify the SSL configuration information with the host. |
HTTP Connection | ||
Success | Completed successfully | None |
Failure | Unknown Host | Indicates a problem with the host information specified in the endpoint. |
Failure | Server may require SSL | Indicates that this profile is not configured for SSL, but that this server may require you to use SSL. |
Failure | Handshake Failure | The profile is configured to perform SSL but could not establish an SSL connection, Possible causes include: The server is not configured to do SSL Problem with the security credentials Problem with certificates used with SSL |
Failure | Error | Check status report for more information. |
Failure | 404:Not Found | Invalid endpoint HTTP connection test. Verify endpoint specified in the transport is correct. |
Failure | Unknown Host | Invalid host HTTP connection test. Verify host specified in the transport is correct. |
Failure | Error. Status report contains “Could not complete connection to specified host” |
Invalid port HTTP connection test. Verify the port specified in the transport is correct. |
Additional TestNow Troubleshooting Tips
If you run the TestNow option for a trading partner profile and it fails, first review the TestNow Messages table to see if the resolution is covered there. If not, here are some other possible issues and resolutions:
Problems Accessing the TestNow Option
- On the Admin Console, select Accounts > User Accounts to see the Accounts page.
- Search for the user account and click the name in the search results to see that account's settings.
- Check that the TestNow permission is assigned.