Skip to main content

SMA File Transfer Messages

The following error and informational messages may be encountered in the *SMA/FTAGENT.

MessagePossible Cause/Recommended Action
** Bad CRC ***Internal error – contact SMA Technologies.
** Can't write to FTSERVER **Check the status of the FTServer on both machines.
Agent cannot delete source fileVerify privileges.
Bad CRC from AgentInternal error – contact SMA Technologies.
Can't agree on a CommonCharSetInternal error – contact SMA Technologies.
Can't create destination fileVerify privileges.
Can't read msg from HandlerCheck the status of the SMA/FTHANDLER#.
Can't write to AgentCheck the status of the FTAgent on both machines.
Can't write to HandlerCheck the status of the SMA/FTHANDLER#.
Can't write to ServerCheck the status of the FTServer on both machines.
Can't write to transfer fileVerify privileges.
Compression is not supportedRemove Compression requirement from OpCon job.
Configuration file is missingCheck configuration.
Data type mismatch for appended fileExisting file EXTMODE does not match transfer type on an "Append" transfer.
Dest file exists; No overwrite"Do Not Overwrite" has been specified on the transfer job.
Encryption is not supportedRemove Encryption requirement from OpCon job.
File exists and overwrite not permitted"Do Not Overwrite" has been specified on the transfer job.
File is not availableVerify privileges.
FTAgent configured for non-TLS only; job requires TLSThe machine properties as defined within the OpCon database indicate that the MCP FTAGENT will support transfers using a connection secured by TLS, but the LSAM configuration setting for SMAFT security (the Sec? field) indicates that all transfers require that the connection NOT be secured with TLS.
FTAgent configured for TLS only; job requires non-TLSThe machine properties as defined within the OpCon database indicate that the MCP FTAGENT will support transfers using an unsecure connection, but the LSAM configuration setting for SMAFT security (the Sec? field) indicates that all transfers require that the connection be secured with TLS.
FTAgent is unresponsiveCheck the status of the FTAgent on both machines.
FTServer is unresponsiveCheck the status of the FTServer on both machines.
FTServer OPEN errorCheck the status of the FTServer on both machines.
FTServer OPEN warningCheck the status of the FTServer on both machines.
Inv fileclass for src datatypeUsually caused by attempting to transfer a stream file using a text transfer mode.
Invalid <CommonCharSet>Internal error – contact SMA Technologies.
Invalid destination file data typeThe existing file's EXTMODE is not compatible with the job's destination file data type (usually ASCII vs EBCDIC).
Invalid destination file titleThe destination file title does not conform to MCP file naming syntax (check for quotes if the file name contains a period).
Invalid FILECLASS for Source fileThe source file's FILECLASS is not compatible with the job's source file data type (usually text vs binary).
Invalid source file data typeThe source file's EXTMODE is not compatible with the job's source file data type (usually ASCII vs EBCDIC).
Invalid source file titleThe source file title does not conform to MCP file naming syntax (check for quotes if the file name contains a period).
Invalid value for FTAGENT portCheck configuration.
Invalid value for SMAFT_IN_USE flagCheck configuration.
IP Addr Err: Insufficient spaceInternal error – contact SMA Technologies.
IP Addr Err: Invalid VersionInternal error – contact SMA Technologies.
IP Addr Err: Invalid Address VersionInternal error – contact SMA Technologies.
IP Addr Err: Invalid DataInternal error – contact SMA Technologies.
IP Addr Err: Missing right bracketInternal error – contact SMA Technologies.
IP Addr Err: Internal library faultInternal error – contact SMA Technologies.
IP Addr Err: Unspecified errorInternal error – contact SMA Technologies.
Msg size nnnnnn exceeds allowed len, where nnnnnn is the reported message sizeThis is a protocol error. Please enable debugging on both SMA File Transfer components, attempt to rerun the File Transfer job, and contact SMA Technologies.
No open socketsCommunication issue – check the status of the FTAgent and FTServer for both platforms.
No rec seps in max rec len (65535)Specify a record length on the MCP file to circumvent this issue.
No rec seps in data - use ',REC='Specify a record length on the MCP file to circumvent this issue.
No record seps in data - use ',REC='Specify a record length on the MCP file to circumvent this issue.
Outgoing transfer not allowedCheck configuration.
Packet number errorInternal error – contact SMA Technologies.
Preferred settings not accommodatedThis is a warning. It indicates that Compression/Encryption were preferred, but could not be accommodated.
Printerbackup file – use binaryThe source file is a printerbackup file and a text mode (ASCII/EBCDIC/Default Text) was specified. Change the mode to Binary.
'Push' transfer not allowed"Run on Destination machine" was specified but either the FTAgent or FTServer cannot accommodate this request.
Received an invalid requestInternal error – contact SMA Technologies.
Requested file not foundThe source file could not be located.
Server cannot delete src fileThe FTServer attempted to delete the source file following the transfer, but was unable to do so. Check privileges.
Server does not support 'delete'The job specifies that the source file is to be deleted following the transfer, but the FTAgent or FTServer does not support this functionality.
Server does not support 'push'"Run on Destination machine" was specified but the FTServer cannot accommodate this request.
SMA File Transfer not allowedCheck configuration.
SMAFT is not enabled for this LSAMCheck configuration.
SMAFT is permitted for outbound xfr onlyCheck configuration.
Unable to read source fileThe source file could not be read. Check privileges.
Unable to send status msgThe FTAgent is unable to insert a job status message into the SMA/OUTBOUND/FILE. Look for *SMA/ALGOLPROCS in the waiting mix, probably waiting on sectors.
Unable to write to transfer fileThe temporary, interim transfer file could not be written to. Check privileges and disk space.
Undefined msg type:Internal error – contact SMA Technologies.
Unrecognized Action valueInternal error – contact SMA Technologies.
Unsupported file type:Internal error – contact SMA Technologies.
Variable length records not specified.Internal error – contact SMA Technologies.