BusinessWorks

TIBCO Business Works – Commandline Deployment

Trace Message Fields

Each trace message includes the following fields:

Table 14 Tracing Fields
Field Name Description
Timestamp Timestamp of occurrence. For example, 2010 Feb 22 20:14:51:718 GMT -8.
AdapterIdentifier Name of the adapter that wrote the trace message. This is a combination of the adapter acronym and adapter configuration name. For example, the application identifier, ADB.publisher1 identifies a TIBCO ActiveMatrix Adapter for Database service named publisher1.
Role A role can be:

Info. Indicates normal adapter operation. No action is necessary. A tracing message tagged with Info indicates that a significant processing step was reached and has been logged for tracking or auditing purposes. Only info messages preceding a tracking identifier are considered significant steps.
Warn. An abnormal condition was found. Processing will continue, butspecial attention from an administrator is recommended.
Error. An unrecoverable error occurred. Depending on the error severity,the adapter may continue with the next operation or may stop altogether.
Debug. A developer-defined tracing message. In normal operatingconditions, debug messages should not display.

When configuring the adapter you define what roles should or should not belogged. For example, you may decide not to log Info roles to increase performance.

Category One of the following:

Adapter. The adapter is processing an event.
Application. The adapter is interacting with the SAP system.
Configuration. The adapter is reading configuration information.
Database. The adapter is interacting with a database.
Schema. The adapter is retrieving metadata from the SAP system.
Palette. The adapter is interacting with the palette.
Publication. The publication service is reporting this trace message.
RequestResponseInvocation. The Request-Response invocation service is reporting this trace message.
RequestResponse. The Request-Response service is reporting this tracemessage.
Shutdown. The adapter is shutting down.
Startup. The adapter is starting.
Subscription. The subscription service is reporting this trace message.
Connection. This is an application connection related trace message.
System. This category is not linked to a specific event process. The tracemessage may be related to a Windows service related messages, memory allocation, file system error, and so on.
TibRvComm. The adapter is communicating with TIBCO Rendezvous.
XML. The adapter is parsing XML documents.
Status Code Unique code for the message and description. Status codes are identified by a unique number and description. If a trace message includes an error or warn role, the status code documentation includes a resolution. See Status Messages for details.
TrackingIdentifier A unique identifier that is “stamped” on each message by the originatingadapter. The tracking identifier remains in effect from a message’s beginning to its completion as it is exchanged by TIBCO applications. If the adapter is the termination point of the message, the tracking identifier is not displayed in the trace message.

You cannot modify the tracking identifier format or configure what information is displayed.

ApplicationInformation Application-specific information added to the tracking info to trace themessage back to its source. Set initially by the originating adapter and carried forward. It is augmented by each intermediate component.

Status Messages

The following table lists all the new error messages introduced in this release.

Status Code Role Category Resolution
AER3-000486 Invalid Destination %1 specified
Error Adapter Specify a valid destination.
AER3-910003 Startup Error. The command-line parameter(s): configurl, repourl have notbeen specified
Error Startup Specify the command-line parameters configURL and repoURL.
AER3-910005 Startup Error. SDK Error %1 received during initialization. The RepositoryURL is %2 and the Configuration URL is %3
Error Startup Verify your repository settings.
AER3-910006 Startup Error. SDK Exception %1 occurred while creating a shutdownlistener with parameters %2. The Repository URL is %3 and theConfiguration 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-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-940001 Request Response error. Request Response service %1 listening on %2received unexpected null data in incoming request. Expects event %3. The Repository URL is %4 and the Configuration URL is %5
Error RequestResponse 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. ReferChapter 2, Getting Started for details on configuration of Request-Response Service.
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 RequestResponse 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. ReferChapter 2, Getting Started for details on configuration of Request-Response Service.
AER3-940008 Request Response error. Connection error in invocation of RequestResponse service %1 listening on subject %2. Connection Parameters are %3
Error RequestResponse Check if the end application is up and running. Also verify the connection parameters are specified in the repository.
AER3-940009 Request Response error. Request Response service %1 listening on subject %2 failed due to target application invocation error %3. Target application is %4 and inbound event is %5
Error RequestResponse Check the validity of the incomingrequest-data to the Request-Response Service.
AER3-940010 Request Response error. Request Response service %1 listening on subject %2 failed to create reply. Error : %3
Error RequestResponse Verify the data received from the SAP system and make sure it matches the schema associated to the Request-Response Service.
AER3-940020 Server Timeout
Error Request-Response Check if the end application is up and running.
AER3-920001 Subscription error. Subscription service %1 listening on %2 received anunexpected event of type = %3, Expects event %4. The Repository URL is %5 and the Configuration URL is %6
Error 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. ReferChapter 2, Getting Started for details on configuration of Subscription Service.

If the error message is of the format Subscription error. Subscription service %1 listening on %2 received an unexpected event of type = %3, Expects event IDOC. The Repository URL is %5 and the Configuration URL is %6

and if using the unicode version of the adapter or the non-unicode version of the adapter with UTF-8 message encoding, the propertyadr3.preserveFieldBlanks is either set to OFF or commented out causing the subscriber to not successfully process the IDoc.

AER3-920002 Subscription error. Subscription service %1 failed to deserialize the eventreceived on subject %2 and SDK exception thrown is %3. The RepositoryURL is %4 and the Configuration URL is %5
Error 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. ReferChapter 2, Getting Started for details on configuration of Subscription Service.
AER3-920003 Subscription error. Subscription service %1 listening on subject %2 received inbound event with null data. The Repository URL is %3 and theConfiguration URL is %4
Error 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.
AER3-920007 Subscription error. Subscription service %1 listening on subject %2 couldnot get the class description of %3. The Repository URL is %4 and theConfiguration URL is %5
Error Subscription Check the repository configuration for this service. Refer Chapter 2, Getting Started for details on configuration of Subscription Service.
AER3-920008 Subscription error. Subscription service %1 listening on subject %2 couldnot find the mandatory property %3 in class %4. The Repository URL is %5 and the Configuration URL is %6
Error 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. ReferChapter 2, Getting Started for details on configuration of Subscription Service.
AER3-9200015 Subscription error. Subscription service %1 listening on subject %2 faileddue 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-950001 Request Response Invocation error. Request Response Invocation service %1 with subject as %2 received event from target application %3. It failed while converting event to request, as it could not get the class description for %4. Repository URL is %5 and the Configuration URL is %6
Error RequestResponseInvocation Verify the configuration of theRequest-Response Invocation Service and check that the schema/class definitions are present in the repository. ReferChapter 2, Getting Started for details on configuration of Request-Response Invocation Service.
AER3-950003 Request Response Invocation error. Request Response Invocation service %1 with subject as %2 received event from target application %3. It failed while converting event to request. Repository URL is %5 and the Configuration URL is %6
Error RequestResponseInvocation Verify the configuration of theRequest-Response Invocation Service and check that the schema/class definitions are present in the repository. ReferChapter 2, Getting Started for details on configuration of Request-Response Invocation Service.
AER3-950008 Request Response Invocation error. Request Response Invocation service %1 with subject %2 received error while requesting event over the wire. Error %3
Error RequestResponseInvocation Check repository settings for validconfiguration of the Request-Response Invocation endpoint for this service. Refer Chapter 2, Getting Started for details on setting up a Request-Response Invocation end point and a Request-Response Invocation Service.
AER3-950009 Request Response Invocation error. Request Response Invocation service %1 with subject %2 received error while requesting event over the wire. Error %3
Error RequestResponseInvocation Check repository settings for validconfiguration of the Request-Response Invocation endpoint for this service. Refer Chapter 2, Getting Started of for details on setting up a Request-Response Invocation end point and a Request-Response Invocation Service.
AER3-9500010 Request Response Invocation error. Request Response Invocation service %1 with subject %2 received null reply while requesting event over the wire
Error RequestResponseInvocation Check the target application, if it isrunning or not. Check the configuration of Request-Response Invocation 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 RequestResponseInvocation Check repository settings for validconfiguration of the Request-Response Invocation endpoint for this service. Refer Chapter 2, Getting Started for details on setting up a Request-Response Invocation end point and a Request-Response Invocation Service.
AER3-9500012 Request Response Invocation error. Request Response Invocation service %1 with subject %2 received error while processing reply message. Error %3
Error RequestResponseInvocation Check repository settings for validconfiguration of the Request-Response Invocation endpoint for this service. Refer Chapter 2, Getting Started for details on setting up a Request-Response Invocation end point and a Request-Response Invocation Service.
AER3-930003 Publication error. Publication service %1 with publishing subject as %2received 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 and check that the schema/class definitions are present in the repository. ReferChapter 2, Getting Started for details on configuration of Publication Service.
AER3-930006 Publication error. Publication service %1 with publishing subject %2received the event from target application %3. It failed while convertingevent 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 and check that the schema definitions are present in the repository. Refer Chapter 2, Getting Started for details on configuration of Publication Service.
AER3-9300014 Publication error. Publication service %1 with publication subject %2received error while sending event over the wire. Error : %3
Error Publication Check repository settings for validconfiguration of the publish endpoint for this service. ReferChapter 2, Getting Started for details on setting up a publish end point and a Publication Service.
AER3-930015 Property: adr3.preserveFieldBlanks must be set to ON when using message encoding UTF-8 for publisher: %1 in mode: %2
Error RequestResponse Verify that the propertyadr3.preserveFieldBlanks is set to ON.
AER3-890006 Connection Error. Adapter stopping due to persistent connection errors to the SAP system(s)
Error Connection Check the SAP system(s) connected to, and restart the adapter.
AEADR3-600001 JMS Service Configured. This adapter version does not support JMSservices, but one was found. Use the Go To button to select it.
Warning Configuration You have configured a service with transport type as JMS. But the AE Version of this adapter instance does not support JMS. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600002 XML Wire Format found. This adapter version does not support XML WireFormat.
Warning Configuration You have configured a service with XML Wire Format. But the AE Version of this adapter instance does not support XML format. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600003 Subscriber in exploded batch mode found. This adapter version does notsupport Subscriber in Explode Batch Mode.
Warning Configuration You have configured a Subscription service with Exploded Batch Mode. But the AE Version of this adapter instance does not support Subscriber in Exploded Batch Mode. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600004 Connection Retry Mechanism Warning. This adapter version does notsuspend services on connection failure. The configured value ‘AdapterTermination Criteria’ will be ignored.
Warning Configuration You have configured a service with Connection Retry. But the AE Version of this adapter instance does not suspend services on connection failure. You may change the AE Version or the value of ‘Adapter Termination Criteria’ will be ignored.
AEADR3-600005 Connection Retry Mechanism Warning. This adapter version does notsuspend services on connection failure. The configured values ‘Number of Reconnect Attempts Before Suspending Impacted Service(s)’ and ‘Adapter Termination Criteria’ will be ignored.
Warning Configuration You have configured a service with Connection Retry. But the AE Version of this adapter instance does not suspend services on connection failure. You may change the AE Version or the value of ‘Adapter Termination Criteria’ will be ignored.
AEADR3-600006 Empty Service Found. The Service is not Configured Or Class Reference or Endpoint Reference is Empty.
Warning Configuration You have configured an adapter instance with a service which has no schema associated with it. Such an adapter instance cannot be used at run-time. Make sure that you do not have an empty service before deploying the adapter instance.
AEADR3-600007 Absolute Path not Found. Field %1, Palette error. Unable to find specifiedabsolute path. Make sure that you have specified the absolute path correctly.
Error Configuration Absolute path of the Plugin Directory not found. Check the path.
AEADR3-600008 Connection Failure. Test Connection Failed
Information DTA Test Connection to SAP R3 System failed. Check your connection parameters.
AEADR3-600009 Connection Failure. %1
Information DTA Test Connection to SAP R3 System failed. Check your connection parameters.
AEADR3-600010 Connection Success. Hostname – %1, System Name – %2, R-3 Release – %3
Information DTA Indicates normal adapter operation. No action necessary.
AEADR3-600011 Error copying Configuration information/Inbound Connection Type doesnot support copying of connection information from Configuration view.
Error Configuration You are trying to copy Design-Time parameters to Run-Time Inbound Connection which is not of type ’Dedicated.’ If you want to copy, make sure that the default inbound connection type is ’Dedicated’.
AEADR3-600012 Illegal Adapter Instance Name. Adapter Configuration names must haveonly alphanumeric characters with no embedded spaces and can be up to 80 characters long. Type in a valid name.
Error Configuration Cannot rename the adapter instance. Provide a valid name. Make sure you have entered alphanumeric characters, no blank spaces, and the name is not more than 80 characters.
AEADR3-600013 Subject Names. Do you wish to regenerate subjects set to previous defaults?
Error Configuration Click YES to regenerate.
AEADR3-600014 Regenerate Names?. Do you wish to regenerate Subject Names, Connection Names and Session Parameters?
Warning Configuration Click YES to regenerate.
AEADR3-600015 Replace Resource. The resource %1 is already defined as a type. Do you want to replace it?
Warning Configuration Click OK to continue.
AEADR3-600016 Illegal Operation/The new nested name is in conflict with the name of theresource you are editing. Rename the existing resource or choose a different name.
Error Configuration Conflicting resource names. Try using a different name.
AEADR3-600017 Select an IDoc. You did not make a selection.
Error DTA Select an IDoc.
AEADR3-600018 Select an RFC Function. You did not make a selection.
Error DTA Select an RFC function.
AEADR3-600019 IDoc Fetch Failed. %1
Error DTA No IDocs were retrieved. Check your connection parameters and your IDoc filter criteria.
AEADR3-600020 RFC Fetch Failed. %1
Error DTA No RFCs were retrieved. Check your connection parameters and your RFC filter criteria.
AEADR3-600021 Reuse Schema Type. Schema for %1 already exists. Do you want to reuseexisting schema?
Warning Schema This is a Yes/No option. Select Yes if you want to use the existing schema. Select No if you want to re-download the schema for the SAP R3 system.
AEADR3-600022 Deleting Operation Type. Do you want to delete %1 ?
Warning Configuration Delete confirmation. Select Yes to delete.
AEADR3-600023 Invalid Value. Field %1, Palette error. This is not a valid value.
Error Configuration You tried to enter an invalid value in the connection parameters.
AEADR3-600024 Invalid Value. Palette error. Endpoint Reference cannot have null value.
Error Configuration Endpoint Reference is empty. Select a valid end-point reference.
AEADR3-600026 Filter Length Exceeded. Palette error. The RFC Filter cannot be more than 30 characters in Length. Enter a filter value less than 30 characters in length.
Error DTA You have exceeded the filter length. Enter a filter value less than 30 characters in length.
AEADR3-600027 Filter Length Exceeded. Palette error. The RFC Group Filter cannot be more than 26 characters in Length. Enter a filter value less than 26 characters in length.
Error DTA You have exceeded the filter length. Enter a filter value less than 26 characters in length.
AEADR3-600028 Illegal Operation. Selected Resource Can Not Be Moved
Error Configuration No resolution.
AEADR3-600029 Filter Applied to mandatory segments. You have applied the filter on thefollowing mandatory segment(s)
Warning Schema You have applied a filter on mandatory segments. Uncheck the filter on these segments.
AEADR3-600030 Error Occurred. Error Creating Global Variables.
Error Repository TIBCO Designer encountered an error while creating global variables. You may have to manually create global variables in the Global Variables pane.
AEADR3-600031 Not Found. No IDocs Retrieved. Check the filter.
Information DTA Check IDoc Filter.
AEADR3-600032 Not Found. No RFCs Retrieved. Check the filter.
Information DTA Check RFC Filter.
AEADR3-600033 No List. IDoc List could not be retreived-%1′
Information DTA Check IDoc Filter.
AEADR3-600034 No List. RFC – BAPI List could not beretreived-%1′
Information DTA Check RFC/BAPI Filter.
AEADR3-600035 Error Occurred. Conflicting Services. A Publication Service, having the same Schema, is already configured.
Error Schema You already have a Publication service with the same schema. You cannot configure another service in the same adapter instance.
AEADR3-600036 Error Occurred. Conflicting Services. A Subscription Service, having thesame Schema, is already configured.
Error Schema You already have a Subscription service with the same schema. You cannot configure another service in the same adapter instance.
AEADR3-600037 Error Occurred. Conflicting Services. A Request-Response Service, having the same Schema, is already configured.
Error Schema You already have a Request-Response service with the same schema. You cannot configure another service in the same adapter instance.
AEADR3-600038 Error Occurred. Conflicting Services. A Request-Response InvocationService, having the same Schema, is already configured.
Error Schema You already have a Request-Response Invocation service with the same schema. You cannot configure another service in the same adapter instance.
AEADR3-600039 Download Operation Schema. Schema for operation %1 is already available, Use existing schema?
Warning Schema Click YES to reuse existing schema. Click NO to re-download schema from SAP R3 system.
AEADR3-600040 Regenerate Resources ? Do you want to regenerate endpoint and subjectinformation?
Warning Configuration Click YES to regenerate.
AEADR3-600041 Regenerate Resources? Do You want to regenerate Subject Names andSession Parameters?
Warning Configuration Click YES to regenerate.
AEADR3-600042 Regenerate Connections. Do You want to regenerate Connection Names?
Warning Configuration Click YES to regenerate Connection Names.
AEADR3-600043 Error while pasting. Deserialization of Schema Failed.
Error Schema Copy/Paste of schemas failed. Tryconfiguring again.
AEADR3-600044 Error while pasting. Deserialization of R3 Connections Failed.
Error Configuration Copy/Paste of connections failed. Try configuring again.
AEADR3-600045 Error while writing the Meta Url.
Error Configuration Error in Meta URL. Try configuring again.
AEADR3-600046 Inbound Management Warning. This adapter version does not supportInbound Management.
Warning Configuration You have configured an adapter instance with Inbound Management. But the AE Version of this adapter instance does not support Inbound Management. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600047 Advanced Logging Warning. This adapter version does not supportadvanced logging to a file.
Warning Configuration You have configured an adapter instance with advanced logging. But the AE Version of this adapter instance does not support advanced logging to a file. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600048 Confirm Publisher Warning. This adapter version does not support confirm publisher on the inbound side.
Warning Configuration You have configured an adapter instance with advanced logging. But the AE Version of this adapter instance does not support advanced logging to a file. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600049 Valid destination Warning. This adapter version does not support Validating destination on the inbound side
Warning Configuration You have configured an adapter instance to validate destination on the inbound side. But the AE Version of this adapter instance does not support validating destination on the inbound side. You may change the AE Version or make sure that the runtime version is higher than this version.
AEADR3-600050 Not Checked out. Failed to update Schema. The associated Schema files are not checked out from source control.
Error Configuration Check out schema files from the source control.
AEADR3-600051 Illegal child error occurred while processing connection – %1
Error Configuration Error while processing R3 Connection. Try configuring again.
AEADR3-600052 Name conflict error occurred while processing connection – %1
Error Configuration Error while processing R3 Connection. Try configuring again.
AEADR3-600053 Error occurred while applying changes to connection – %1
Error Configuration Error while applying changes to R3 Connection. Try configuring again.
AEADR3-600054 Not Checked out. Failed to update R3Connections. The connection file is not checked out from source control
Error Configuration Check out the connection file from source control.
AEADR3-600055 Error Renaming Service. Service name must only have alphanumericcharacters and must be at most 80 characters long.
Error Configuration Cannot rename the service. Provide a valid name. Make sure you have entered alphanumeric characters, no blank spaces, and the name is not more than 80 characters.
AEADR3-600056 Global Variables File:Read-Only. Global Variable files needs to be checked out in order to successfully create the adapter.
Error Configuration Check out Global Variables file from source control.
AEADR3-600057 Error During Rename : Read-Only File. The resource %1 could not berenamed. Rename requires the %2 should be checked out. Check out theresource and try renaming again. You can select the resource to be checked out by clicking on the Go To Resource button.
Error Configuration Check out the resource and try renaming again.
AEADR3-600058 Error During Delete : Read-Only File/The resource %1 could not be deleted. Delete requires the %2 should be checked out. Check out the resource and try deleting again. You can select the resource to be checked out by clicking on the Go To Resource button.
Error Configuration Check out the resource and try deleting again.
AEADR3-600059 Error During Creation of Service : Read-Only File. The service can not becreated. Creation requires the %1 should be checked out. Check out theresource and try creating the service again. You can select the resource to be checked out by clicking on the Go To Resource button.
Error Configuration Check out the resource and try creating the service again.
AEADR3-600060 Need to Add File to RCS: %1 was created during schema generation. Ensure that this resource is added to RCS and checked in. Click on the Go To Resource button to select the resource.
Warning Configuration Ensure that this resource is added to RCS and checked in.
AEADR3-600061 RFC/BAPI: %1: Import/Export parameters referencing String data type areignored.
Warning 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.

AEADR3-600062 RFC/BAPI: %1: Invalid parameter: %2, (%3) data type not allowed. Removeselection.
Error Configuration When downloading a RFC/BAPIcontaining parameters referring to a table type or complex or nested type remove selection by unchecking the selection. If this RFC/BAPI is required, create a custom module and use the internal tables and flat structures.

The following table lists error messages for which codes have been changed.

Table 15 Error Messages with Changed Codes
NewMessage Code OldMessage Code Severity Cat. Description Resolution
AER3-000000 R3-CORE-APP-8000 INFO AD The request does not contain closure data for operation %1 Indicates normal adapter operation. No action necessary.
AER3-000001 R3-CORE-APP-8001 Error AD Invalid closure data for operation %1 Create a correct instance of RFC_CLOSURE defined in SAPAdapterSchema.xml and set it as closure data in the request to be sent to the inbound adapter. To find out more about closure, refer to TIB Adapter SDK documentation and TIBCO 2.0 ActiveEnterprise wire format.
AER3-000002 R3-CORE-APP-8002 Error AP Invalid value for attribute %1 for operation %2 Verify if you are using the correct class descriptions and value specified is valid and no mandatory values are omitted.
AER3-000003 R3-CORE-APP-8003 Error AD Function call is transactional but no provided When you set bTransactional in closure, you must also supply a value for .
AER3-000004 R3-CORE-APP-8004 INFO S Adapter application %1 is stopped Indicates normal adapter operation. No action necessary.
AER3-000005 R3-CORE-CFG-1000 Error C Could not find interface description element 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 R3-CORE-CFG-1001 Error C %1 not specified for %2 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-000007 R3-CORE-CFG-1003 INFO C management is local It is advisable to use a remote Manager if more than multiple adapters are running in a load balanced manner. This is to ensure that the failed transactions are not executed twice among the load balanced group. This means that it is possible to get duplicate messages if more than one adapters are being run in a load balanced configuration and are setup to do local management.
AER3-000008 R3-CORE-CFG-1004 Error C file is not specified Specify the file name, attribute “tidFileName” in the adapter instance level Adapter Servicestab.
AER3-000009 R3-CORE-CFG-1005 Error C Timer %1 does not exist Provide a correct reference to the TIB Adapter SDK timer in the server connection section of the connection manager.
AER3-000010 R3-CORE-CFG-1006 Error C The interface %1 does not specify attribute ‘classRef’ Provide a correct reference to the TIBCO Adapter SDK timer in the server connection section of the connection manager
AER3-000011 R3-CORE-CFG-1007 Error C Invalid producer %1 Provide a correct reference to an TIBCO Adapter SDK producer (publisher).
AER3-000013 R3-CORE-CFG-1009 Error C No RpcClient specified for operation %1 Provide a valid reference to an TIB Adapter SDK RPC Client through “mbRpcClientRef” element in Deployment Descriptions of IDocs.
AER3-000014 R3-CORE-CFG-1010 WARN C Interface %1 does not contain deployment description for IDocs… continuing… 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 R3-CORE-CFG-1011 INFO C Invalid producer %1; using default producer %2 Indicates normal adapter operation. No action necessary.
AER3-000016 R3-CORE-CFG-1012 Error C Invalid consumer component %1 Modify your configuration by defining a consumer name as suggested by the error description.
AER3-000017 R3-CORE-CFG-1013 Error C No components defined in the configuration document Modify your configuration so that it has at least one component under the ‘components’ section.
AER3-000018 R3-CORE-CFG-1014 Error C No connection manager defined in the configuration document Modify your configuration so that it has a ‘connectionManager’ under the ‘connectionManagers’ section.
AER3-000019 R3-CORE-CFG-1015 Error C Invalid rpcServer %1 specified for interface %2 Modify your configuration so that it has a ‘connectionManager’ under the ‘connectionManagers’ section.
AER3-000020 R3-CORE-CFG-1016 Error C The Subscriber Description does not specify consumer reference, skipping … Add consumerRef attribute in the configuration.
AER3-000021 R3-CORE-CFG-1017 Error C Consumer %1 for deployment description %2 does not exist ConsumerRef must point to a valid subscriber.
AER3-000022 R3-CORE-CFG-1018 WARN C No instance defined for %1; control fields will not be replaced You must have an instance defined under class instances.
AER3-000023 R3-CORE-CFG-1019 WARN C Invalid reference for attribute consumerRef ConsumerRef must point to a valid subscriber.
AER3-000024 R3-CORE-FIL-3000 Error S Error while reading directory=%1, filename=%2; %3 Determine the cause from the error description.
AER3-000025 R3-CORE-FIL-3001 WARN S directory=%1, filename=%2; No matching files found There were no matching files. Check your filenames.
AER3-000026 R3-CORE-FIL-3002 Error S Could not open %1 for reading The specific file could not be opened. Check permissions.
AER3-000027 R3-CORE-FIL-3003 Error S %1 is unreadable Check whether the file can be opened using a text editor.
AER3-000028 R3-CORE-FIL-3004 WARN S %1 is empty File is empty.
AER3-000029 R3-CORE-FIL-3005 Error S %1 does not contain newline. Perhaps not a text file The file is not a text file, because it does not contain a new line.
AER3-000030 R3-CORE-FIL-3006 INFO AD IDoc from file %1 sent in %2 mode Indicates normal adapter operation. No action necessary.
AER3-000031 R3-CORE-IDC-7000 Error AD Unsupported datatype %1 The datatype is unsupported by SDK or SAP or both.
AER3-000032 R3-CORE-IDC-7001 WARN AD Cannot get control record for IDoc The IDoc does not have a control record. If it’s not intentional, add a control record.
AER3-000033 R3-CORE-IDC-7002 Error AD class name invalid for IDoc The adapter received an IDoc but could not determine its class. If you are creating the IDoc meant to be consumed by the adapter, ensure that you are creating it correctly.
AER3-000034 R3-CORE-LIB-6000 WARN AD False call to %1 See the error description for more details.
AER3-000035 R3-CORE-LIB-6001 WARN AD Could not generate GUID Even though a warning, this message is often indicative of a memory-low situation that could severely affect the adapter performance.
AER3-000036 R3-CORE-LIB-6002 Error AD No connection for %1 The named component does not have a valid connection Manager. Refer also to the description for ‘R3-CORE-CFG-1014’.
AER3-000037 R3-CORE-LIB-6003 Error AD Could not create Manager If the problem persists, repeat with remote Management.
AER3-000038 R3-CORE-LIB-6004 Error C Could not find default client connection 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 R3-CORE-LIB-6005 Error AD No proxy defined to process request for RFC function %1 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-000040 R3-CORE-LIB-6006 INFO AD Adding RFC function %1 For an inbound configuration, the message means that the Adapter can serve as an RFC Client; for an outbound configuration, the message means that the Adapter can serve as an RFC Server.
AER3-000041 R3-CORE-LIB-6007 Error AD Unable to create RFC server function %1 Look at earlier error messages in the log file(s) for possible causes.
AER3-000042 R3-CORE-LIB-6008 Error AD Unable to create request proxy for %1 Look at earlier error messages in the log file(s) for possible causes.
AER3-000043 R3-CORE-LIB-6009 Error AD Unable to create RFC client for %1 Look at earlier error messages in the log file(s) for possible causes.
AER3-000044 R3-CORE-LIB-6010 Error AD Unable to create function impl for %1 Look at earlier error messages in the log file(s) for possible causes.
AER3-000045 R3-CORE-LIB-6011 Error AD RFC function initialization failure : %1; function name : %2 Look at the error description for the cause of the failure.
AER3-000046 R3-CORE-LIB-6012 Error AD Cannot create publisher proxy for %1 Look at earlier error messages in the log file(s) for possible causes.
AER3-000047 R3-CORE-LIB-6014 Error AP %1 is not a valid structure or table 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 R3-CORE-LIB-6015 Error AD Unpacking error: Invalid class type for structure %1 Data inappropriate for the named structure. See also R3-CORE-LIB-6014.
AER3-000049 R3-CORE-LIB-6016 Error AD Unpacking error: Invalid class type for table %1 Data inappropriate for the named table. See also R3-CORE-LIB-6014.
AER3-000050 R3-CORE-LIB-6017 Error AP Unpacking error: Row of table %1 is not a structure Data inappropriate for the named table. See also R3-CORE-LIB-6014.
AER3-000051 R3-CORE-LIB-6018 INFO AD User-defined operation called successfully The Adapter invoked the user-defined operation successfully.
AER3-000052 R3-CORE-LIB-6019 Error AD Invalid or no data received from user-defined operation Check the program that implements the user-defined operation and make sure that it returns data.
AER3-000053 R3-CORE-LIB-6020 Error AD User-defined operation invocation exception; name : %1, data : %2 Ensure that your operation executes without any exception and that it returns valid data to the Adapter.
AER3-000054 R3-CORE-LIB-6021 Error AD User-defined operation invocation timeout Ensure that the Rpc Server that implements your operation is running and that it is reachable from the Adapter.
AER3-000055 R3-CORE-LIB-6022 Error AD User-defined operation invocation : bad reply received Ensure that your operation returns valid data to the Adapter.
AER3-000056 R3-CORE-LIB-6023 Error AD User-defined operation invocation exception; name : %1 Ensure that your operation executes without any exception and that it returns valid data to the Adapter.
AER3-000057 R3-CORE-LIB-6024 Error AD The request sent to user-defined operation contains invalid data If you’re constructing the data to be sent to the user-defined operation, ensure that it’s being constructed correctly.
AER3-000058 R3-CORE-LIB-6025 Error AD Invalid operation name for IDoc %1 The Adapter found that the IDoc data is arriving from a function other than ‘IDOC_INBOUND_ASYNCHRONOUS’ or ‘INBOUND_IDOC_PROCESS’.
AER3-000059 R3-CORE-LIB-6026 Error AD Cannot create IDoc parser instance 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 R3-CORE-LIB-6027 Error AP Invalid RFC function %1 Look at earlier error messages in the log file(s) for possible causes.
AER3-000061 R3-CORE-LIB-6028 WARN AD The IDoc %1 could not be exploded See R3-CORE-LIB-6026.
AER3-000062 R3-CORE-LIB-6029 Error AD Unable to create reply listener for operation %1 See earlier messages in the log file(s) for possible causes.
AER3-000063 R3-CORE-LIB-6030 Error AD RFC invocation timeout for function %1; description : %2 The named RFC function invocation timed out. See error description for more details.
AER3-000064 R3-CORE-LIB-6031 Error AD RFC invocation bad reply for function %1; description : %2 The named RFC function returned a bad reply. See error description for more details.
AER3-000065 R3-CORE-LIB-6032 Error AD RFC invocation remote exception; name : %1, description : %2 The named RFC function caused a remote exception. See error description for more details.
AER3-000066 R3-CORE-LIB-6033 Error AD Cannot create IDoc parser instance for subscriber %1 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-000067 R3-CORE-LIB-6034 WARN AD Invalid MTree data received for subscriber See earlier error messages in the log file(s) for possible causes.
AER3-000068 R3-CORE-LIB-6035 Error AD Cannot create IDoc data instance from received IDoc tree The adapter subscriber received MTree data but the received data could not be converted to an MInstance. Because an MInstance is an MTree bounded by a class, the error implies that the received MTree 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-000069 R3-CORE-LIB-6036 Error AD Cannot implode IDoc %1 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 R3-CORE-LIB-6037 Error AD Cannot get RFC client function %1 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 R3-CORE-LIB-6038 Error AD Cannot get marshaller for RFC client function %1 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-000072 R3-CORE-LIB-6039 Error AP Client connection %1 is invalid Ensure that the login parameters are correct and that the Adapter can reach the SAP system.
AER3-000073 R3-CORE-LIB-6040 Error AP Cannot get RFC connection for client %1 See R3-CORE-LIB-60.
AER3-000074 R3-CORE-LIB-6041 Error AD Operation %1 timed out Make sure that the RPC Server that corresponds to the named operation is executing and is accessible from the Adapter.
AER3-000075 R3-CORE-LIB-6042 WARN AD Operation %1 returned a bad reply %2 The named operation returned a bad reply. Look at the error message description for more details.
AER3-000076 R3-CORE-LIB-6043 Error AD Initialization exception type : %1, operation : %2, description : %3 The named operation returned the named exception. Look at the error message description for more details.
AER3-000078 R3-CORE-LIB-6045 INFO AD Successfully added RFC function %1 The Adapter successfully added the named RFC function. Depending on the configuration, the adapter can function as an RFC client, RFC Server, or both.
AER3-000079 R3-CORE-LIB-6046 Error AD Unpacking error 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 R3-CORE-LIB-6047 WARN AD Could not create TIBCO RV advisory handlers; exception type : %1, description : %2 The Adapter could not create the license expiry advisories. Look at the error description for more details.
AER3-000081 R3-CORE-LIB-6048 WARN AD Could not create TIBCO Hawk implants; exception type : %1, description : %2 The adapter could not create TIBCO Hawk implants. Look at the error description for more details.
AER3-000082 R3-CORE-LIB-6049 INFO AD Successful initialization of Adapter Indicates normal adapter operation. No action necessary.
AER3-000083 R3-CORE-LIB-6050 Error AD Unable to create operation request for function : %1, class : %2, rpcClient : %3 The Adapter could not create Operation request for the named function. Look at the error description for more details.
AER3-000084 R3-CORE-LIB-6051 INFO AP Received IDoc Name/Number/Receiving Partner: %1, Count: %2 Indicates normal adapter operation. No action necessary.
AER3-000085 R3-CORE-LIB-6052 INFO AD IDoc sent in %1 mode Indicates normal adapter operation. No action necessary.
AER3-000086 R3-CORE-LIB-6053 INFO AD IDoc received in %1 mode Indicates normal adapter operation. No action necessary.
AER3-000087 R3-CORE-LIB-6054 INFO AD IDoc Sent to SAP System Indicates normal adapter operation. No action necessary.
AER3-000088 R3-CORE-LIB-6055 INFO AD IDoc sent as a Business Document Indicates normal adapter operation. No action necessary.
AER3-000089 R3-CORE-LIB-6056 INFO AD IDoc received as a Business Document Indicates normal adapter operation. No action necessary.
AER3-000090 R3-CORE-LIB-6057 INFO C The Destination %1 in not defined, IDoc is logged to file %2 Indicates normal adapter operation. No action necessary.
AER3-000091 R3-CORE-LIB-6058 INFO AD Total IDocs processed: %1 Indicates normal adapter operation. No action necessary.
AER3-000092 R3-CORE-LIB-6059 INFO AD The subscriber for this IDoc message could not be determined Indicates normal adapter operation. No action necessary.
AER3-000093 R3-CORE-LIB-6060 INFO AD IDoc Message sequence number %1 confirmed to %2 Indicates normal adapter operation. No action necessary.
AER3-000094 R3-CORE-LIB-6061 INFO AD Preparing to send IDoc to client %1 Indicates normal adapter operation. No action necessary.
AER3-000095 R3-CORE-LIB-6062 INFO AD IDoc sent to client %1 Indicates normal adapter operation. No action necessary.
AER3-000096 R3-CORE-LIB-6064 INFO AD IDoc Message sequence number %1 could not be confirmed to %2, Use pre-registration of subscribers Indicates normal adapter operation. No action necessary.
AER3-000097 R3-CORE-LIB-6065 INFO C IDoc Message could not be confirmed, validation must be turned off, if 10X Publishers used Indicates normal adapter operation. No action necessary.
AER3-000098 R3-CORE-LIB-6066 INFO AP IDoc RFC Function invoked: %1 Indicates normal adapter operation. No action necessary.
AER3-000099 R3-CORE-LIB-6067 INFO AD RFC Function invoked: %1 Indicates normal adapter operation. No action necessary.
AER3-000100 R3-CORE-LIB-6068 WARN C User-defined operation: operation not specified, assuming ‘transform’ If the default transfer is not desired, name your operation explicitly.
AER3-000101 R3-CORE-LIB-6069 WARN C User-defined operation reference: operationRpcClientRef not specified, operation will not be invoked The operation requires an rpcClient, specific through operationRpcClientRef. Specify this client.
AER3-000102 R3-CORE-LIB-6070 Error AD operation timed out. Make sure that Manager is running Make sure Manager is running and is accessible from the Adapter. Also, ensure that subject names match.
AER3-000103 R3-CORE-LIB-6071 INFO AD Adding %1 parameter %2, Type %3 Indicates normal adapter operation. No action necessary.
AER3-000104 R3-CORE-LIB-6072 INFO AD Setting up Imports and Exports for RFC function %1 Indicates normal adapter operation. No action necessary.
AER3-000105 R3-CORE-LIB-6073 INFO AD RFC function has %1 imports, %2 exports Indicates normal adapter operation. No action necessary.
AER3-000106 R3-CORE-LIB-6074 INFO AD %1 = { %2 } Indicates normal adapter operation. No action necessary.
AER3-000107 R3-CORE-LIB-6075 INFO AD Number of records in table %1 = %2 Indicates normal adapter operation. No action necessary.
AER3-000108 R3-CORE-LIB-6076 INFO AD Invoking function: %1 … Indicates normal adapter operation. No action necessary.
AER3-000109 R3-CORE-LIB-6077 INFO AD Successfully invoked function: %1 Indicates normal adapter operation. No action necessary.
AER3-000110 R3-CORE-LIB-6078 INFO AD Reply sent for function: %1 Indicates normal adapter operation. No action necessary.
AER3-000111 R3-CORE-LIB-6079 INFO AD Received reply for: %1 … Indicates normal adapter operation. No action necessary.
AER3-000112 R3-CORE-LIB-6080 INFO AD Data sent back to SAP System Indicates normal adapter operation. No action necessary.
AER3-000113 R3-CORE-LIB-6081 INFO AD Performing one way invocation on the server Indicates normal adapter operation. No action necessary.
AER3-000114 R3-CORE-LIB-6082 INFO AD Received invocation request for %1 from SAP System Indicates normal adapter operation. No action necessary.
AER3-000115 R3-CORE-LIB-6083 INFO AD Performing invocation on the server Indicates normal adapter operation. No action necessary.
AER3-000116 R3-CORE-LIB-6084 INFO AD Function call is transactional, : %1 Indicates normal adapter operation. No action necessary.
AER3-000117 R3-CORE-LIB-6085 INFO AD Received invocation request for %1 Indicates normal adapter operation. No action necessary.
AER3-000118 R3-CORE-LIB-6086 INFO AD Invoking RFC function %1 in SAP System Indicates normal adapter operation. No action necessary.
AER3-000119 R3-CORE-LIB-6087 INFO AD Received one way invocation request for %1 Indicates normal adapter operation. No action necessary.
AER3-000120 R3-CORE-LIB-6088 INFO AD Invoking transactional RFC function %1 in SAP System Indicates normal adapter operation. No action necessary.
AER3-000121 R3-CORE-LIB-6089 INFO C Cannot get class descriptions for control record of IDoc class %1 Indicates normal adapter operation. No action necessary.
AER3-000122 R3-CORE-LIB-6090 Error AP The IDoc %1 does not contain a control record Make sure that the IDoc contains a control record.
AER3-000123 R3-CORE-LIB-6091 Error C Cannot get class descriptions for data record of IDoc class %1 During configuration ensure that you are downloading the class descriptions.
AER3-000124 R3-CORE-LIB-6092 Error AD The received IDoc tree in exploded form is null Make sure that the Tree (MTree in SDK) is created correctly and corresponds to an IDoc.
AER3-000125 R3-CORE-LIB-6093 Error C Class descriptions cannot be obtained for received IDoc tree During configuration ensure that you are downloading the class descriptions.
AER3-000126 R3-CORE-LIB-6094 Error C %1 is not of a sequence type The named sequence does not have a valid definition. Check the configuration.
AER3-000127 R3-CORE-LIB-6095 Error C Sequence %1 does not have a contained class description A sequence is a sequence of objects of type T. The adapter could not determine T, probably because the definitions don’t exist in the configuration.
AER3-000128 R3-CORE-LIB-6096 Error C Sequence %1 for the segment holder could not be obtained Check configuration and make sure that a valid definition exists for the named sequence.
AER3-000129 R3-CORE-LIB-6097 Error C Segment %1 does not have attribute: %2 The data mentioned contains the named attribute, but the class definition does not. Check the configuration and how the IDoc is being created.
AER3-000130 R3-CORE-LIB-6098 Error C Cannot obtain field class description for IDoc Segment Check configuration.
AER3-000131 R3-CORE-LIB-6099 Error AD Cannot get EDIDD header attribute from the fields for segment %1 Check the data. It must include the EDIDD header.
AER3-000132 R3-CORE-LIB-6100 Error C Cannot obtain class description for segment %1 attribute %2 Check the segment name as well as the attribute and make sure that a definition exists in the configuration.
AER3-000133 R3-CORE-LIB-6101 INFO AD The segment instance %1 does not contain attribute %2 Indicates normal adapter operation. No action necessary.
AER3-000134 R3-CORE-LIB-6102 INFO AD The default values will be used Indicates normal adapter operation. No action necessary.
AER3-000135 R3-CORE-LIB-6103 INFO AD Segment name: %1 added Indicates normal adapter operation. No action necessary.
AER3-000136 R3-CORE-LIB-6104 Error AD The %1 record sequence does not contain a valid control record Check the data first. Make any changes. Check the configuration for an appropriate definition.
AER3-000137 R3-CORE-LIB-6105 Error C The %1 record of the IDoc does not have a valid class description Check the data first. Make any changes. Check the configuration for an appropriate definition.
AER3-000138 R3-CORE-LIB-6106 INFO AD The %1 record does not contain attribute %2 Indicates normal adapter operation. No action necessary.
AER3-000139 R3-CORE-LIB-6107 INFO AD trying to recover the received message … Indicates normal adapter operation. No action necessary.
AER3-000140 R3-CORE-LIB-6108 INFO AD Subscriber: %1, Exception occurred on receiving the message Indicates normal adapter operation. No action necessary.
AER3-000141 R3-CORE-LIB-6109 Error AD Subscriber: %1, the message could not be recovered Indicates normal adapter operation. No action necessary.
AER3-000142 R3-CORE-LIB-6110 INFO AD Subscriber: %1, The 10X Opaque message type is not supported Indicates normal adapter operation. No action necessary.
AER3-000143 R3-CORE-LIB-6111 INFO AD the received message was recovered Indicates normal adapter operation. No action necessary.
AER3-000144 R3-CORE-LIB-6112 INFO AD The IDoc message received in 10X format does not contain %1field Indicates normal adapter operation. No action necessary.
AER3-000145 R3-CORE-LIB-6113 Error C The class descriptions for IDoc base classes cannot be obtained from the registry During configuration ensure that you’ve downloaded the class definition.
AER3-000146 R3-CORE-LIB-6114 INFO AD Function called transactionally but Transaction Identifier () not supplied Indicates normal adapter operation. No action necessary.
AER3-000147 R3-CORE-LIB-6115 Error S Could not open file %1 for writing File could not be opened. Check permissions and whether you’ve adequate space on your disk.
AER3-000148 R3-CORE-LIB-6116 Error AD CIDocIterator: The IDoc container does not contain any IDocs Check the log file for any previous errors that may have led to this situation.
AER3-000149 R3-CORE-LIB-6117 Error AD The IDoc %1 does not contain %2 The IDoc does not contain a data record section. Check the IDoc data.
AER3-000150 R3-CORE-LIB-6118 Error AD No control record instance for the %1 IDoc in the packet The named IDoc does not have a control record. Check the data.
AER3-000151 R3-CORE-LIB-6119 Error AD No data record instance for the %1 IDoc in the packet The IDoc does not contain a data record section. Check the data.
AER3-000152 R3-CORE-LIB-6120 Error AD %1 record of the data record instance does not contain mandatory attribute DOCNUM DOCNUM is a mandatory attribute for data record. Check the data and modify it to include DOCNUM.
AER3-000153 R3-CORE-LIB-6121 INFO AD %1 row of the data record instance of the %2 IDoc instance of type %3 could not be obtained Indicates normal adapter operation. No action necessary.
AER3-000154 R3-CORE-LIB-6122 Error S The IDoc instance could not be written to file, the instance is invalid The Instance could not be written because it was empty. Check the IDoc data.
AER3-000155 R3-CORE-LIB-6123 Error AD The IDoc does not contain a data record The IDoc does not contain a data record section. Check the IDoc data.
AER3-000156 R3-CORE-LIB-6124 INFO AD Writing IDoc %1, Number %2 to file: %3, ServiceName %4 SubjectName %5 Indicates normal adapter operation. No action necessary.
AER3-000157 R3-CORE-LIB-6125 INFO AD Invocation for RFC function %1 still pending Indicates normal adapter operation. No action necessary.
AER3-000158 R3-CORE-LIB-6126 INFO AD Adapters initialization mode:%1 Indicates normal adapter operation. No action necessary.
AER3-000159 R3-CORE-LIB-6127 WARN AD Cannot find communication client for Manager, Management will be local The configuration does not specify the rpcClient for Manager, hence the management will be local.
AER3-000160 R3-CORE-LIB-6128 INFO AD Connection: waiting for reply from server … Indicates normal adapter operation. No action necessary.
AER3-000161 R3-CORE-LIB-6129 INFO AD No component for the RFC call; Exception=%1 Indicates normal adapter operation. No action necessary.
AER3-000162 R3-CORE-LIB-6130 INFO AD Active connection is null Indicates normal adapter operation. No action necessary.
AER3-000163 R3-CORE-LIB-6131 INFO AD Checking for connections Indicates normal adapter operation. No action necessary.
AER3-000164 R3-CORE-LIB-6132 INFO AD Connection disconnected Indicates normal adapter operation. No action necessary.
AER3-000165 R3-CORE-LIB-6133 INFO AD Connection re-established Indicates normal adapter operation. No action necessary.
AER3-000166 R3-CORE-LIB-6134 INFO AD Connection State: Available Indicates normal adapter operation. No action necessary.
AER3-000167 R3-CORE-LIB-6135 INFO AD Connection State: Pending invocation Indicates normal adapter operation. No action necessary.
AER3-000168 –NEW– INFO AD %1 connection could not be removed Indicates normal adapter operation. No action necessary.
AER3-000169 R3-CORE-LIB-6136 WARN AD Subscriber %1 could not be suspended The named subscriber could not be suspended. No action necessary.
AER3-000170 R3-CORE-LIB-6137 WARN AD Stop Adapter: Correct consumer reference could not be obtained from deployment description %1, skipping… The configuration did not specify consumerRef. No action necessary.
AER3-000171 R3-CORE-LIB-6138 INFO AD Adapter is waiting for invocation response before shutdown can proceed… Indicates normal adapter operation. No action necessary.
AER3-000172 R3-CORE-LIB-6139 INFO AD Adapter stop method called Indicates normal adapter operation. No action necessary.
AER3-000173 R3-CORE-LIB-6141 INFO AD Subscriber %1 suspended Indicates normal adapter operation. No action necessary.
AER3-000174 R3-CORE-LIB-6142 INFO AD Connection Manager %1 stopped Indicates normal adapter operation. No action necessary.
AER3-000175 R3-CORE-LIB-6143 INFO AD Component %1 stopped Indicates normal adapter operation. No action necessary.
AER3-000176 R3-CORE-LIB-6144 INFO AD Deactivating stop scheduler Indicates normal adapter operation. No action necessary.
AER3-000177 R3-CORE-LIB-6145 INFO AD Stopping Adapter %1 instance on host %2 Indicates normal adapter operation. No action necessary.
AER3-000178 R3-CORE-LIB-6146 INFO AD Stop notification received via TIBCO RV Indicates normal adapter operation. No action necessary.
AER3-000179 R3-CORE-LIB-6147 Error AD Remote Exception: Exception Name: %1, Exception Data: %2 See the error description for details.
AER3-000180 R3-CORE-RVD-9000 WARN AD ADV_CLASS/ADV_SOURCE/ADV_NAME: %1, ADV_DESC : %2 %3 See the error description for more details.
AER3-000181 R3-CORE-RVD-9001 Error AD ADV_CLASS/ADV_SOURCE/ADV_NAME: %1, ADV_DESC : %2 %3 The adapter responds ‘license expiry’ warning from the daemon with this message.
AER3-000182 R3-CORE-RVD-9002 Error AD ADV_CLASS : %1, ADV_SOURCE : %2, ADV_NAME : %3 The adapter responds ‘registration collision’ error from the daemon with this message.
AER3-000183 R3-CORE-SAP-4000 Error AP RFC error; Group : %1, Key : %2, Message : %3 Look at the error description for details about the SAP Exception. Also check your connection parameters.
AER3-000184 R3-CORE-SAP-4001 Error AP RFC connection invalid for %1 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 R3-CORE-SAP-4002 Error AP CallReceive failed for operation %1; exception : %2, RFC error; Group/Key/Message: %3 Look at the error description for details about the SAP Exception.
AER3-000186 R3-CORE-SAP-4003 INFO AP Transaction %1 skipped The Adapter did not execute this transaction because it was already executed.
AER3-000187 R3-CORE-SAP-4004 WARN AP Invalid transaction state received from Manager for transaction %1 The Adapter received an invalid stated from Manager. Check the tidmanager display for possible causes.
AER3-000188 R3-CORE-SAP-4005 WARN AD Failed to %1 Tid The Adapter could not perform the named /Manager function. Check the /Manager display for possible causes.
AER3-000189 R3-CORE-SAP-4007 Error AP RFC function initialization error for function %1; RFC Error; Group/Key/Message : %2 Look at the error description for details about the SAP Exception.
AER3-000190 R3-CORE-SAP-4008 WARN AD RFC remote function %1 implementation exception %2 Look at the error description for details about the SAP Exception.
AER3-000191 R3-CORE-SAP-4009 Error AP Indirect call error while sending IDoc; RFC Error; Group : %1, Key : %2, Message : %3 Look at the error description for details about the SAP Exception.
AER3-000192 R3-CORE-SAP-4010 Error AP RFC error; Group : %1, Key : %2, Message : %3, Attempt to connect timed out See the error description for details.
AER3-000193 R3-CORE-SAP-4011 Error AD Connection not available for client %1, retrying … See the error description for details.
AER3-000194 R3-CORE-SAP-4012 INFO AD Invalid RFC client connection object for client %1 Indicates normal adapter operation. No action necessary.
AER3-000195 R3-CORE-SAP-4013 INFO AD Transaction created %1 Indicates normal adapter operation. No action necessary.
AER3-000196 R3-CORE-SAP-4014 INFO AD Transaction skipped %1 Indicates normal adapter operation. No action necessary.
AER3-000197 R3-CORE-SAP-4015 INFO AD Transaction committed %1 Indicates normal adapter operation. No action necessary.
AER3-000198 R3-CORE-SAP-4016 INFO AD Transaction confirmed %1 Indicates normal adapter operation. No action necessary.
AER3-000199 R3-CORE-SAP-4017 INFO AD Transaction rolled back %1 Indicates normal adapter operation. No action necessary.
AER3-000200 R3-CORE-SAP-4018 Error AD Failed to update state for transaction %1. Ensure that the user has write permissions for tidFile.tid Look at the earlier error messages in the log-file(s) for possible causes. One of the reasons for this error could be that, you do not have write permissions for the tidFile.tid.
AER3-000201 R3-CORE-SAP-4019 INFO AD Starting Inbound transaction %1 Indicates normal adapter operation. No action necessary.
AER3-000202 R3-CORE-SAP-4020 INFO AD Inbound transaction %1 completed Indicates normal adapter operation. No action necessary.
AER3-000203 R3-CORE-SCH-5000 Error C No class definition exists for %1 The named class is invalid or does not exist. Check the repository to make sure that a valid class exists with that name.
AER3-000204 R3-CORE-SCH-5001 Error C %1 is not a modeled class 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 R3-CORE-SCH-5002 Error C No operations defined in class %1 Modify the class definition to include operations.
AER3-000206 R3-CORE-SCH-5003 Error C The operation %1 does not have any parameters Modify the class definition to include parameters.
AER3-000207 R3-CORE-SCH-5004 Error C The class %1 does not specify attribute %2 The attribute is invalid for the named class. Check the repository. Re-create the class definition (if you suspect it has been incorrectly created) or modify the class definition to include the named attribute.
AER3-000208 R3-CORE-SCH-5005 Error C Operation description not available for %1 The named operation is invalid or non-existent. Check the repository to make sure that an operation exists with the specified name.
AER3-000209 R3-CORE-SCH-5006 Error C No IDoc operations defined in class %1 The named class does not have IDoc operations defined. Check the repository to make sure that the class definition is correct.
AER3-000210 R3-CORE-SCH-5008 Error C Attribute %1 in class %2 is invalid Check the configuration.
AER3-000211 R3-CORE-SCH-5009 Error AD Unsupported type %1 for attribute %2 in class %3 The named type is unsupported by SDK or SAP or both.
AER3-000212 R3-CORE-SCH-5010 Error AD Unexpected %1 : %2; inform technical support Unexpected error. You cannot determine the cause from the description. Contact technical support: support@tibco.com.
AER3-000213 R3-CORE-SCH-5011 WARN C Control field replacements specify an attribute %1 which does not exist in the control record Control field replacements in classInstances specify an attribute that does not exist in control record. Check spelling.
AER3-000214 R3-CORE-SDK-2000 Error AD Cannot access class registry 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 R3-CORE-SDK-2001 Error AD Subscriber %1 received a message that has invalid wire format There was an exception in the Adapter upon receive of this message. When you are using 10x style, follow the configuration requirements given in Chapter 3, Adapter Instance Options.
AER3-000261 –NEW– INFO AD Using ini file %1 Indicates normal adapter operation. No action necessary.
AER3-000262 –NEW– INFO AD No program ID defined in the ini file, using destination %1 as program ID Indicates normal adapter operation. No action necessary.
AER3-000263 –NEW– INFO AD Using Logon Groups Indicates normal adapter operation. No action necessary.
AER3-000264 –NEW– INFO AD Using a dedicated connection Indicates normal adapter operation. No action necessary.
AER3-000265 –NEW– INFO AD Creating a Server connection Indicates normal adapter operation. No action necessary.
AER3-000266 –NEW– INFO AD Initialized successfully Indicates normal adapter operation. No action necessary.
AER3-000267 –NEW– INFO AD CREATED %1 Indicates normal adapter operation. No action necessary.
AER3-000268 –NEW– INFO AD EXECUTED %1 Indicates normal adapter operation. No action necessary.
AER3-000269 –NEW– INFO AD CONFIRMED %1 Indicates normal adapter operation. No action necessary.
AER3-000270 –NEW– Error AD Invalid client function specified in removeClient call Because this message appears during shutdown, no action is necessary.
AER3-000271 –NEW– Error C Invalid poolRef name %1 poolRef must point to a valid pool definition.
AER3-000272 –NEW– Error C Pool reference not provided in Server Component Provide a value that corresponds to a valid definition.
AER3-000273 –NEW– Error AD Invalid Connection for pool %1 Check the pool definitions to ensure that they are valid.
AER3-000274 –NEW– Error AD Invalid default Connection for pool %1 Check the pool definitions to ensure that they are valid.
AER3-000275 –NEW– Error C No default session defined The configuration must either specify a valid value for start up/default session or define at least one rvSession/rvCmSession.
AER3-000276 –NEW– Error AD Duplicate DEST parameter defined in %1 : %2 Remove duplicate definition.
AER3-000277 –NEW– Error AD Destination %1 not defined in %2 Define destination given in message.
AER3-000278 –NEW– INFO AD Received message is written to file %1 Indicates normal adapter operation. No action necessary.
AER3-000279 –NEW– Error AD Exception while initializing adapter; exception type : %1, description : %2 Refer to the description and take the required action.
AER3-000280 –NEW– Error AD Error: Could not send reply for function: %1 Refer to the accompanying error messages for additional details.
AER3-000281 –NEW– Error AD Error while invoking User-defined operation: %1 Refer to the accompanying error messages for additional details.
AER3-000282 –NEW– Error AD Receive reply failed for: %1 Refer to the accompanying error messages for additional details.
AER3-000283 –NEW– Error AD Exception during one way invocation of function: %1, Type: %2, Description: %3 Refer to the accompanying error messages for additional details.
AER3-000284 –NEW– INFO AD Request written to file: %1 for operation: %2 Indicates normal adapter operation. No action necessary.
AER3-000285 –NEW– Error AD Error code: %1, Message: %2 Refer to the description and take the required action.
AER3-000286 –NEW– INFO C ‘userExit’ class does not exist or it does not contain operation %1, operation will not be invoked Indicates normal adapter operation. No action necessary.
AER3-000287 –NEW– INFO C There is no RpcClient named: %1, operation will not be invoked Indicates normal adapter operation. No action necessary.
AER3-000288 –NEW– INFO AD Untransformed IDoc data sent Indicates normal adapter operation. No action necessary.
AER3-000289 –NEW– INFO AD Performing asynchronous invocation for User-defined function: %1 Indicates normal adapter operation. No action necessary.
AER3-000290 –NEW– WARN C No R/3 client configured for %1, usingdefault-client %2 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 –NEW– INFO AD Received request for logon to SAP R/3 System Indicates normal adapter operation. No action necessary.
AER3-000292 –NEW– INFO AD Successfully logged-on to SAP R/3 System Indicates normal adapter operation. No action necessary.
AER3-000293 –NEW– INFO AD Received request for logoff from SAP R/3 System Indicates normal adapter operation. No action necessary.
AER3-000294 –NEW– INFO AD Successfully logged-off from SAP R/3 System Indicates normal adapter operation. No action necessary.
AER3-000295 –NEW– Error AD No session id exists in the logoff request 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 –NEW– Error AD No logon session exists for the session ID 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 –NEW– INFO M Created discovery subscriber successfully using subject %1 Indicates normal adapter operation. No action necessary.
AER3-000301 –NEW– INFO M Attempting to create dynamic connection to SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000302 –NEW– INFO M Attempting to close dynamic connection from SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000303 –NEW– INFO M Retrieving list of function modules from SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000304 –NEW– INFO M Retrieving schema for IDoc %1 FROM SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000305 –NEW– INFO M Retrieving entries for table %1 FROM SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000306 –NEW– INFO M Retrieving schema for structure/table %1 FROM SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000307 -NEW– INFO M Received unknown operation %1 TIBCO Designer sent an invalid request to the design-time adapter. If problem persists contact technical support: support@tibco.com
AER3-000308 -NEW– INFO M Metadata adapter operation failure:%1; operation name : %2 Refer to the surrounding error messages for additional details.
AER3-000309 -NEW– INFO M Retrieving schema for RFC/BAPI %1 from SAP R/3 system Indicates normal adapter operation. No action necessary.
AER3-000310 -NEW– ERROR AD Received Error Advisory Message: %1, Subject: %2 This is an error advisory thrown by a TIBCO Infrastructure component. The message %1 is context-sensitive. Report the error to TIBCO Support.
AER3-000400 –NEW– INFO AD Invalid connection detected. Message : % Indicates normal adapter operation. No action necessary.
AER3-000401 –NEW– INFO AD %1 RFCServers registered with SAP R/3 system with program-id %2 on GatewayHost %3 Indicates normal adapter operation. No action necessary.
AER3-000402 –NEW– Error AD No session id in request for operation %1 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 –NEW– Error AD Unable to obtain context forimplementation of operation %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000405 –NEW– Error AD Invalid session id passed in request for operation %1 The sessionID should be a valid string.
AER3-000406 –NEW– Error AD Invalid session id passed for operation %1 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 –NEW– Error AD Invalid call received, connection closedfor thread 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 –NEW– Error AD Server thread unable to dispatch call, callskipped. message : %1 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 –NEW– Error AD Server thread unable to dispatch call, connection invalidated 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 –NEW– WARN AD Server thread exited, message : %1 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 –NEW– Error C No poolRef specified for operation %1 The RFC does not have a ‘poolRef’ attribute in its deployment description. Ensure that a valid ‘poolRef’ is specified for the RFC.
AER3-000412 –NEW– INFO AD Obtaining connection for R/3 client %1 for %2 Indicates normal adapter operation. No action necessary.
AER3-000413 –NEW– Error AD The session for commit/rollback timed out for operation %1 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 –NEW– INFO C No session timeout specified forcommit/rollback for operation %1,defaulting to %2 seconds… 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 –NEW– INFO AD Session timeout for commit/rollback for operation %1 set to %2 seconds Indicates normal adapter operation. No action necessary.
AER3-000417 –NEW– INFO AD Connection pending commit for operation %1 Indicates normal adapter operation. No action necessary.
AER3-000418 –NEW– Error AD Invalid client specified : %1 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 –NEW– INFO AD Created new thread for RFCServer Indicates normal adapter operation. No action necessary.
AER3-000420 –NEW– INFO AD Server thread(s) stopped for Component %1 Indicates normal adapter operation. No action necessary.
AER3-000421 –NEW– Error AD No valid connection handle available forserver for operation %1 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 –NEW– Error C No client specified in deploymentdescription for operation %1 Ensure that a client is configured for the operation
AER3-000423 –NEW– Error C No poolRef specified for operation %1 Ensure that a poolRef is specified for the operation
AER3-000424 –NEW– Error C No default client specified for operation %1 Ensure that a defaultClient is specified for the operation
AER3-000425 –NEW– Error C Invalid poolRef specified in deployment : %1 Ensure that a valid poolRef is specified in the deployment description for the RFC/IDoc
AER3-000426 –NEW– INFO AD Thread monitor started for %1 server thread(s) Indicates normal adapter operation. No action necessary.
AER3-000427 –NEW– Error AD No active connections available in configuration, exiting… 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 –NEW– WARN C Interface %1 does not contain deployment description for RFCs… continuing… The adapter could not find deployment descriptions for any RFC. If it is not intentional, ensure that the RFC configuration is correct.
AER3-000429 –NEW– WARN C No deployment description available for idoc %1…using default… The adapter could not find deployment descriptions for the specified IDoc. If it is not intentional, ensure that the IDoc configuration is correct.
AER3-000430 –NEW– INFO AD Total requests processed : %1 Indicates normal adapter operation. No action necessary.
AER3-000431 –NEW– Error AD Unable to create marshaller for operation %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000432 –NEW– Error AD Unable to clone proxy for operation %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000433 –NEW– Error AD Unable to clone RFC client for %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000434 –NEW– Error AD Unable to clone function implementation for operation %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000435 –NEW– Error AD Unable to create listener for call-operation Look at earlier error messages in the log-file(s) for possible causes.
AER3-000436 –NEW– Error AD Unable to create reply listener for operation %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000437 –NEW– Error AD Unable to clone subscriberimplementation Look at earlier error messages in the log-file(s) for possible causes.
AER3-000438 –NEW– Error AD Unable to generate transaction-id. message : %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000439 –NEW– Error AD Unable to create implementation for thread Look at earlier error messages in the log-file(s) for possible causes.
AER3-000440 –NEW– Error AD Unable to create server thread Look at earlier error messages in the log-file(s) for possible causes.
AER3-000441 –NEW– INFO C management is remote Look at earlier error messages in the log-file(s) for possible causes.
AER3-000442 –NEW– Error AD Connection context lost. Operation %1 failed Look at earlier error messages in the log-file(s) for possible causes.
AER3-000443 –NEW– Error AD Logon to SAP R/3 system failed.message : %1 Look at earlier error messages in the log-file(s) for possible causes.
AER3-000444 –NEW– Error AD Error writing to file for transaction %1 Ensure that the file has write permissions.
AER3-000446 –NEW– Error AD No active connections in connection-pool%1. All retry attempts exhausted.Connections for this pool deactivated. Ensure that the SAP system pointed to by the connection-pool %1 is up and running.
AER3-000447 –NEW– Error AD No active connections in connection-pool%1. All retry attempts exhausted.Exiting… 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-000448 –NEW– INFO AD Suspended endpoint component %1 None.
AER3-000449 –NEW– INFO AD The Application Manager has beenflagged to restart on re-establishingconnection to R/3. None.
AER3-000450 –NEW– INFO AD Created timer to check connectivity to R/3. None.
AER3-000451 –NEW– WARN AD Adapter application will restart now 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 –NEW– INFO AD Adapter application %1 is restarting on host %2. None.
AER3-000453 –NEW– WARN C Invalid control-field replacement attribute %1 skipped. 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 –NEW– INFO AD Performing oneway invocation for User-defined function: %1 None.
AER3-000455 –NEW– Error C No class description available for explode sequence %1 Check the repository under/tibco/public/adapter/SAPAdapter40/<sapversion>/IDOCS/ for the class description for class %1.
AER3-000456 –NEW– Error C No attribute description forexplode sequence %1 Check the repository for attribute description for explode sequence %1.
AER3-000457 –NEW– Error AD Operation %1 requires externallogon. The request does not contain sessionID in the closure data. Supply the session-id parameter in the RFCCLOSURE data of the incoming request.
AER3-000500 –NEW– WARN AD Unsupported datatype: class %1. Parameter: %2 This datatype is not supported.
AER3-000461 –NEW– Error AD Connection Error. Unable to create a connection with the target application %1 using connection parameters %2 and the target application error is %3 Ensure that valid connection parameters have been specified and that the SAP server is not down.
Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s