Send
Trouble |
Measure |
---|---|
Unable to connect to a remote host |
Make sure that the ping command ends successfully. Run the command as follows in the command prompt (MS-DOS): > ping remote host name If the command does not end successfully, check the following points:
|
Make sure that the receive port number of the remote host matches the port number defined in the Host Information of the local host. |
|
Unable to open send files |
Check whether the file exists under File Name (FILENAME) in the Send Management Information. |
Make sure that the Send file is not being used by other processing. |
|
A communication error occurs |
Check whether the host on the receiving side has forcibly terminated the receiving. |
Check whether a socket read time-out has occurred on the host on the receiving side. |
|
Make sure that the settings of devices, such as routers, and the setting of the LAN environment are correct. |
|
A request to cancel sending has been accepted successfully, but it takes quite a long time until the cancelation actually takes place |
When you cancel sending, even if the request is accepted successfully, it may take time until the cancelation actually takes place in the following cases:
|
Unable to send a file that uses network resources (networked files) |
If HULFT operates under the system account, HULFT may be unable to log in to the server that stores the target file. Make sure that the permission to access the target file and the permission to access the path that is specified for Path to Location for Cross-Product Sharing (hulsharepath) in the System Environment Settings are granted to the account that started HULFT. |
Make sure that the target file is not being used by HULFT on another host or by another application. |
|
Check that the path to the file is specified in a UNC format. |
|
Check the following points on the server that stores the file:
|