There are several ways to view connection error messages:
Connection failure indicator in Systems Information view |
---|
![]() |
Error: | Connection timed out: connect or UnknownHostException: <IP address or host name> |
---|---|
Explanation: | Incorrect IP or host name |
Actions: |
Verify entered IP address or host name is reachable from your machine: You can use the ping tool to check whether the IP address is reachable.
Look for messages appearing which start with Reply from <IP address or host name> such messages indicate that the address or host name is reachable from your machine. If you do not see such messages, or if you see Request time out. messages, then you need to speak with your network administrator. Note that in some cases, IP addresses which are accessible from your machine may not respond to ping if the administrator of the system has disabled this functionality (or network administrator has blocked this, for example using a firewall) - speak with your system administrators and/or network administrators to determine whether this is the case; if it is, using the ping tool will not provide any useful diagnostic information. |
Error: | Connection refused: connect |
---|---|
Explanation: | File Manager® server not installed, incorrectly configured, or not running |
Actions: |
Verify File Manager® is running on chosen port: If you have the Telnet tool installed, you can use the Telnet tool to attempt to connect to the File Manager® server:
If a black window opens and says it is Connecting and then goes blank, the File Manager® server is running on the entered IP address and port. If a black window opens and says it is Connecting and then disappears shortly after, or if you get an error message complaining that Telnet is unknown, cannot be found, or is an invalid command, then the File Manager® server is not running on the entered IP address and port. Verify File Manager® Configuration is correct: Speak to your mainframe system administrator to verify that the File Manager® server is installed and running correctly on the specified IP address or host name and port number. |
Error: | Invalid authentication credentials |
---|---|
Explanation: | Incorrect username and/or password |
Actions: |
Verify your username and password are correct: Try connecting with another tool or speak to your mainframe system administrator. |
Error: | Failed to communicate with the server because the server was unable to start your session under your user ID. You may not have the privilege to access the File Manager® server. Please consult your systems administrator. |
---|---|
Explanation: | Entered user may not have the privilege to access the File Manager® server |
Actions: |
Attain the privileges required to access the File Manager® server: Contact your mainframe system administrator to make sure you are authorized to use the File Manager® server, and have your system administrator grant you the privileges required to access the File Manager® server if you are not currently authorized. |
If you encounter any problems while using the product, follow the steps below and contact the IBM support team.
Clear your output queue on your mainframe system. This is optional, but makes retrieval of the correct set of File Manager® host tracing information easier.
Clear the current log by selecting Clear File Manager Log from the drop down menu (the view menu) of the Systems Information view.
![]() |
![]() |
Open the Preferences dialog
Navigate to the File Manager® general preference page and tick Run IBM File Manager in Debug Mode, click Apply, then click OK.
Close all connections to the relevant system
![]() |
![]() |
The local log file(s) are located in your Eclipse workspace directory:
The current log file will be called pluginlog.log. If this log file grows larger than 10mb, it will be moved to pluginlog.log.1 and a new log file (also called pluginlog.log) will be created. Subsequent logs will follow this naming pattern.
Usually it is enough to provide only the current log file (as is done in the step-by-step walk-through above), however if troubleshooting an issue with large sets of data, all log files may be required to troubleshoot a problem. To include the full log files in a report, follow the steps detailed in the General Problem Diagnostics, with the following modifications: