General Status Messages
The following table lists status codes, detailed explanation of each error, where applicable, and ways to solve different errors.
Status Code and Status Message | Role | Category | Resolution |
---|---|---|---|
AEFA-000002
Out of memory |
errorRole | System | Check the system to determine why it ran out of memory. |
AEFA-000003
Missing class definition for <class name> in the configuration |
errorRole | Configuration | Review the documentation. If that does not help, contact TIBCO support. |
AEFA-000004
Missing attribute for <attribute name> in the configuration |
errorRole | Configuration | Review the documentation. If that does not help, contact TIBCO support. |
AEFA-000005
Attribute <attribute name> in the configuration has the wrong value <attribute name> |
errorRole | Configuration | Review the documentation. If that does not help, contact TIBCO support. |
AEFA-000007
Couldn’t open file <filename> |
errorRole | System | Check the file system to ensure that all of the files exist and can be opened. |
AEFA-000008
Couldn’t close file <filename> |
errorRole | System | Check the file system to determine why the file could not be closed. |
AEFA-000009
Couldn’t read file <filename> |
errorRole | System | Check the file and the file system to determine why the error occurred. |
AEFA-000011
Pre Processing Script File directory <directory name> couldn’t be found |
errorRole | Configuration | Make sure that the directory exists. If it does, correct the configuration to point to the correct directory for the Pre Processing Script File. |
AEFA-000012
Pre Processing Script File <filename> couldn’t be found |
errorRole | Configuration | Make sure that the file exists. If it does, correct the configuration to point to the correct file and directory names for the Pre Processing Script. |
AEFA-000013
Post-processing script file <filename> couldn’t be found |
errorRole | Configuration | Correct the configuration to point to the correct file and directory names for the Post Processing Script of the Publication Service. |
AEFA-000014
No access to Input Directory <directory name> |
errorRole | Configuration | Create the Input Directory or give access to it. |
AEFA-000015
No access to Working Directory <directory name> |
errorRole | Configuration | Create the Working Directory or give access to it. |
AEFA-000016
No access to Completion Directory <directory name> |
errorRole | Configuration | Create the Completion Directory or give access to it. |
AEFA-000017
Working file <filename> already exists |
errorRole | Adapter | Remove the duplicate file from the Working Directory. |
AEFA-000018
Could not add file <filename> to Working Directory <directory name>. Reasons: 1. The Working Directory or Input Directory could be in read only mode. 2. The file specified does not exist anymore. 3. The file specified is locked by some other applications |
errorRole | System | 1. If none of the files are processed, check the file system. Make sure the Working Directory and Input Directory exist and are in write mode. 2. If the file does not exist anymore then verify if you have other applications processing the input directory the adapter is using. 3. If the file is locked by some other application, the file will be processed in the next iteration. In such cases consider using trigger files. |
AEFA-000019
Cannot remove file <filename> from Working Directory <directory name> |
warnRole | System | Check the file system to determine why the error occurred. |
AEFA-000020
Cannot add TimeStamp to file <filename> in directory <directory name> |
warnRole | System | Check the file system to determine why the error occurred. |
AEFA-000021
Cannot move file <filename> to Completion Directory <directory name> |
warnRole | System | Check the file system to determine why the error occurred. |
AEFA-000022
Cannot remove Trigger File <filename> from Input Directory <directory name> |
errorRole | System | Check the Trigger File rights and the file system state to determine why the error occurred. |
AEFA-000023
Cannot open data file <filename> in Working Directory <directory name> |
errorRole | System | Check the working data file rights and the file system state to determine why the error occurred. |
AEFA-000024
Cannot find input data file <filename> matching Trigger File <filename> in Input Directory <directory name> |
errorRole | Adapter | Check the existence of the input data file and the input data file rights. |
AEFA-000025
Cannot open input data file <filename> on CheckPoint Restart |
errorRole | Adapter | Check the existence of the input data file, the input data file rights, and the content of the CheckPoint Restart file. |
AEFA-000026
User exit failed for Publication Service <service name> Input file = <filename>; Message = <data message> |
errorRole | Adapter | Check the User exit server to determine why the error occurred. |
AEFA-000027
User exit timed out for Publication Service <service name> |
errorRole | Adapter | Check that the User exit server is running. |
AEFA-000028
User exit failed for Subscription Service <service name> |
errorRole | Adapter | Check the User exit server to determine why the error occurred. |
AEFA-000029
User exit timed out for Subscription Service <service name> |
errorRole | Adapter | Check that the User exit server is running. |
AEFA-000030
Deserialisation failed for Subscription Service <service name> |
errorRole | Configuration | Check if the publisher is sending a MInstance. |
AEFA-000033
No formatting defined for class <class name> |
errorRole | Metadata | Configure the class in your Subscription Service or change its subject address. |
AEFA-000034
Received message couldn’t be written to a file |
errorRole | System | Check the file system to determine why the error occurred. |
AEFA-000035
No access to Working Directory <directory name> |
errorRole | Configuration | Create the Working Directory or give access to it. |
AEFA-000036
No access to Completion Directory <directory name> |
errorRole | Configuration | Create the Completion Directory or give access to it. |
AEFA-000037
No access to Error Directory <directory name> |
errorRole | Configuration | Create the Error Directory or give access to it. |
AEFA-000038
Cannot write file <filename> in Working Directory <directory name> |
errorRole | System | Check the file system state to determine why the error occurred. |
AEFA-000039
Cannot create file <filename> in Working Directory <directory name> |
errorRole | System | Check the file system state to determine why the error occurred. |
AEFA-000040
Cannot move file <filename> to Output Directory <directory name> |
errorRole | System | Check the file system state to determine why the error occurred. |
AEFA-000041
Cannot move file <filename> to Error Directory <directory name> |
errorRole | System | Check the file system state to determine why the error occurred. |
AEFA-000042
Cannot add TimeStamp to file <filename> in directory <directory name> |
errorRole | System | Check the file system state to determine why the error occurred. |
AEFA-000043
Post Processing Script file directory <directory name> couldn’t be found |
errorRole | Configuration | Check that the directory for the Post Processing Script File of Subscription Service exists and is readable. |
AEFA-000044
Post Processing Script file <filename> couldn’t be found |
errorRole | Configuration | Check that Subscription Service’s Post Processing Script File exists and is readable. |
AEFA-000045
Pre Processing Script <command string> returned error code <status string> |
warnRole | System | Check the Pre Processing script. |
AEFA-000046
Post Processing script <command string> returned error code <status string> |
warnRole | System | Check Publication Service’s Post Processing Script. |
AEFA-000047
<class name> will not be published since no Publication Service could be found |
warnRole | Configuration | Assign a Read Schema to the File Record. |
AEFA-000048
<input record> couldn’t be parsed |
warnRole | Adapter | Either modify an existing File Record to match this input line or create a new one. Make sure that the File Record is linked to a Read Schema. |
AEFA-000049
File <filename> has been parsed, <number of error records> lines couldn’t be interpreted |
warnRole | Adapter | Check if the input line is valid. If it is, then modify the File Record to correctly interpret it. |
AEFA-000051
Subscription Service <service name> received an unexpected message. Type <event type>. Data <event data>. |
warnRole | TibRvComm | Check the format of data sent by other applications on the subject that this Subscription Service is listening on. |
AEFA-000052
Attribute <attribute name> of class <class name> is of an unsupported type |
warnRole | Metadata | Check for any discrepancy between the incoming class and the Write Schema. |
AEFA-000053
Attribute <attribute name> of class <class name> is of an unsupported type |
warnRole | Metadata | Change the input class to make sure that it only includes supported types. |
AEFA-000054
File <filename> already exists in Working Directory <directory name> |
warnRole | Adapter | Remove the file from the Input Directory. Check why the file was still there so the problem does not repeat. |
AEFA-000055
File <filename> has been created in Output Directory <directory name> due to an input message time out |
warnRole | Adapter | If Subscription Service was not supposed to have timed out then you have to check your publisher to find out why the publications were delayed. |
AEFA-000056
Post Processing script <command string> returned error code <status string> |
warnRole | System | Check the Post Processing Script File to make sure that it is valid and correctly returned an error. |
AEFA-000057
<number of messages> messages have been published from file <filename> while <number of messages> have been written |
warnRole | Adapter | Check the content of your input and output data, check your logs for unsent data, and check if only one publisher is sending data. |
AEFA-000058
TIBCO ActiveMatrix Adapter for Files successfully initialized |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000059
Scanning Input Directory <directory name> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000060
Processing input file <filename> in Input Directory <directory name> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000061
Pre Processing script <command string> succeeded |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000062
Execute Post Processing script <command string> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000063
Publication of file <filename> is finished. |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000064
File <filename> has been processed, all lines were interpreted |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000065
Message containing class <class name> published on subject <subject name> (message is from file <filename>) |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000067
Message containing class <class name> received on subject <subject name> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000068
Message containing class <class name> written to working file <filename in Working Directory <directory name> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000069
<number of messages> messages have been published and received from file <filename> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000070
File <filename> is moved to the Output Directory <directory name> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000071
Post Processing Script <command string> succeeded |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000072
Multiple publisher mode used |
warnRole | Configuration | Contact TIBCO support if you experience any problem due to migration. |
AEFA-000073
Subscription Service <service name> received an empty MBusinessDocument in which the DataSection attribute was not set. |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000074
The line "<input record>" contains an invalid field |
errorRole | Adapter | Correct the invalid field. |
AEFA-000075
Could not create simple datetime class. Received error code <error code> |
errorRole | Adapter | Unsupported locale is the main cause for this error. |
AEFA-000076
Failed to parse the datetime string <datetime string> for the pattern specified <datetime pattern>. Received error code <error code> |
errorRole | Adapter | Invalid pattern or locale mismatch is the main cause for this error. |
AEFA-000077
Failed to format the datetime value to the specified pattern <datetime pattern>. Received error code <error code> |
errorRole | Adapter | Invalid pattern or locale mismatch is the main cause for this error. |
AEFA-000078
Failed to set attribute <attribute name> for the class <class name> Received error code <error description> |
warnRole | Adapter | Missing attribute in the class, wrong value or wrong data type is the main cause for this error. The other one being filtering of the attributes of the schema. |
AEFA-000079
File <filename> has been parsed. Total: <number of total records> lines, Error: <number of error records> lines |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000080
Processing file <filename>... |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000081
Pre Processing Script <command string> returned message <status string> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000082
Post Processing Script <command string> returned message <status string> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000083
Post Processing Script <command string> returned message <status string> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000084
Skip processing file <filename> at the request of the preprocessing script. |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000094
ECM is flex, and times to retry is over. The following subscribers have not responded and will be de-activated. |
warnRole | Adapter | |
AEFA-000095
Registered Subscriber name = <name string> |
warnRole | Adapter | |
AEFA-000099
Expected sequence does not match incoming data |
warnRole | Adapter | |
AEFA-000100
Checksum mismatch with the published file |
warnRole | Adapter | |
AEFA-000102
IO error detected |
warnRole | Adapter | |
AEFA-000106
Publisher is switching to ECM |
warnRole | Adapter | |
AEFA-000107
The admin confirmation timer is activated. |
warnRole | Adapter | |
AEFA-000115
The admin confirmation timer is activated. |
warnRole | Adapter | |
AEFA-000116
File <filename> is moved to the Error Directory <directory name> |
infoRole | Adapter | Indicates normal adapter information. No action necessary. |
AEFA-000117
Cannot process messages due to version mismatch. Product version = <version number>. Received message version = <version number> |
errorRole | Adapter | |
AEFA-000118
No access to Error Directory <directory name> |
errorRole | Configuration | Create the Error Directory or give access to it. |
AEFA-000119
File transfer failed for the subscriber <name string> because <error description>. Updated subscriber specific error log file <filename> |
errorRole | Configuration | |
AEFA-000120
Unable to open the subscriber specific error log file <filename> |
errorRole | Configuration | |
AEFA-000125
Cannot reset input directory to <directory name>. The directory does not exist or cannot be accessed |
errorRole | Configuration | Create the Input Directory or give access to it. |
AEFA-000126
Input directory is successfully changed to <directory name> |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000127
filename to process is reset to <filename> |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000128
File prefix to process is reset to <file prefix> |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000129
File extension to process is reset to <file extension> |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000132
Subscriber is started Simple File Transfer mode |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000133
Publisher is started Simple File Transfer mode |
infoRole | Configuration | Indicates normal adapter information. No action necessary. |
AEFA-000134
The progress file <filename> is corrupt |
errorRole | Configuration | Remove the progress file and restart the adapter. |
AEFA-000135
Received advisory message. Role: <role name>, Subject: <subject name>, Message: <message string> |
errorRole | Adapter | Check the advisory message for cause. |
AEFA-000136
Cannot add sequence number to file <filename> in directory <directory name> |
errorRole | System | Check the file system state to determine why the error occurred. |
AEFA-000137
Polling subscriber endpoint is not defined |
errorRole | Adapter | The file palette generates the polling subscriber endpoint. Name of the endpoint is FAPollingSubscriberServiceName. |
AEFA-000138
Subscriber <subscription service name> is experiencing IO Error. The publisher will deactivate the subscriber for the current file transfer and will reactivate the subscriber on a new file transfer |
errorRole | Adapter | If the IO error is temporary, the subscriber will automatically come back up; however, if it is permanent, you need to stop the subscriber and resolve the IO error, and then restart the subscriber. |
AEFA-000139
Progress filename is empty. Verify configuration and set a valid progress filename |
errorRole | Adapter | Set a valid progress filename using the designer and restart the publisher. |
AEFA-000140
IOError received when accessing progress file. Verify if progress filename is valid |
errorRole | Adapter | Set a valid progress filename using the designer and restart the publisher. Only LATIN_1 encoded filenames are valid. |
AEFA-000143
Cannot open the data file <filename> specified in the progress file on publisher restart |
errorRole | Adapter | Check the existence of the data file, the data file rights, and the content of the progress file. |
AEADFILES_910 006
Exit subscriber is not defined. The Repository URL is <repourl> and the Configuration URL is <configurl> |
warnRole | Startup | |
AEADFILES_920 001
Subscription error. <service name, subject name, repourl, configurl> received an invalid event. |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 002
Subscription error. <service name, subject name, repourl, configurl> failed to deserialize the received event. SDK exception thrown is <error description> |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 003
Subscription error. <service name, subject name, repourl, configurl> received inbound event with null data. |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 004
Subscription Service <subscription service name> received an MBusinessDocument <business document> in which the DataSection attribute was not set. |
infoRole | Subscription | Indicates normal adapter information. No action necessary. |
AEADFILES_920 005
Subscription error. <error message> could not deserialize the inbound event to MBusinessDocument <name of the business document> |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 007
Subscription error. Subscription Service <service name> listening on subject <subject name> could not get the class description of <class name>. <repoUrl and configUrl parameters>. |
errorRole | Subscription |
Check the repository configuration for this service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure, run and test Subscription Service. |
AEADFILES_920 009
Subscription error. <service name, subject name, repourl, configurl> received event with invalid value <attribute value> for property <attribute name> in class <class name>. |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 010
Subscription error. <service name, subject name, repourl, configurl> received event with missing attribute <attribute name> in class <class name>. |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 011
Subscription error. <service name, subject name, repourl, configurl> received event with missing association <association name> for class <class name>. |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 012
Subscription error. <service name, subject name, repourl, configurl> received MBusinessDocument <business document name> with NULL value for attribute <attribute name>. |
errorRole | Subscription | Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on the configuration of Subscription Service. |
AEADFILES_920 015
Subscription error. Subscription Service <service name> listening on subject <subject name> failed due to target application invocation error <error description>. Target application is FILES. The target application specific commands and parameters are <command name> |
errorRole | Subscription | Make sure that the directory or file exists and the permission is set properly. |
AEADFILES_920 020
Subscription error. <service name, subject name, repourl, configurl> received an event from the wire but encountered error <error description> in pre-processing user exit invocation. The User exit is <userexit client name>. The event details are <class name>. |
errorRole | Subscription | Make sure that the parameters passed to the UserExit are valid and the User Exit can be invoked by the adapter. |
AEADFILES_930 002
Publication error. Publication Service <service name> with publication subject <subject name> encountered error <error description>. |
errorRole | Publication | Make sure that the directory or file exists and the permission is set correctly. |
AEADFILES_930 003
Publication error. Publication Service <service name> with publishing subject as <subject name> received event from target application FILES. It failed while converting event to MInstance as it could not get the class description for <class name>. <repourl, configurl>. |
errorRole | Publication | Verify the configuration of Publication Service and check that the schema/class definitions are present in the repository. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure a Publication Service. |
AEADFILES_930 004
Publication error. <service name, subject name, repourl, configurl> received event from target application FILES. It failed while converting event to MInstance as it could not find property <attribute name> in class <class name>. |
errorRole | Publication | Verify the configuration of Publication Service and check that the schema definitions are present in the repository. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure a Publication Service. |
AEADFILES_930 005
Publication error. <service name, subject name, repourl, configurl> received event from target application FILES. It failed while converting event to MInstance as property <attribute name> of class <class name> has invalid value <attribute value>. |
errorRole | Publication | Verify the configuration of Publication Service and check that the schema definitions are present in the repository. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure a Publication Service. |
AEADFILES_930 006
Publication error. <service name, subject name, repourl, configurl> It failed while converting event to MInstance. Attribute <attribute name> of class <class name> is missing. |
errorRole | Publication | Verify the configuration of Publication Service and check that the schema definitions are present in the repository. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure a Publication Service. |
AEADFILES_930 007
Publication error. <service name, subject name, repourl, configurl> received event from target application but could not create the business document <business document name>. The target application details are <class name>. |
errorRole | Publication | Verify the configuration of Publication Service and check that the schema definitions for the MBusinessDocument maps properly to the event received from the target application. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure a Publication Service. |
AEADFILES_930 008
Publication error. <service name, subject name, repourl, configurl> received SDK Exception <error description> while converting the event received from target application to BusinessDocument. The exception occurred while setting the attribute <attribute name>. The target application details are <class name>. |
errorRole | Publication | Verify the configuration of Publication Service and check that the schema definitions for the MBusinessDocument maps properly to the event received from the target application. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on how to configure a Publication Service. |
AEADFILES_930 009
Publication error. <service name, subject name, repourl, configurl> received an event from the target application but encountered error <error description> in pre-processing user exit invocation. The User exit is <userexit client name>. The target application details are <class name>. |
errorRole | Publication | Make sure that the parameters passed to the UserExit are valid and the User Exit can be invoked by the adapter. |
AEADFILES_930 014
Publication error. <service name, subject name, repourl, configurl> received error while sending event over the wire. The Publish endpoint details are <error description> |
errorRole | Publication | Check the repository settings for a valid configuration of the publish endpoint for this service. See TIBCO ActiveMatrix Adapter for Files for Unix/Win (TIBCO Business Studio) User’s Guide on setting up a Publication Service and a publish endpoint. |
AEADFILES_930 015
Publication error. <service name, subject name, repourl, configurl> Field count or record length does not match the schema. |
errorRole | Publication | Correct the record according to the schema. |
AEADFILES_930 016
Publication error. <service name, subject name, repourl, configurl> Publication Service cannot create RegEx matcher for the configured pattern. |
errorRole | Publication | Check the configured pattern for validity. |
AEADFILES_930 017
Publication Service notification. |
infoRole | Publication | Indicates normal adapter information. No action necessary. |
AEADFILES_980 001
<function name> Running out of memory when trying to create a new object. Shutting down... |
errorRole | System | Check the system memory usage. |
AEADFILES_990 002
Shutdown error. SDK cleanup exception = <error description> |
errorRole | Shutdown | Check the system resource. |
AEADFILES_990 003
Shutdown error. Failed to cleanup Hawk microagent. SDK exception = <error description> |
errorRole | Shutdown | Check the system resource. |