Locked transfer admissions - possible causes and remedies
If FTAC rejects a file transfer request on account of an invalid transfer admission, the cause may be one of several:
No transfer admission was defined when the FT profile was created or modified.
A user wished to create an FT profile with a transfer admission which was already assigned to a different FT profile on the computer. If the relevant FT profile is marked as private, the transfer admission becomes invalid. At the same time, the values for date, scope (public/private) and validity (-d, -u and -v) are set to the default values.
The FTAC administrator modifies an FT profile for a user without knowledge of the complete login authorization. In this case, the transfer admission remains valid, but is locked.
The FT profile was imported by an FTAC administrator who is not the FT administrator. It is therefore locked automatically.
The FT profile was locked explicitly.
The period during which the transfer admission may be used has expired.
The detailed output of the ftshwp command displays the cause of an invalid transfer admission using the additional output parameter TRANS-ADM. The possible values for this output parameter, the meanings and counteractions are shown in the table "TRANS-ADM" in the ftshwp command.