Title
 Overview
 Features
Setup
 

Choosing a Package

Connectivity

Install Windows

Install macOS

Install Others

License Codes

Adding Users

Performance

servedat Server
 

Access

Users

Home Directories

Access Privileges

SysAuth

AuthFile

AuthHandler

mkpasswd

Features

Host Groups

Encryption

Compression

Upload Status

Capacity

Monitoring

Logging

Object Handlers

Structured Lists

Configuration

Configuration File

Negotiation

Options

Web Integration
 

Web Clients

expedat:// URLs

JavaScript API

HTTP API

WebDat Ref UI

Server Dashboard

Landing Page

Web File Browser

Desktop Client
 

Basics

Interface

Authentication

Browsing

Getting

Sending

Copying Folders

Canceling

Resuming

Errors

Advanced

Encryption

Compression

Automatic Retry

Multitasking

Web Integration

Object Handlers

Branding

Maintenance

Renaming Files

Deleting Files

New Folders

Name Filters

Configuration

About

Options Window

Settings

Embedding

Priority

movedat Client
 

Basics

Browsing

Getting

Sending

Copying Folders

Authentication

Canceling

Resuming

Advanced

Encryption

Compression

Displaying Files

Path Completion

Maintenance

Renaming Files

Deleting Files

New Folders

Automation

Automatic Retry

Wildcards

Filters

Object Handlers

Piping Files

Logging

Structured Lists

Reference

Errors

Exit Codes

Configuration File

Options

DropDat
 

Creating Droplets

Changing Droplets

Sending Files

Pause & Abort

Automatic Retry

Distribution

Filters

Command Line

Limitations

Mobile Client
 

Adding Servers

Sending Files

History

Limitations

WebDat
 

Installation

Status Menu

Selection Dialogs

mtping Utility
 

Servedat Status

Latency

Load Monitoring

Route Tracing

Response Output

Transaction Report

Option Summary

Support
 

Revision Codes

Known Issues

Troubleshooting

 Legal Notices

Errors

movedat reports error messages as they occur.  By default errors are written to stdout.  If stdout is being used for piping, listing, or output display, or if Quiet mode is enabled, then errors will be sent to stderr instead.

Most error messages will include a brief explanation and suggestions for correcting the problem.  To receive errors and other reports in a structured format, use the Logging feature.  Common errors are described below as well as in the Troubleshooting chapter.  A complete list of MTP/IP errors can be found in DEI Technical Note 0013.

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 Network 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 indicate a network connectivity problem, that the ExpeDat server is not running, 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 DEI Technical Note 0002 for firewall configuration instructions.

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 authentication, make sure that the username and password you have entered are correct.

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.

Object Busy: Try again later
The file you are attempting to access is being used by another transaction or application.  If it is being uploaded by another ExpeDat transaction, you may receive an estimate of when it is expected to complete.

Server Capacity Exceeded: Try again later
The server may be beyond its configured capacity.  Try your transaction again later.  If the problem persists, contact the server administrator.

Feature not supported by software license
The specified server does not support one or more features requested by movedat.  For example, you may be attempting to download a structured directory listing from a server which is not licensed for application integration.

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