Tech Note 0027
License Registration Errors
Common errors received when registering an MTP/IP license code
Most non-trial MTP/IP software requires a valid license code. This code is typically entered once when the software is first installed and then saved for future operation. If your software requires a license code, it will be found in the MTP-Codes.pdf document which you can download from your customer site.
Refer to the Setup chapter of your product documentation for more information about how to register a license code.
If a license code is not valid, MTP/IP will return an error code and may display one of the following MTP0 diagnostic messages below.
Steps to Correct
Download the latest license code document from your customer site or verify with your administrator that you have the latest code.
Download the latest distribution package from your customer site or verify with your administrator that you have the most recent package. See Tech Note 0001 for guidance on determining the software version you are running.
Make sure that the license code you are using matches the software you are registering.
For host-bound server licenses, make sure that the host identifier of the system you are installing on matches that of the license. See Tech Note 0007 for more information about host binding.
Make sure that you are not trying to install a trial or older version of the software. See Tech Note 0012 for guidelines on installing new MTP/IP software over existing MTP/IP software.
Perform all registration operations using a local administrator account. If you attempted to register a license while logged in as a Windows domain administrator and are now receiving "Improperly formatted license code" or "Invalid license code" errors, see License Storage below for instructions.
Contact DEI technical support for help.
After an MTP license code is validated, a license token is stored in a host-specific location for future use. This token is tied to the CPU on which it was created and will not work if copied to other CPUs. This may create conflicts in environments with clustered storage or when installing from a Windows domain administrator account.
On unix systems, including macOS, the license tokens for servers and command-line clients will be saved in ~/.dei-mtp and copied into /etc/dei-mtp if this file is writeable. Placing the token in /etc/dei-mtp registers the application for all users of the system.
On macOS systems, graphical clients store license tokens in their preferences databases: ~/Library/Preferences/com.dataexpedition.DropDat.plist or ~/Library/Preferences/com.dataexpedition.ExpeDat-Desktop.plist.
On Windows systems, the license token will be saved in the Current User class under dei\mtp and copied into the Local Machine class if that is writeable. A backup token will also be placed in the LocalAppData folder in the file dei\dei-mtp.dat. It is important to register server licenses as the same local admin user that will be used to run the service. If you use a domain administrator to install a server, or fail to run the installer "As Administrator", the Windows Service may fail to launch.
When installing server software on a Windows system, do so while logged into a local Administrator account. Installing server software as a domain user may result in "Improperly formatted license code" or "Invalid license code" errors at run time.
If you change your hardware configuration, you may be required to re-enter your license code. For example, the first time you switch from an ethernet to a wireless network, you may need to re-enter your code.
If an application repeatedly asks for a license code, or if it fails to start with "Improperly formatted license code" or "Invalid license code" error, then the license tokens may be corrupt or there may exist multiple conflicting codes.
Contact DEI technical support for help if these steps do not resolve the problem.
Tech Note History
|Oct||22||2021||Updated license storage locations|
|Oct||08||2021||Updated formatting and instructions|