Status Codes Discontinued
The following status codes are discontinued in TIBCO ActiveMatrix Adapter for SAP.
Status Code | Role | Category | Resolution |
---|---|---|---|
AEADR3-600061
RFC/BAPI: %1: Import/Export parameters referencing String data type are ignored |
Warn | Configuration | The schema for the RFC/BAPI including import or export referencing String data types can be downloaded. But any references to String data types are ignored at runtime.
If parameters referring to String data types are required, create a custom module and change any references of String data type to fixed character types. |
AER3-000002
Invalid value for attribute %1 for operation %2 |
Error | Adapter | Verify if you are using the correct class descriptions and value specified is valid and no mandatory values are omitted. |
AER3-000003
Function call is transactional but no provided |
Error | Adapter | When you set transactional in closure, you must also supply a value for. |
AER3-000005
Could not find interface description element |
Error | Configuration | This problem might also occur if the configuration file is edited manually and is invalidated in the process. After making any changes to the file make sure that the XML file is well formed. The SML file can be validated by opening it in an XML enabled browser. |
AER3-000006
%1 not specified for %2 |
Error | Configuration | This problem might also occur if the configuration file is edited manually and is invalidated in the process. After making any changes to the file make sure that the XML file is well formed. The file can be validated by opening it in an XML enabled browser. |
AER3-000008
file is not specified |
Error | Configuration | Specify the file name, attribute “tidFileName” in the adapter instance level Adapter Services tab. |
AER3-000009
Timer %1 does not exist |
Error | Configuration | Provide a correct reference to the TIB Adapter SDK timer in the server connection section of the connection manager. |
AER3-0000010
The interface %1 does not specify attribute 'classRef' |
Error | Configuration | Provide a correct reference to the TIBCO Adapter SDK timer in the server connection section of the connection manager. |
AER3-0000011
Invalid producer %1 |
Error | Configuration | Provide a correct reference to an TIBCO Adapter SDK producer (publisher). |
AER3-0000013
No RpcClient specified for operation %1 |
Error | Configuration | Provide a valid reference to an TIB Adapter SDK RPC Client through "mbRpcClientRef" element in Deployment Descriptions of IDocs. |
AER3-0000014
Interface %1 does not contain deployment description for IDocs... continuing... |
Warn | Configuration | Provide a valid reference to an MBOperation. Also add a reference to the XML document that contains the descriptions for this operation. This is done using the model document tag at the beginning of the configuration file in the document section.
The default class descriptions for MB operations, i.e. UserExitSchema.xml, can also be extended with class description for additional operations. |
AER3-000015
Invalid producer %1; using default producer %2 |
Info | Configuration | Indicates normal adapter operation. No action necessary. |
AER3-000016
Invalid consumer component %1 |
Error | Configuration | Modify your configuration by defining a consumer name as suggested by the error description. |
AER3-000017
No components defined in the configuration document |
Error | Configuration | Modify your configuration so that it has at least one component under the 'components' section. |
AER3-000018
No connection manager defined in the configuration document |
Error | Configuration | Modify your configuration so that it has a 'connectionManager' under the 'connectionManagers' section. |
AER3-000019
Invalid rpcServer %1 specified for interface %2 |
Error | Configuration | Modify your configuration so that it has a 'connectionManager' under the 'connectionManagers' section. |
AER3-000020
The Subscriber Description does not specify consumer reference, skipping... |
Error | Configuration | Add consumerRef attribute in the configuration. |
AER3-000021
Consumer %1 for deployment description %2 does not exist |
Error | Configuration | ConsumerRef must point to a valid subscriber. |
AER3-000022
No instance defined for %1; control fields will not be replaced |
Warn | Configuration | You must have an instance defined under class instances. |
AER3-000023
Invalid reference for attribute consumerRef |
Warn | Configuration | ConsumerRef must point to a valid subscriber. |
AER3-000024
Error while reading directory=%1, filename=%2; %3 |
Error | System | Determine the cause from the error description. |
AER3-000025
directory=%1, filename=%2; No matching files found |
Warn | System | There were no matching files. Check your filenames. |
AER3-000026
Could not open %1 for reading |
Error | System | The specific file could not be opened. Check permissions. |
AER3-000027
%1 is unreadable |
Error | System | Check whether the file can be opened using a text editor. |
AER3-000028
%1 is empty |
Warn | System | File is empty. |
AER3-000029
%1 does not contain newline. Perhaps not a text file |
Error | System | The file is not a text file, because it does not contain a new line. |
AER3-000030
IDoc from file %1 sent in %2 mode |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000032
Cannot get control record for IDoc |
Warn | Adapter | The IDoc does not have a control record. If it’s not intentional, add a control record. |
AER3-000034
False call to %1 |
Warn | Adapter | See the error description for more details. |
AER3-000035
Could not generate GUID |
Warn | Adapter | Even though a warning, this message is often indicative of a memory-low situation that could severely affect the adapter performance. |
AER3-000036
No connection for %1 |
Error | Adapter | The named component does not have a valid connection Manager. Refer also to the description for 'R3-CORE-CFG-1014'. |
AER3-000037
Could not create Manager |
Error | Adapter | If the problem persists, repeat with remote Management. |
AER3-000038
Could not find default client connection |
Error | Configuration | Modify your configuration so that the login parameters that you specify for 'defaultClient' are valid and that the Adapter can establish a valid connection to the SAP System. |
AER3-000039
No proxy defined to process request for RFC function %1 |
Error | Adapter | The Adapter could not create a proxy for the named RFC function. Look at the earlier error messages in the log file(s) for possible causes. |
AER3-000041
Unable to create RFC server function %1 |
Error | Adapter | Look at earlier error messages in the log file(s) for possible causes. |
AER3-000042
Unable to create request proxy for %1 |
Error | Adapter | Look at earlier error messages in the log file(s) for possible causes. |
AER3-000043
Unable to create RFC client for %1 |
Error | Adapter | Look at earlier error messages in the log file(s) for possible causes. |
AER3-000047
%1 is not a valid structure or table |
Error | Adapter | If the name represents a valid SAP structure (or table), ensure that the repository contains the class definition for this structure (or table). If you are sending data from your custom program(s) to the SAP Adapter, make sure that you're constructing the data correctly and that you're using valid classes. |
AER3-000048
Unpacking error: Invalid class type for structure %1 |
Error | Adapter | Data inappropriate for the named structure. See also R3-CORE-LIB-6014. |
AER3-000049
Unpacking error: Invalid class type for table %1 |
Error | Adapter | Data inappropriate for the named table. See also R3-CORE-LIB-6014. |
AER3-000050
UnpacUnpacking error: Invalid class type for structure %1 king error: Row of table %1 is not a structure |
Error | Adapter | Data inappropriate for the named table. See also R3-CORE-LIB-6014. |
AER3-000051
User-defined operation called successfully |
Info | Adapter | The Adapter invoked the user-defined operation successfully. |
AER3-000052
Invalid or no data received from user-defined operation |
Error | Adapter | Check the program that implements the user-defined operation and make sure that it returns data. |
AER3-000053
User-defined operation invocation exception; name: %1, data: %2 |
Error | Adapter | Ensure that your operation executes without any exception and that it returns valid data to the Adapter. |
AER3-000054
User-defined operation invocation timeout |
Error | Adapter | Ensure that the Rpc Server that implements your operation is running and that it is reachable from the Adapter. |
AER3-000055
User-defined operation invocation: bad reply received |
Error | Adapter | Ensure that your operation returns valid data to the Adapter. |
AER3-000056
User-defined operation invocation exception; name: %1 |
Error | Adapter | Ensure that your operation executes without any exception and that it returns valid data to the Adapter. |
AER3-000057
The request sent to user-defined operation contains invalid data |
Error | Adapter | If you're constructing the data to be sent to the user-defined operation, ensure that it's being constructed correctly. |
AER3-000058
Invalid operation name for IDoc %1 |
Error | Adapter | The Adapter found that the IDoc data is arriving from a function other than 'IDoc_INBOUND_ASYNCHRONOUS' or 'INBOUND_IDoc_PROCESS'. |
AER3-000059
Cannot create IDoc parser instance |
Error | Adapter | The error indicates that it could not create a parser, either because of a memory-low problem or because of an earlier error during Adapter initialization. |
AER3-000060
Invalid RFC function %1 |
Error | Adapter | Look at earlier error messages in the log file(s) for possible causes. |
AER3-000062
Unable to create reply listener for operation %1 |
Error | Adapter | See earlier messages in the log file(s) for possible causes. |
AER3-000063
RFC invocation timeout for function %1; description: %2 |
Error | Adapter | The named RFC function invocation timed out. See error description for more details. |
AER3-000064
RFC invocation bad reply for function %1; description: %2 |
Error | Adapter | The named RFC function returned a bad reply. See error description for more details. |
AER3-000065
RFC invocation remote exception; name: %1, description: %2 |
Error | Adapter | The named RFC function caused a remote exception. See error description for more details. |
AER3-000066
Cannot create IDoc parser instance for subscriber %1 |
Error | Adapter | The error indicates that it could not create a parser, either because of a memory-low problem or because of an earlier error during Adapter initialization. |
AER3-000069
Cannot implode IDoc %1 |
Error | Adapter | Either the adapter encountered a low-memory condition or the received data is incorrect. If it is your application that is sending the offending data to the adapter subscriber, make sure that your data is valid. |
AER3-000070
Cannot get RFC client function %1 |
Error | Adapter | Make sure that SAP login parameters are correct and that the subscriber adapter can reach the SAP system. Also check earlier error messages in the log file(s) for possible causes. |
AER3-000071
Cannot get marshaller for RFC client function %1 |
Error | Adapter | The subscriber adapter could not get marshaller to convert between adapter data and SAP data, perhaps because of a low-memory problem or because of an error encountered earlier during initialization. Check the earlier error messages in the log file(s) for possible causes. |
AER3-000073
Cannot get RFC connection for client %1 |
Error | Application | See R3-CORE-LIB-60. |
AER3-000074
Operation %1 timed out |
Error | Adapter | Make sure that the RPC Server that corresponds to the named operation is executing and is accessible from the Adapter. |
AER3-000075
Operation %1 returned a bad reply %2 |
Warn | Adapter | The named operation returned a bad reply. Look at the error message description for more details. |
AER3-000076
Initialization exception type: %1, operation: %2, description: %3 |
Error | Adapter | The named operation returned the named exception. Look at the error message description for more details. |
AER3-000079
Unpacking error |
Error | Adapter | The Adapter encountered an error either because of low-memory condition or because of an error earlier during the initialization. Check the earlier error messages in the log file(s) for possible causes. |
AER3-000080
Could not create TIBCO RV advisory handlers; exception type: %1, description: %2 |
Warn | Adapter | The Adapter could not create the license expiry advisories. Look at the error description for more details. |
AER3-000081
Could not create TIBCO Hawk implants; exception type: %1, description: %2 |
Warn | Adapter | The adapter could not create TIBCO Hawk implants. Look at the error description for more details. |
AER3-000083
Unable to create operation request for function: %1, class: %2, rpcClient: %3 |
Warn | Adapter | The Adapter could not create Operation request for the named function. Look at the error description for more details. |
AER3-000087
IDoc Sent to SAP System |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000088
IDoc sent as a Business Document |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000089
IDoc received as a Business Document |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000092
The subscriber for this IDoc message could not be determined |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000096
IDoc Message sequence number %1 could not be confirmed to %2, Use pre-registration of subscribers |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000097
IDoc Message could not be confirmed, validation must be turned off, if 10X Publishers used |
Info | Configuration | Indicates normal adapter operation. No action necessary. |
AER3-000099
RFC Function invoked: %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000100
User-defined operation: operation not specified, assuming 'transform' |
Warn | Configuration | If the default transfer is not desired, name your operation explicitly. |
AER3-000101
User-defined operation reference: operationRpcClientRef not specified, operation will not be invoked |
Warn | Configuration | The operation requires an rpcClient, specific through operationRpcClientRef. Specify this client. |
AER3-000104
Setting up Imports and Exports for RFC function %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000105
RFC function has %1 imports, %2 exports |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000142
Subscriber: %1. The 10x Opaque message type is not supported |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000143
The received message was recovered |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000144
The IDoc message received in 10x format does not contain %1field |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000148
CIDocIterator: The IDoc container does not contain any IDocs |
Error | Adapter | Check the log file for any previous errors that may have led to this situation. |
AER3-000149
The IDoc %1 does not contain %2 |
Error | Adapter | The IDoc does not contain a data record section. Check the IDoc data |
AER3-000150
No control record instance for the %1 IDoc in the packet |
Error | Adapter | The named IDoc does not have a control record. Check the data. |
AER3-000151
No data record instance for the %1 IDoc in the packet |
Error | Adapter | The IDoc does not contain a data record section. Check the data. |
AER3-000152
%1 record of the data record instance does not contain mandatory attribute DOCNUM |
Error | Adapter | DOCNUM is mandatory attribute for data record. Check the data and modify it to include DOCNUM. |
AER3-000153
%1 row of the data record instance of the %2 IDoc instance of type %3 could not be obtained |
Error | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000154
The IDoc instance could not be written to file, the instance is invalid |
Error | Subscription | The instance could not be written because it was empty. Check the IDoc data. |
AER3-000155
The IDoc does not contain a data record |
Error | Adapter | The IDoc does not contain a data record section. Check the IDoc data. |
AER3-000157
Invocation for RFC function %1 still pending |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000158
Adapters initialization mode:%1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000159
Cannot find communication client for Manager, Management will be local |
Warn | Adapter | The configuration does not specify the rpcClient for Manager, hence the management will be local. |
AER3-000160
Connection: waiting for reply from server ... |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000161
No component for the RFC call; Exception=%1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000162
Active connection is null |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000163
Checking for connections |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000168
%1 connection could not be removed |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000170
Stop Adapter: Correct consumer reference could not be obtained from deployment description %1, skipping... |
Warn | Adapter | The configuration did not specify consumerRef. No action necessary. |
AER3-000171
Adapter is waiting for invocation response before shutdown can proceed... |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000174
Connection Manager %1 stopped |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000175
Component %1 stopped |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000176
Deactivating stop scheduler |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000179
Remote Exception: Exception Name: %1, Exception Data: %2 |
Error | Adapter | See the error description for details. |
AER3-000180
ADV_CLASS/ADV_SOURCE/ADV_NAME: %1, ADV_DESC : %2 %3 |
Warn | Adapter | See the error description for more details. |
AER3-000181
ADV_CLASS/ADV_SOURCE/ADV_NAME: %1, ADV_DESC : %2 %3 |
Error | Adapter | The adapter responds 'license expiry' warning from the daemon with this message. |
AER3-000182
ADV_CLASS : %1, ADV_SOURCE : %2, ADV_NAME : %3 |
Error | Adapter | The adapter responds 'registration collision' error from the daemon with this message. |
AER3-000183
RFC error; Group : %1, Key : %2, Message : %3 |
Error | Application | Look at the error description for details about the SAP Exception. Also check your connection parameters. |
AER3-000184
RFC connection invalid for %1 |
Error | Application | The adapter could not get a valid connection to the SAP system. Check your login parameters. Also make sure that the adapter can reach the SAP system. |
AER3-000185
CallReceive failed for operation %1; exception : %2, RFC error; Group/Key/Message: %3 |
Error | Application | Look at the error description for details about the SAP Exception. |
AER3-000189
RFC function initialization error for function %1; RFC Error; Group/Key/Message : %2 |
Error | Application | Look at the error description for details about the SAP Exception. |
AER3-000190
RFC remote function %1 implementation exception %2 |
Warn | Adapter | Look at the error description for details about the SAP Exception. |
AER3-000191
Indirect call error while sending IDoc; RFC Error; Group : %1, Key : %2, Message : %3 |
Error | Application | Look at the error description for details about the SAP Exception. |
AER3-000192
RFC error; Group : %1, Key : %2, Message : %3, Attempt to connect timed out |
Error | Application | See the error description for details. |
AER3-000193
Connection not available for client %1, retrying ... |
Error | Application | See the error description for details. |
AER3-000194
Invalid RFC client connection object for client %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000204
%1 is not a modeled class |
Error | Configuration | The named class is invalid, non-existent, or does not represent a modeled class. Check the repository to make sure that a valid class exists with that name. |
AER3-000205
No operations defined in class %1 |
Error | Configuration | Modify the class definition to include operations. |
AER3-000206
The operation %1 does not have any parameters |
Error | Configuration | Modify the class definition to include parameters. |
AER3-000208
Operation description not available for %1 |
Error | Configuration | The named operation is invalid or non-existent. Check the repository to make sure that an operation exists with the specified name. |
AER3-000209
No IDoc operations defined in class %1 |
Error | Configuration | The named class does not have IDoc operations defined. Check the repository to make sure that the class definition is correct. |
AER3-000210
Attribute %1 in class %2 is invalid |
Error | Configuration | Check the configuration. |
AER3-000211
Unsupported type %1 for attribute %2 in class %3 |
Error | Adapter | The named type is unsupported by SDK or SAP or both. |
AER3-000212
Unexpected %1 : %2; inform technical support |
Error | Adapter | Unexpected error. You cannot determine the cause from the description. Contact technical support: support@tibco.com. |
AER3-000213
Control field replacements specify an attribute %1 which does not exist in the control record |
Warn | Configuration | Control field replacements in classInstances specify an attribute that does not exist in control record. Check spelling. |
AER3-000214
Cannot access class registry |
Error | Adapter | You specified an attribute that does not exist in the control record. Either omit that attribute or replace it with an attribute that exists. |
AER3-000215
Subscriber %1 received a message that has invalid wire format |
Error | Adapter | There was an exception in the Adapter upon receive of this message. When you are using 10x style, follow the configuration requirements given in Creating Adapter Configurations on page 63. |
AER3-000261
Using ini file %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000262
No program ID defined in the ini file, using destination %1 as program ID |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000266
Initialized successfully |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000267
CREATED %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000268
EXECUTED %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000269
CONFIRMED %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000270
Invalid client function specified in removeClient call |
Error | Adapter | Because this message appears during shutdown, no action is necessary. |
AER3-000271
Invalid poolRef name %1 |
Error | Configuration | poolRef must point to a valid pool definition. |
AER3-000272
Pool reference not provided in Server Component |
Error | Configuration | Provide a value that corresponds to a valid definition. |
AER3-000274
Invalid default Connection for pool %1 |
Error | Adapter | Check the pool definitions to ensure that they are valid. |
AER3-000275
No default session defined |
Error | Configuration | The configuration must either specify a valid value for start up/default session or define at least one rvSession/rvCmSession. |
AER3-000276
Duplicate DEST parameter defined in %1 : %2 |
Error | Adapter | Remove duplicate definition. |
AER3-000277
Destination %1 not defined in %2 |
Error | Adapter | Define destination given in message. |
AER3-000278
Received message is written to file %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000279
Exception while initializing adapter; exception type : %1, description : %2 |
Error | Adapter | Refer to the description and take the required action. |
AER3-000280
Error: Could not send reply for function: %1 |
Error | Adapter | Refer to the accompanying error messages for additional details. |
AER3-000281
Error while invoking User-defined operation: %1 |
Error | Adapter | Refer to the accompanying error messages for additional details. |
AER3-000283
Exception during one way invocation of function: %1, Type: %2, Description: %3 |
Error | Adapter | Refer to the accompanying error messages for additional details. |
AER3-000284
Request written to file: %1 for operation: %2 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000285
Error code: %1, Message: %2 |
Error | Adapter | Refer to the description and take the required action. |
AER3-000286
'userExit' class does not exist or it does not contain operation %1, operation will not be invoked |
Info | Configuration | Indicates normal adapter operation. No action necessary. |
AER3-000287
There is no RpcClient named: %1, operation will not be invoked |
Info | Configuration | Indicates normal adapter operation. No action necessary. |
AER3-000288
Untransformed IDoc data sent |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000289
Performing asynchronous invocation for User-defined function: %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000290
No R/3 client configured for %1, using default-client %2 |
Warn | Configuration | There is no deployment-description configured for the RFC. If not intentional, ensure that the client is specified in the deployment-descriptions for the RFC. |
AER3-000291
Received request for logon to SAP R/3 System |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000292
Successfully logged-on to SAP R/3 System |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000293
Received request for logoff from SAP R/3 System |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000294
Successfully logged-off from SAP R/3 System |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000295
No session id exists in the logoff request |
Error | Adapter | The sessionID obtained on logging-on to SAP system through design-time-adapter should be passed in the RFCCLOSURE along with the logoff request to successfully logoff from SAP system |
AER3-000296
No logon session exists for the session ID |
Error | Adapter | The sessionID obtained on logging-on to SAP system through design-time-adapter should be passed in the RFCCLOSURE along with the logoff request to successfully logoff from SAP system. |
AER3-000300
Created discovery subscriber successfully using subject %1 |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000301
Attempting to create dynamic connection to SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000302
Attempting to close dynamic connection from SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000303
Retrieving list of function modules from SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000304
Retrieving schema for IDoc %1 FROM SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000305
Retrieving entries for table %1 FROM SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000306
Retrieving schema for structure/table %1 FROM SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000307
Received unknown operation %1 |
Info | M | TIBCO Designer sent an invalid request to the design-time adapter. If problem persists contact technical support: support@tibco.com |
AER3-000308
Metadata adapter operation failure:%1; operation name : %2 |
Info | M | Refer to the surrounding error messages for additional details. |
AER3-000309
Retrieving schema for RFC/BAPI %1 from SAP R/3 system |
Info | M | Indicates normal adapter operation. No action necessary. |
AER3-000400
Invalid connection detected. Message : % |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000401
%1 RFCServers registered with SAP R/3 system with program-id %2 on GatewayHost %3 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000402
No session id in request for operation %1 |
Error | Adapter | If the request is for an RFC that requires an explicit logon to SAP system, then the sessionID obtained on logging-on to SAP /3 system has to be passed in the RFCCLOSURE along with the RFC request. |
AER3-000403
Unable to obtain context for implementation of operation %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000405
Invalid session id passed in request for operation %1 |
Error | Adapter | The sessionID should be a valid string. |
AER3-000406
Invalid session id passed for operation %1 |
Error | Adapter | If the sessionID was obtained after logging-on to the SAP system, ensure that the sessionID passed in the RFCCLOSURE while invoking a request on the InboundRFC instance is the same as the one obtained. Instead, if the sessionID was obtained for a subsequent BAPI_TRANSACTION_COMMIT call, ensure that the same sessionID was passed with BAPI_TRANSACTION_COMMIT invocation. Also check if the session created for commit/rollback has already timed-out as specified by the 'commitExpiry' parameter. |
AER3-000407
Invalid call received, connection closed for thread |
Error | Adapter | The adapter received an invalid call from the SAP system that caused a connection to be closed. Ensure that the adapter connections to SAP system are alive. |
AER3-000408
Server thread unable to dispatch call, call skipped. message : %1 |
Error | Adapter | The adapter entered an invalid state because of an invalid call from the SAP system. See message description for more details. Ensure that the adapter connections to SAP system are alive. |
AER3-000409
Server thread unable to dispatch call, connection invalidated |
Error | Adapter | The adapter entered an invalid state because of an invalid call from the SAP system. See message description for more details. Ensure that the adapter connections with SAP system are alive. |
AER3-000410
Server thread exited, message : %1 |
Warn | Adapter | The adapter encountered an exception condition that caused the server thread to exit. Look at earlier messages in the log-file(s) for possible causes. No resolution necessary. |
AER3-000411
No poolRef specified for operation %1 |
Error | Configuration | The RFC does not have a 'poolRef' attribute in its deployment description. Ensure that a valid 'poolRef' is specified for the RFC. |
AER3-000413
The session for commit/rollback timed out for operation %1 |
Error | Adapter | Ensure that the BAPI_TRANSACTION_COMMIT call is triggered in the SAP system before the session for commit/rollback times out as specified by the 'commitExpiry' parameter. |
AER3-000414
No session timeout specified for commit/rollback for operation %1, defaulting to %2 seconds... |
Error | Configuration | The 'commitExpiry' parameter defaults to 60 seconds if it is not specified. If this value is insufficient, ensure that a higher value is specified for the parameter. |
AER3-000415
Session timeout for commit/rollback for operation %1 set to %2 seconds |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000417
Connection pending commit for operation %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000418
Invalid client specified : %1 |
Error | Adapter | Ensure that a valid client is specified for the RFC/IDoc in their respective deployment descriptions, if any. Else ensure that the 'defaultClient' attribute specified in client connectionpool is a valid client. |
AER3-000419
Created new thread for RFCServer |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000420
Server thread(s) stopped for Component %1 |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000421
No valid connection handle available for server for operation %1 |
Error | Adapter | The outbound adapter could not get a valid connection handle to the SAP system. Look at earlier messages in the log-file(s) for possible causes. |
AER3-000422
No client specified in deployment description for operation %1 |
Error | Configuration | Ensure that a client is configured for the operation. |
AER3-000423
No poolRef specified for operation %1 |
Error | Configuration | Ensure that a poolRef is specified for the operation. |
AER3-000424
No default client specified for operation %1 |
Error | Configuration | Ensure that a defaultClient is specified for the operation. |
AER3-000425
Invalid poolRef specified in deployment : %1 |
Error | Configuration | Ensure that a valid poolRef is specified in the deployment description for the RFC/IDoc. |
AER3-000426
Thread monitor started for %1 server thread(s) |
Info | Adapter | Indicates normal adapter operation. No action necessary. |
AER3-000427
No active connections available in configuration, exiting... |
Error | Adapter | This indicates that all the SAP systems the adapter is connected to, are down and none of the connections established by the adapter with the SAP system are active. Ensure that the SAP systems are up and running. |
AER3-000428
Interface %1 does not contain deployment description for RFCs... continuing... |
Warn | Configuration | The adapter could not find deployment descriptions for any RFC. If it is not intentional, ensure that the RFC configuration is correct. |
AER3-000429
No deployment description available for idoc %1...using default… |
Warn | Configuration | The adapter could not find deployment descriptions for the specified IDoc. If it is not intentional, ensure that the IDoc configuration is correct. |
AER3-000432
Unable to clone proxy for operation %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000433
Unable to clone RFC client for %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000434
Unable to clone function implementation for operation %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000435
Unable to create listener for call-operation |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000436
Unable to create reply listener for operation %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000437
Unable to clone subscriber implementation |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000438
Unable to generate transaction-id. message : %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000439
Unable to create implementation for thread |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000440
Unable to create server thread |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000442
Connection context lost. Operation %1 failed |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000443
Logon to SAP R/3 system failed. message : %1 |
Error | Adapter | Look at earlier error messages in the log-file(s) for possible causes. |
AER3-000444
Error writing to file for transaction %1 |
Error | Adapter | Ensure that the file has write permissions. |
AER3-000445
No active connections in connection-pool %1. All retry attempts exhausted. Connections for this pool deactivated. |
Error | Adapter | Ensure that the SAP system pointed to by the connection-pool %1 is up and running. |
AER3-000447
No active connections in connection-pool %1. All retry attempts exhausted. Exiting... |
Error | Adapter | This indicates that all the SAP systems the adapter is connected to, are down and none of the connections established by the adapter with the SAP system are active. Ensure that the SAP systems are up and running. |
AER3-000449
The Application Manager has been flagged to restart on re-establishing connection to R/3. |
Info | Adapter | None. |
AER3-000451
Adapter application will restart now |
Warn | Adapter | The adapter is recovering missed messages by performing an internal-restart. Ensure that the adapter has performed a restarted successfully by checking the adapter log files. |
AER3-000452
Adapter application %1 is restarting on host %2. |
Info | Adapter | None. |
AER3-000453
Invalid control-field replacement attribute %1 skipped. |
Warn | Configuration | A control-field name %1 not present in the IDoc's control record was specified for replacement. Ensure that the field name is one of those defined for the IDoc's control record. |
AER3-000454
Performing oneway invocation for User-defined function: %1 |
Info | Adapter | None. |
AER3-000455
No class description available for explode sequence %1 |
Error | Configuration | Check the repository under /tibco/public/adapter/SAPAdapter40/<sap version>/IDOCS/ for the class description for class %1. |
AER3-000456
No attribute description for explode sequence %1 |
Error | Configuration | Check the repository for attribute description for explode sequence %1. |
AER3-000457
Operation %1 requires external logon. The request does not contain sessionID in the closure data. |
Error | Adapter | Supply the session-id parameter in the RFCCLOSURE data of the incoming request. |
AER3-9100012
Startup Error. Unable to create a Custom Hawk Micro Agent Named %1 used for %2 |
Error | Startup | Verify your repository settings for validity of the stop-subscriber session parameters. |
AER3-910003
Startup Error. The command-line parameter(s): configurl, repourl have not been specified |
Error | Startup | Specify the command-line parameters configURL and repoURL. |
AER3-910006
Startup Error. SDK Exception %1 occurred while creating a shutdown listener with parameters %2. The Repository URL is %3 and the Configuration URL is %4 |
Error | Startup | Verify your repository settings for validity of configuration for the shut down listener. |
AER3-910007
Startup Error. Unable to create a connection with the target application %1 using connection parameters %2 and the target application error is %3 |
Error | Startup | Verify your repository settings for validity of connection parameters. |
AER3-9300014
Publication error. Publication service %1 with publication subject %2 received error while sending event over the wire. Error: %3 |
Error | Publication | Check repository settings for valid configuration of the publish endpoint for this service. |
AER3-9200015
Subscription error. Subscription Service %1 listening on subject %2 failed due to target application invocation error %3. Target application is %4 |
Error | Subscription | Verify the structure of the incoming message. Check in the SAP system for more detailed information on the cause of the error. |
AER3-930003
Publication error. Publication service %1 with publishing subject as %2 received event from target application %3. It failed while converting event to MInstance as it could not get the class description for %4. Repository URL is %5 and the Configuration URL is %6' |
Error | Publication | Verify the configuration of the Publication Service service and check that the schema/class definitions are present in the repository. See Adapter Service Reference for details. |
AER3-930006
Publication error. Publication service %1 with publishing subject %2 received the event from target application %3. It failed while converting event to MInstance attribute %4 of class %5 is missing. RepositoryURL is %6 and the ConfigurationURL is %' |
Error | Publication | Verify the configuration of the Publication Service service and check that the schema definitions are present in the repository. See Adapter Service Reference for details. |
AER3-930015
Property: adr3.preserveFieldBlanks must be set to ON when using message encoding UTF-8 for publisher: %1 in mode: %2 |
Error | Request-Response | Verify that the property adr3.preserveFieldBlanks is set to ON. |
AER3-940001
Request Response error. Request Response service %1 listening on %2 received unexpected null data in incoming request. Expects event %3. The Repository URL is %4 and the Configuration URL is %5 |
Error | Request-Response | Check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above Request-Response Service service. See Adapter Service Reference for details. |
AER3-940005
Request Response error. Request Response service %1 failed to deserialize the received Request to MInstance: Received event on subject %2, event = %3, SDK exception = %4. The Repository URL is %5 and the Configuration URL is %6 |
Error | Request-Response | Check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above Request-Response Service service. See Adapter Service Reference for details. |
AER3-940008
Request Response error. Connection error in invocation of Request Response service %1 listening on subject %2. Connection Parameters are %3 |
Error | Request-Response | Check if the end application is up and running. Also verify the connection parameters are specified in the repository. |
AER3-9500010
Request-Response Invocation error. Request-Response Invocation Service %1 with subject %2 received null reply while requesting event over the wire |
Error | Request-Response Invocation | Check the target application, if it is running or not. Check the configuration of the Request-Response Invocation Service service. |
AER3-9500011
Request-Response Invocation error. Request-Response Invocation Service %1 with subject %2 received timeout error while requesting event over the wire |
Error | Request-Response Invocation | Check repository settings for valid configuration of the Request-Response Invocation endpoint for this service. See Adapter Service Reference for details. |
AER3-9500012
Request-Response Invocation error. Request-Response Invocation Service %1 with subject %2 received error while processing reply message. Error %3 |
Error | Request-Response Invocation | Check repository settings for valid configuration of the Request-Response Invocation endpoint for this service. See Adapter Service Reference for details. |