movedat Errors

Error messages are written to stderr as they occur.  Most error messages will include a brief explanation and suggestions for correcting the problem.  You may also refer to the following list for more details:

No Application at Given Port
movedat is able to reach the machine you specified, but no server is running there.  Check that you entered the correct server name and port, and that servedat is running on that machine.

No Response, ICMP Prohibited, or Nework Down
movedat is unable to reach the server.  Check that you are connected to the network, that you entered the correct server name and port number, that servedat is running on that machine, and that any firewalls have been configured to allow ExpeDat through.

Operation Timed Out
The transaction has been canceled because there has been no contact with the server for a long time.  If this occurs at the start of the transaction, it may mean that you are not online, that the server is not running ExpeDat, or that you entered the wrong address or port number.  If this occurs after a transaction has started, it indicates a loss of network connectivity, such as your Internet connection or the server going down.  This can also happen if there is a dynamic firewall which is configured to block high-volume UDP traffic.  See the Troubleshooting chapter for firewall tips.

Invalid Pathname
The server did not recognize the Remote Path.  Check that your remote path is typed correctly, and that any special characters are properly quoted or escaped.  This error may also occur if the server and port you specified is not running an ExpeDat application.

Bad Credentials, Username, or Password
If the server requires a username and password, make sure that you have entered these correctly.

Request Denied
You do not have permission or access rights to perform the requested transaction.  If the server requires a username and password, that username may lack sufficient access privileges on the server.

Server Busy: Try again later
The server may be beyond its configured capacity or it may be running low on memory.  Wait a few minutes and try your transaction again.  If the problem persists, contact the server administrator.

If you receive a different error whose cause is not self-explanatory, contact your system administrator or refer to the Troubleshooting chapter.