8.6.3 User Agent Troubleshooting

Following are some User Agent errors and their most common causes:

Send action has failed

If the user receives this message when trying to send a file, then your server has reported an error. In this case, more information can be found by checking the Response tab in the User Agent window.

If the response contains the text "JSMDirect transaction did not complete", then JSMDirect on your server either could not find the appropriate DC@W29 or dc_w29.txt entry, or could not execute the LANSA function. Check the HTTP server job log on IBM i, or jsmdirect.log on Windows or Linux.

If the response is some form of server error, then check the HTTP server configuration or the URL being used.

Connection refused or timed out

If the user receives a java.net.ConnectException, then the User Agent was unable to open a socket connection to your server. Check that the port number in the configuration file is correct, and check that your HTTP server is running. It is also possible that either you or the end user has a firewall that is blocking this connection.

Unknown host

If the user receives a java.net.UnknownHostException, then the host name in the configuration file may be incorrect, or the client running the User Agent may not be able to resolve the host name due to DNS issues.

Class not found

If the user receives a message that a class has not been found, or support for some feature has not been installed, then it is possible that some extra JAR files need to be included with the User Agent. Refer to 8.6.2 What Needs to be Installed? for more information. Additionally, it is possible that the user is using an older version of Java; the User Agent requires JRE version 1.4.