22.0 FTP Server Messages
The following includes messages from the NWFTPD.NLM and FTPUPGRD.NLM.
Failed to bind to FTP port
Source:
NWFTPD.NLM
Explanation:
The port that the FTP Server is trying to bind to is busy.
Possible Cause:
Another instance of the FTP Server or another application is bound to the port.
Action:
Unload the application that is bound to the port, bind the FTP Server to a different port, or delete the busy port from TCPCON.
Failed to initialize Anonymous user
Source:
NWFTPD.NLM
Explanation:
The FTP Server failed to create an Anonymous user.
Possible Cause:
Incorrect data was entered to create the user.
Action:
Enter nwftpd -a [-c config_file].
Failed to add Anonymous User object to NDS
Source:
NWFTPD.NLM
Possible Cause:
The user entered has insufficient rights.
Action:
Ensure that the user has sufficient rights.
Failed to generate an ObjectKeyPair
Source:
NWFTPD.NLM
Possible Cause:
The user entered has insufficient rights.
Action:
Ensure that the user has sufficient rights.
Failed to open configuration file
Source:
NWFTPD.NLM
Possible Cause:
The configuration file is not available at specified location.
Action:
Verify if the configuration file is available at the specified location.
Unable to find default configuration file
Source:
NWFTPD.NLM
Possible Cause:
Configuration file is not available at default location (SYS:/ETC).
Action:
Verify if the configuration file is availabl at the default location.
Unable to locate Anonymous user in default context
Source:
NWFTPD.NLM
Possible Cause:
Anonymous use does not exist at the FTP Server’s context
Action:
Run nwftpd -a to create anonymous user and reload NWFTPD.NLM.
USAGE : nwftpd [-c <Config File>] [-a]
Source:
NWFTPD.NLM
Possible Cause:
The user might have tried to load NWFTPD.NLM with wrong usage.
Action:
Load NWFTPD.NLM by typing only the NLM name for default configuration file, or ftpupgrd [-c config_file] for specific configuration file name or nwftpd [-a] for creating anonymous user.
Could not create the .cfg file.
Source:
FTPUPGRD.NLM
Possible Cause:
Configuration file does not exist for ftp server upgrade, or existing configuration file has read only access.
Action:
Modify the file access if it is read only or specify proper configuration file name with ftpupgrd [-c config_file] usage.
Could not create the FTP Server Restriction file.
Source:
FTPUPGRD.NLM
Possible Cause:
Restriction file does not exist for ftp server upgrade, or existing Restriction file has read only access.
Action:
Modify the file access if it is read only or specify proper restriction file name.
Source:
FTPUPGRD.NLM
Possible Cause:
Configuration file does not exist for FTP server upgrade, or existing configuration file has read only access, or restriction file does not exist for ftp server upgrade, or existing Restriction file has read only access
Action:
Modify the file access if it is read only or specify the proper configuration file name with ftpupgrd [-c config_file] uusage. Modify the file access if it is read only or specify proper restriction file name.
Correct Usage: ftpupgrd [-c <Config File>]
Source:
FTPUPGRD.NLM
Possible Cause:
The user might have tried to load FTPUPGRD.NLM with wrong usage.
Action:
Use the specified user command ftpupgrd [-c config_file].