CAS Errors

 CAS Overview

The following list contains commonly occurring CAS and fax server errors, that are typically caused by calling CAS functions with invalid domain, server or user information, or by attempting to send a fax with invalid recipient or content information.  Error codes are obtained by reading the STATUS_NUM tag in response taglists from CAS functions.  For errors in completed messages, see the MESSAGE_COMPLETION_CODE tag.

Error Error Name
Description
4096    ALREADY_LOGGED_ON The LOGON function failed because the CAS instance to be logged onto a NET SatisFAXtion connection router was already logged on to a connection router.  Be sure to call LOGOFF when a CAS instance no longer needs to be logged on to a connection router.
4099 SERVER_QUERY_FAILED The LOGON function failed because the server specified by the DOMAIN_NAME tag could not be found on the network according to the specified PROTOCOL.  Verify that the DOMAIN_NAME is properly formatted as \\DOMAIN\SERVER and that it matches the name of a currently running fax server.
4101 NOT_LOGGED_IN The OPEN_SESSION function failed because an attempt was made to connect to a server using a CAS instance that had not been properly logged on to a NET SatisFAXtion connection router. 
4102 NO_OPEN_SESSION The CAS Send method failed because an attempt was made to send a function taglist using a CAS instance that did not currently have an open session with a CAS server.
4103 ALREADY_OPEN_SESSION The OPEN_SESSION function failed because an attempt was made to open a session using a CAS instance that already had an open session with a CAS server.
4107 INVALID_TAG_CMD A CAS method or function rejected the function taglist because it either lacked a required tag, or it was malformed.
4111 DST_NOT_FOUND The OPEN_SESSION function failed because the server name specified in the REMOTE_LOGON_NAME tag could not be located within the NET SatisFAXtion domain. 
4113 INVALID_LOGIN The LOGON function failed because the connection router for the NET SatisFAXtion domain already included the user name specified in the LOGON_NAME tag, or the name was invalid (blank, too long, or contained invalid characters).  The LOGON_NAME can be randomly generated to avoid conflicts between different CAS clients.  Be sure to call LOGOFF when a CAS instance no longer needs to be logged on to a connection router.
4116 SESSION_TIMEOUT A CAS method or function failed because a CAS session had been closed automatically for having been open too long without any activity.
4117 TIMEOUT A CAS method or function failed because the remote CAS server took too long to respond to a function request. 
4119 REQUIRED_TAG_MISSING The function failed because a required tag was missing in the function taglist.  For the LOGON function, ensure that LOGON_NAME and DOMAIN_NAME tags are properly set.
4120 FILE_NOT_AVAILABLE The GET_FILE_FUNCTION function failed because the file from a message specified in the CURRENT_FILESPEC tag did not exist or could not be accessed by the fax server.
4131 USER_NOT_FOUND A CAS function failed because the name specified by the REGISTERED_NAME or USER_NAME tag in a function taglist was not found in the NET SatisFAXtion user list.
4132 INVALID_PASSWORD A CAS function failed because the name specified by the REGISTERED_PASSWORD tag in a function taglist was not the password for the user specified by the REGISTERED_NAME tag.  Passwords must be encrypted by the CAS EncryptOnce method before being added to a taglist in the REGISTERED_PASSWORD tag.
4134 PRECONVERSION_FAILED The SEND_MESSAGE function failed, or the MESSAGE_COMPLETION_CODE tag for a completed message is set to this error because the fax server was unable to convert the message attachments for fax delivery.
4135 MESSAGE_NOT_FOUND A CAS function failed because the message handle specified in the MESSAGE_HANDLE or SPECIFIED_MESSAGE_HANDLE tag in a function taglist was either invalid or not associated with a message on the fax server. 
4139 ACCESS_DENIED A CAS function failed because the user specified by the REGISTERED_NAME tag in a function taglist did not have the necessary privileges to perform the requested function.  Most functions will allow a user to access or modify their own messages, and a supervisor to access and modify messages belonging to any user.
4140 SERVER_SUSPENDED The SEND_MESSAGE function failed because the server has been suspended and was not accepting new messages.  The server is in a suspended state while loading, and can become suspended if available disk space is insufficient.
4208 VALIDATION_ALL_FAILED  The SEND_MESSAGE function failed because all recipient addresses specified in RECEIVER_ADDRESS tags failed validation by the Validation Server.  Validation rules can be modifed by selecting the "Validation Editor..." option from the Tools menu in the NET SatisFAXtion Administration program.  In addition to modifying validation rules, the Validation Editor allows fax numbers to be tested to see what will pass or fail validation.
4209 VALIDATION_ANY_FAILED Multi-address messages retrieved from the fax server with the GET_Q_ENTRIES_INFO function will include a  MESSAGE_COMPLETION_CODE tag set to this error if one or more, but not all recipient addresses failed validation by the Validation Server.
4214 LOAD_FILE_FAILED The SEND_MESSAGE function failed because a file specified by the CURRENT_FILESPEC tag in a CONTENT_PART section of a message taglist could not be found or accessed by the fax server.  The content for a message can be contained in the CONTENT_DATA tag, or supplied by referencing a file already on the fax server, copying a file to the fax server, or by specifying a URL.  Ensure that all tags in the CONTENT_PART section are set properly based on the method being used.  These tags include CONTENT_DATA, CONTENT_TYPE, COPY_ATTACHMENT, ORIGINAL_FILENAME and CURRENT_FILESPEC.