Alert Codes for Java CAPS Adapters

Chapter 1 Alert Codes for Java CAPS Adapters

The following sections provide information on Sun Adapter Alert Codes. If you have any questions or problems, see the Java CAPS web site at http://developers.sun.com/javacaps/

This chapter covers the following topics,

Alert Codes Overview

This book will present you with explanations to various Alert Codes that you may come across while installing a Sun Adapter.

Alert Codes Task Overview

This task allows you to To View the Sun Adapter Alert Codes.

Viewing Alert Codes

You can view and delete alerts using the Enterprise Manager. An alert is triggered when a specified condition occurs in a Project component. The purpose of the alert is to warn the administrator or user that a condition has occurred.

ProcedureTo View the Sun Adapter Alert Codes

  1. Add the adapter Enterprise Manager plug-in for this adapter.

  2. From the Enterprise Manager's Explorer tool-bar, click the Configuration icon.

  3. Click the Web Applications Manager tab and go to the Manage Alert Codestab. The installed alert codes are displayed under the Results section. If the adapter alert codes are not available displayed under Results, perform the following:

    1. From the Install New Alert Codes section, browse to and select the Adapter alert properties file for the application plug-in that you added. The alert properties files are located in the Alert Codes folder of the Sun Java Composite Application Platform Suite installation directory.

    2. Click Deploy. The available alert codes for the application will be displayed under Results.

Alert Codes for Application Adapters

The table briefly describes a complete list of Application Server Alert Codes.

Table 1–1 Application Server Adapter Alert Codes

Sun Adapter Name 

Alert Code 

Description 

User Action 

Oracle Applications 

DBCOMMON-CONNECTFAILED000001= Failed to connect to database {0} on host {1}. Reason: The Pooled connection could not be allocated: [{2}] 

Occurs during the initial database connection. 

  • Database is down; start the database.

  • External configuration information is invalid. Verify the following:

    • Server name

    • Database name

    • User name

    • Password

    • Port

DBCOMMON-CONNECTFAILED000002= Operation failed because of a database connection error. Reason: [{0}] 

Occurs while retrieving a connection from the database or the pool. 

Verify that the database has not been terminated with unexpected errors. 

DBCOMMON-CONNECTFAILED000005= Connection handle not usable. Reason:[{0}] 

The connection in the pool is stale and is not usable. 

Probably a database restart has occurred causing the connection to be stale, retry the operation after starting the database. 

DBCOMMON-XARESOURCEFAILED000001= Unable to get XAResource for the database. Reason: [{0}] 

Could not obtain XAResource for the connection. 

Check if the database supports XA and has been configured for Distributed Transactions. 

 

DBCOMMON-XACONNECTFAILED000001= Failed to connect to database {0} on host {1}. The XA connection could not be allocated: Reason [{2}] 

Occurs during the initial database connection. 

  • Check if the database is configured for XA and if the database is running.

  • External configuration information is invalid. You may need to verify the following:

    • Server name

    • Database name

    • User name

    • Password

    • Port

DBCOMMON-XASTARTFAILED000001= Unable to perform XAStart for the connection. Reason: [{0}] 

A connection error has occurred which caused XASTART to fail. 

Check if the database is running, and there are no network issues. 

DBCOMMON-XAENDFAILED000001= XAEnd failed. Reason: [{0}] 

Error occurred during commit on XA connection. 

Look for the detailed error mentioned in the alert for the appropriate action. 

 

DBCOMMON-CANNOT-GETISOLATION- LEVEL=Unable to get isolationLevel for the transaction. Reason: [{0}] 

Could not read transaction isolation information of the connection. 

Transaction isolation is one of the following constants: 

  • Connection.TRANSACTION_ READ_UNCOMMITTED

  • Connection.TRANSACTION_ READ_COMMITTED

  • Connection.TRANSACTION_ REPEATABLE_READ

  • Connection.TRANSACTION_ SERIALIZABLE

  • Connection.TRANSACTION_N ONE

PeopleSoft Server 

PSOFTHTTPSERVEREWAYREQUEST- FAILED000001 

Failed to process the POST or GET request. 

Message cannot be processed. Verify that the message content is compatible with PeopleSoft. 

PeopleSoft Client 

PSOFTHTTPCLIENTEWAYCONFIG- FAILED000001 

Configuration error encountered for Peoplesoft HTTP Client Adapter. 

Verify whether the adapter Environment configuration properties are valid. 

PSOFTHTTPCLIENTEWAYCONNECT- FAILED000002 

Failed to prepare the Peoplesoft HTTP Client agent for establishing the connection to the HTTP server. 

Verify whether the PeopleSoft server is running. 

PSOFTHTTPCLIENTEWAYPOST- FAILED000005 

Failed on HTTP POST request to URL {0}.  

  • Verify whether the Environment configuration properties are valid.

  • Verify that the PeopleSoft server is running.

SAP BAPI 

SAPBAPI-CONNECT-CLIENTFAILED000001= 

Alert to indicate that the SAP JCO client initialization has failed. 

The adapter is unable to connect to SAP. Make sure that the adapter is able to reach the SAP system. Also check the SAP BAPI External System values for the Outbound SAP BAPI Adapter. In addition, check the SAP trace logs. 

SAPBAPI-CONNECT-CLIENTSUCCEEDED000002= 

Alert to indicate that the SAP JCO client initialization has succeeded. 

None 

SAPBAPI-CONNECT-CLIENTUP000003= 

Alert to indicate that the SAP JCO client is alive and valid. 

If you are running in manual mode, and this is an unexpected state, check the collaboration configuration and verify all connect() calls; otherwise, this Alert is only for informational purpose. 

 

SAPBAPI-CONNECT-CLIENTDOWN000004= 

Alert to indicate that the SAP JCO client is disconnected. 

If you are running in manual mode, and this is an unexpected state, check the collaboration and verify all disconnect() calls; otherwise, this Alert is only for informational purpose. 

SAPBAPI-CONNECT-CLIENTRETRY000005= 

Alert to indicate that the SAP BAPI Adapter is unable to connect to SAP R/3 and is in retry mode. 

None 

SAPBAPI-TIDFILENOTAVAIL000006= 

Alert to indicate that the TID file is inaccessible. 

Check that the directory for the TID file exists and has write permission for the user. 

SAPBAPI-CONNECT-SERVERSTARTED000007= 

Alert to indicate that SAP JCO Server is registered with SAP R/ 3 and started. 

None 

SAPBAPI-CONNECT-SERVERSTARTED- ERROR000008= 

Alert to indicate that SAP JCO Server could not be registered with SAP R/3 and is not started. 

The adapter is unable to register with SAP as a server. Make sure that the adapter is able to reach the SAP system. Also check the SAP BAPI External System values for the Inbound SAP BAPI Adapter. In addition, check the SAP trace logs. 

SAPBAPI-CONNECT-SERVERSTOPPED000009= 

Alert to indicate that SAP JCO Server was successfully shutdown. 

None 

 

SAPBAPI-CONNECT-SERVERSTOPPED- ERROR000010= 

Alert to indicate that SAP JCO Server could not be properly shutdown. 

Check the domain server.log and the SAP trace logs for further information. 

SAPBAPI-RFCNOTPROCESSEDERROR000011= 

Alert to indicate that an incoming RFC Function was not processed due to a failure in the Collaboration or Business Process. 

Check the domain server.log for further information. 

Siebel EAI 

SIEBELEAIEWAY-LOGINFAILED000002= Failed to login to url {0} with user name {1}.  

Occurs when a login is attempted at an invalid URL or with an incorrect username or password.  

  • Verify that the URL is valid.

  • Verify that the username and password association is valid.

  • Access the Siebel server log for further information.

SIEBELEAIEWAY-LOGOFFFAILED000003= Failed to log off from Siebel server at url {0} with user name {1}. 

Occurs when a logoff is attempted. 

Access the Siebel server log for further information. 

SIEBELEAIEWAY-POSTFORMFAILED000001= Failed to post to url {0} with SWEExtSource {1}, SWEExtCmd {2}, and SWEExtData {3}. 

Occurs when a Siebel operation is not successful. 

Check the Siebel server log for further information. 

 

SIEBELEAIEWAY-REQFAIL001=An incoming request could not be processed. Event: [{0}] Detail: [{1} 

Occurs when a Siebel operation is not successful. 

Access the Siebel server log for further information. 

SIEBELEAIWAY-CONNECTFAILED000004= Failed to prepare Siebel EAI Client to establish connection to Siebel EAI server. 

Occurs during initial Siebel system connection establishment. 

  • Verify that the configuration parameters for the Siebel client are correct.

  • Verify that the Siebel server is running.

SIEBELEAIWAY-POSTFAILED000006= Failed to handle the Siebel EAI POST request to URL {0}. 

Occurs when a Siebel post operation is not successful. 

Read the response code in the collaboration and proceed accordingly. 

SIEBELEAIWAY-URLFAILED000005= Invalid Siebel URL specified {0}. 

Occurs when an invalid URL is entered. 

Verify that the URL is correct.  

SWIFT AG 

SAGEWAY-CONNECTFAILED000001=Failed to connect 

Failed to establish a SWIFTNet connection. 

Typically, detailed error information is placed in the Integration Server log, explaining the cause of failure and the corresponding required user actions. 

SAGEWAY-EXCHANGEFAILED000002= Failed to exchange message 

Failed to exchange message with SWIFT. 

Typically, detailed error information is placed in the Integration Server log, explaining the cause of failure and the corresponding required user actions. 

WebSphere MQ 

WEBSPHEREMQEWAY_CONNECT 

This is an informational alert that is posted when the adapter successfully connects to a queue manager in client connections mode. 

This is an informational alert that is posted when the adapter successfully connects to a queue manager in client connections mode. 

WEBSPHEREMQEWAY_CONNECT_BINDINGSC 

This is an informational alert that is posted when the adapter successfully connects to a queue manager in bindings connections mode. 

This alert does not indicate any malfunction. No user actions are necessary. 

WEBSPHEREMQEWAY_ CONNECT_FAILED_ BINDINGS 

This alert indicates that the adapter failed to connect to a queue manager in bindings mode.  

  • Verify that the adapter configuration has the correct connection parameters.

  • Verify that the network connectivity is valid.

  • Verify that the targeted WebSphere MQ application is running and has been configured correctly.

WEBSPHEREMQEWAY_ CONNECT_FAILED_ CLIENT 

This alert indicates that the adapter failed to connect to a queue manager in client mode. 

  • Verify that the adapter configuration has the correct connection parameters.

  • Verify that the network connectivity is valid.

  • Verify that the targeted WebSphere MQ application is running and configured correctly.

 

WEBSPHEREMQEWAY_ DISCONNECTA 

This alert indicates that the adapter has successfully disconnected with the targeted queue manager for one of the following reasons: 

  • The adapter is shutting down as initiated by the user or by a Collaboration.

  • The adapter is being shut down by another JavaCAP Suite subcomponent as the result of a Collaboration error.

This alert does not (necessarily) indicate any malfunction. Refer to the log file for more information. 

WEBSPHEREMQEWAY_RECEIVE_FAILED 

This alert is posted if the adapter operates in receive (inbound polling) mode, and fails to retrieve a message from a MQ queue when a message is expected, This is not a case in which the adapter fails to fetch a message from an empty queue. 

  • Verify the network connection.

  • Verify that the adapter parameters associated with message retrieval are correct.

  • The adapter has received a truncated message, and the adapter is configured to NOT accept truncated messages.

  • Check the targeted MQ queue or its queue manager for errors.

 

WEBSPHEREMQEWAY_RECEIVE_TRUNC 

This alert indicates that the adapter, operating in receive mode, has successfully retrieved a message from the queue, but the message is truncated. 

  • If the adapter is configured beforehand to accept truncated messages, this alert is a warning regarding the severity of message truncation.

  • If the adapter is configured to NOT accept truncated messages, and a truncated message is received, this alert is NOT posted; rather, the preceding alert is the one that is posted.

WEBSPHEREMQEWAY_RECONNECT_FAILED 

This alert is no longer posted by the product. This alert code is reserved for future enhancement. 

This alert is no longer posted by the product. 

Alert Codes for Communication Adapters

You can view alerts by using the Enterprise Manager. For details, refer To View the Sun Adapter Alert Codes.

Table 1–2 Communication Adapter Alert Codes

Sun Adapter Name 

Alert Code 

Description 

User Action 

Batch 

BATCH-FTP-EWAY-CONFIGFAILEDY 

Batch FTP Adapter configuration error, message=[{0}]. 

An error has occurred related to configuration. Check IS log for details. 

Parameter 0 - the error message. 

BATCH-FTP-EWAY-CONNACQUIRE- FAILED 

Batch FTP Adapter error when acquiring connection from pool, message=[{0}]. 

An error has occurred when looking up a connection from the connection pool. Check IS log for details. 

Parameter 0 – the error message. 

BATCH-FTP-EWAY-CONNINIT- FAILED 

Batch FTP Adapter connection initialization failed, message=[{0}]. 

An error has occurred when initializing a connection. Check IS log for details. 

Parameter 0 – the error message. 

BATCH-FTP-EWAYCONNECTION- FAILED 

Batch FTP Adapter connection failed, method=[{0}], message=[{1}]. 

An error has occurred when connecting to remote. Check IS log for details. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

BATCH-FTP-EWAY-ERROR 

Batch FTP Adapter error, message=[{0}]. 

An error has occurred. Check IS log for details. 

Parameter 0 — the error message. 

 

BATCH-FTP-EWAYOPERATION- ERROR 

Batch FTP Adapter error when doing data transfer operation in [{0}], message=[{1}]. 

An error has occurred when doing a data operation, such as put/get, and so on. 

  • Parameter 0 — the method in which the error occurred

  • Parameter 1 — the error message.

Check IS log for details.  

BATCH-INBOUND-EWAYCONFIG- FAILED 

Batch Inbound Adapter configuration error, message=[{0}]. 

An error has occurredrelated to configuration. Check IS log for details. 

Parameter 0 — the error message. 

BATCH-INBOUND-EWAYERROR 

Batch Inbound Adapter error, message=[{0}]. 

 

BATCH-INBOUND-EWAYRUNNING 

RUNNING Batch Inbound Adapter is running. 

Inbound Adapter is running. Check IS log for details  

BATCH-INBOUND-EWAYSTARTED 

Batch Inbound Adapter started.  

Inbound Adapter is running. Check IS log for details  

BATCH-INBOUND-EWAYSTOPPED 

STOPPED Batch Inbound Adapter is stopped. 

Batch Inbound Adapter is stopped. Check IS log for details, or restart the Batch Inbound Adapter. 

BATCH-INBOUND-EWAYSTOPPING 

STOPPING Batch Inbound Adapter is being stopped. 

Batch Inbound Adapter is stopping. Check IS log for details, or restart the Batch Inbound Adapter. 

BATCH-INBOUND-EWAYSUSPENDED 

SUSPENDED Batch Inbound Adapter is suspended. 

Batch Inbound Adapter is suspended. Check IS log for details, or restart the Batch Inbound Adapter. 

 

BATCH-INBOUND-EWAYSUSPENDING 

SUSPENDING Batch Inbound Adapter is suspending. 

Batch Inbound Adapter is suspending. Check IS log for details, or restart the Batch Inbound Adapter. 

BATCH-LOCALFILE-EWAYCONFIG- FAILED 

Batch Local File Adapter configuration error, message=[{0}]. 

An error has occurred related to configuration. Check IS log for details.  

Parameter 0 – the error message. 

BATCH-LOCALFILE-EWAYCONN- ACQUIRE-FAILED 

Batch Local File Adapter error when acquiring connection from pool, message=[{0}]. 

An error has occurred when looking up a connection from connection pool. Check IS log for details. 

Parameter 0 – the error message. 

BATCH-LOCALFILE-EWAYCONN- INIT-FAILED 

Batch Local File Adapter connection initialization failed, message=[{0}]. 

An error has occurred when initializing connection. Check IS log for details. 


Note –

A connection object for local file is only an object pooled in the connection pool. It does not physically connect to any host.


Parameter 0 – the error message. 

BATCH-LOCALFILE-EWAYERROR 

Batch Local File Adapter error, message=[{0}].  

A general error occurred. Check IS log for details.  

Parameter 0 – the error message. 

 

BATCH-LOCALFILE-EWAYOPERATION- ERROR 

Batch Local File Adapter error when doing file operation in [{0}], message=[{1}]. 

An error has occurred when doing local file operations, such as put/get. Check IS log for details. 

  • Parameter 0 — the method in which the error occurred

  • Parameter 1 — the error message.

BATCH-REC-EWAY-CONFIGFAILED 

Batch Record Adapter configuration error, message=[{0}]. 

An error has occurred related to configuration. Check IS log for details. 

Parameter 0 – the error message. 

BATCH-REC-EWAY-CONNACQUIRE- FAILED 

Batch Record Adapter error when acquiring connection from pool, message=[{0}]. 

An error has occurred when looking up a connection from connection pool. Check IS log for details. 

Parameter 0 – the error message. 

BATCH-REC-EWAY-CONNINIT- FAILED 

Batch Record Adapter connection initialization failed, message=[{0}]. 

An error has occurred when initializing connection. Check IS log for details. 

Note, a connection object for batch record is only an object pooled in the connection pool, it does not physically connect to any host. 

Parameter 0 – the error message. 

BATCH-REC-EWAY-ERROR 

Batch Record Adapter error, message=[{0}]. 

A general error occurred. Check IS log for details. 

Parameter 0 – the error message. 

 

BATCH-REC-EWAYOPERATION- ERROR 

Batch Record Adapter error when doing record operation in [{0}], message=[{1}]. 

An error has occurred when doing a record operation, such as put/get, and so on. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

Check IS log for details.  

FTP-SSL-EWAY-CONFIGFAILED 

Batch FTP Over SSL Adapter configuration error, message=[{0}]. 

An error has occurred related to the configuration. Check IS log for details. 

Parameter 0 – the error message. 

FTP-SSL-EWAY-CONNACQUIRE- FAILED 

Batch FTP Over SSL Adapter error when acquiring connection from connection pool, message=[{0}]. 

Error when looking up a connection from connection pool. Check IS log for details. 

Parameter 0 – the error message. 

FTP-SSL-EWAY-CONN-INITFAILED 

Batch FTP Over SSL Adapter connection initialization error, message=[{0}]. 

Error when initializing a connection. Check IS log for details. 

Parameter 0 – the error message. 

FTP-SSL-EWAYCONNECTION- FAILED 

Batch FTP Over SSL Adapter connection failed, method=[{0}], message=[{1}]. 

An error has occurred when connecting to the remote server. Check IS log for details. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

FTP-SSL-EWAY-ERROR 

Batch FTP Over SSL Adapter error, message=[{0}]. 

General error occurred. Check IS log for details. 

Parameter 0 – the error message. 

 

FTP-SSL-EWAY-OPERATIONERROR 

Batch FTP Over SSL Adapter error when doing data transfer operation in [{0}], message=[{1}]. 

An error has occurred when doing a data operation, such as put/get, and so on. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

Check IS log for details.  

SCP-EWAY-CONFIG-FAILED 

Batch SCP Adapter configuration error, message=[{0}]. 

Error occurred related to the configuration. Check IS log for details. 

Parameter 0 — the error message. 

SCP-EWAY-CONNACQUIRE- FAILED 

Batch SCP Adapter error when acquiring connection from connection pool, message=[{0}]. 

Error when looking up a connection from connection pool. Check IS log for details. 

Parameter 0 — the error message. 

SCP-EWAY-CONN-INITFAILED 

Batch SCP Adapter connection initialization error, message=[{0}]. 

Error when initializing a connection. Check IS log for details. 

Parameter 0 — the error message. 

SCP-EWAY-CONNECTIONFAILED 

Batch SCP Adapter connection failed, method=[{0}], message=[{1}]. 

Error when connecting to remote. Check IS log for details. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

SCP-EWAY-ERROR 

Batch SCP Adapter error, message=[{0}]. 

General error occurred. Check IS log for details. 

Parameter 0 — the error message. 

 

SCP-EWAY-OPERATIONERROR 

Batch SCP Adapter error when doing data transfer operation in [{0}], message=[{1}]. 

An error has occurred when doing a data operation, such as put/get, and so on. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

Check IS log for details. 

SFTP-EWAY-CONFIG-FAILED 

Batch SFTP Adapter configuration error, message=[{0}]. 

An error has occurred related to the configuration. Check IS log for details. 

Parameter 0 — the error message. 

SFTP-EWAY-CONNACQUIRE- FAILED 

Batch SFTP Adapter error when acquiring connection from connection pool, message=[{0}]. 

An error has occurred when looking up a connection from connection pool. Check IS log for details. 

Parameter 0 — the error message. 

SFTP-EWAY-CONN-INIT-FAILED 

Batch SFTP Adapter connection initialization error, message=[{0}]. 

An error has occurred when initializing a connection. Check IS log for details. 

Parameter 0 - the error message. 

SFTP-EWAY-CONNECTIONFAILED 

Batch SFTP Adapter connection failed, method=[{0}], message=[{1}]. 

An error has occurred when connecting to the remote. Check IS log for details. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

SFTP-EWAY-ERROR 

Batch SFTP Adapter error, message=[{0}]. 

A general error occurred. Check IS log for details.  

 

SFTP-EWAY-OPERATIONERROR 

Batch SFTP Adapter error when doing data transfer operation in [{0}], message=[{1}]. 

An error has occurred when doing a data operation, such as put/get, and so on. 

  • Parameter 0 — the method in which the error occurred.

  • Parameter 1 — the error message.

Check IS log for details. 

CICS 

CICSCLIENTCLIENTEWAYCONNECT- FAILED000002 

Failed to connect to CICS. 

  • CICS is down. Verify that the system you are connecting to is running.

  • Properties are incorrect. Verify that the parameters are correct (host name, port, and so forth).

  • CTG configuration is incorrect. Verify CTG installation and configuration is correct.

Refer to the log for more information. 

COM/DCOM 

COMCREATECOMOBECTJFAILED00 0003 

Failed to create COM object instance with CLSID {0} 

The alert my be caused by one of the following, 

COM Server may not be installed. Verify whether the COM server is running. Verify that parameters are correct. 

 

COMNOMOREACCESSHANDLES00 0002 

No more concurrent access handles available 

Insufficient resources to run Collaboration. 

  • Consider load-balancing by deploying you Project on multiple hosts.

  • Try re-deploying the Project.

  • Verify that the configuration parameters are valid.

COMUNABLETOGETCOMRUNTIME000001 

Failed acquire COM runtime environment 

The Runtime JNI and DLL may not be available. Verify that Runtime JNI and DLL are installed in the correct directory. 

COM -UNKNOWNAPPNAME 000004 

Unrecognized application name {0} 

This alert code is reserved for future enhancement. 

E-mail 

EMAILEWAYCHECKEMAILFAILED000004 

Failed to check for available E-mail messages; host is {0}, using {1} port {2}. 

Some component of the E-mail is not supported by the E-mail Adapter. E-mail message could not be parsed. Refer to the log for more information. 

 

EMAILEWAY-CONNECTFAILED000001 

Failed to connect to host {0} on port {1} as user {2}. 

  • E-mail server is not available. Verify that the E-mail server is running and that you are able to connect to the server.

  • Parameters are not configured properly. Verify that the E-mail Adapter property values are configured correctly.

Refer to the log for more information. 

EMAILEWAY-RECVFAILED000003 

Failed to receive E-mail message; host is {0}, using {1} port {2}. 

Parameters are not configured properly. Verify that the E-mail Adapter property values are configured correctly. Refer to the log for more information. 

EMAILEWAY-SENDFAILED000002 

Failed to send E-mail message; host is {0}, using smtp port {1}. 

Parameters are not configured properly. Verify that the E-mail Adapter property values are configured correctly. Refer to the log for more information. 

File 

FILEASCANTCREATEINPUTDIR000004 

Unable to create input directory {0} 

Make sure that the user has permissions to create the directory. 

FILEASINPUTDIRNONEXISTENT000002 

Input directory {0} does not exist. Creating the directory. This is a warning. 

Verify that the input directory is named correctly. The directory may not have the expected name. Check for spelling mistakes. 

FILE-ASINPUTDIRNOTDIR000003 

Input directory {0} is not a directory 

The directory name may be an existing filename. Verify that the directory name is not the same as an existing file name. 

FILE-ASRENAMEFAILED000001 

Failed attempting to rename input file {0} 

  • Verify that the file permissions for the input file are not readonly.

  • If this occurs when renaming a file to text in the adapter, make sure that a file with this name does not already exist. For example, if you are renaming the input1.txt file to input1.txt.~in, and an ~in file already exists, the rename will fail.

FILECANTWRITEOUTPUTDIR000005 

Error writing to output directory {0} 

  • Verify that the output directory exists.

  • Verify that the output directory has write permissions.

  • Make sure that there is enough disk space to write to the disk.

 

FILECANTWRITEOUTPUTFILE000006 

Error writing to output directory {0} 

  • Verify that the output directory exists.

  • Verify that the output directory has write permissions.

  • Make sure that there is enough disk space to write to the disk.

HTTPS 

HTTPCLIENTEWAY-CONFIGFAILED000001= Configuration error encountered for HTTP Client Adapter. 

Occurs if there the project deployment parameters are invalid. 

Connectivity Map and External configuration information is invalid. Verify configured parameters. 

HTTPCLIENTEWAY-CONNECTFAILED000002= Failed to prepare the HTTP Client agent for establishing the connection to the HTTP server. 

Occurs when a socket connection does not exist. 

Verify that network connectivity is available. 

HTTPCLIENTEWAY-GETFAILED000004= Failed on HTTP GET request to URL {0}. 

Occurs when an HTTPS operation is not successful. 

  • Read the response code in the collaboration and proceed accordingly.

  • Run the operation from a web browser.

 

HTTPCLIENTEWAY-POSTFAILED000005= Failed on HTTP POST request to URL {0}. 

Occurs when an HTTPS operation is not successful. 

  • Read the response code in the collaboration and proceed accordingly.

  • Run the operation from a web browser.

HTTPCLIENTEWAY-URLFAILED000003= Invalid URL specified {0}. 

Occurs when an invalid URL is entered. 

Verify that the URL is correct.  

HTTPSERVEREWAY-REQUESTFAILED000001= Failed to process the POST or GET request. 

Occurs when an HTTPS operation is not successful. 

  • Read the response code in the collaboration and proceed accordingly.

  • Verify that the HTTP Server is running.

IMS 

IMSCLIENTEWAY-CONNECT -FAILED000002 

Failed to connect to IMS. 

  • IMS is down. Verify that the system you are connecting to is running.

  • Properties are incorrect. Verify that the parameters are correct (host name, port, and so forth).

  • CTG configuration is incorrect. Verify CTG installation and configuration is correct.

LDAP 

LDAPCONNECTIONFAILED= Failed to establish connection to the LDAP server on server. 

Unable to establish a connection to the LDAP server. You have reached the maximum connection retry limit.  

  • LDAP server is down; start the server.

  • External configuration information is invalid. You may need to verify the following :

    • Authentication

    • Credentials

    • Principal

    • Provider URL

LDAPDISCONNECTIONFAILED= Failed to disconnect from the LDAP server 

Unable to close the external system connector and release resources. 

LDAP server is down; start the server. 

LDAP-CLEANUPFAILED=Failed to clean up LDAP Adapter connection handler. 

Failed to clean up any resources or reset any state held by the LDAP Adapter Connection instance. 

Contact Support. 

LDAP-INITIALIZEFAILED=Failed to initialize the LDAP adapter connection. 

Unable to initialize a connection to the LDAP server. 

This is a general exception when a connection to the LDAP server has failed to initialize. You may need to verify the following :  

  • Connection Retry

  • Connection Retry Interval

  • Number of Retries

  • External configuration information (Authentication, Credentials, Principal, and Provider URL)

MSMQ 

MSMQ-CLOSEQUEUEFAILED 

Failed to close the MSMQ Queue. 

  • Restart MSMQ.

  • Refer to the alert details and server log file for more details.

MSMQ-CONNECTIONFAILED 

Failed to establish connection to the MSMQ server. 

  • Verify the adapter configuration properties.

  • Verify that the MSMQ server is running.

MSMQ-DISCONNECTIONFAILED 

Failed to disconnect from MSMQ server: {0}. 

  • Restart MSMQ.

  • Refer to the alert details and server log file for more details.

MSMQ-OPENQUEUEFAILED 

Failed to open the MSMQ Queue: {0}. 

  • Verify the adapter configuration properties.

  • Verify that the MSMQ server is running.

MSMQ-RECEIVEMESSAGEFAILED 

Failed to receive the message from MSMQ Queue: {0}. 

  • Verify that the MSMQ server and MSMQ service is running.

  • Refer to the alert details and server log for the MSMQ API error code.

MSMQ-SENDMESSAGEFAILED 

Failed to send message to MSMQ Queue: {0}. 

  • Verify that the MSMQ server and MSMQ service is running.

  • Refer to the alert details and server log for the MSMQ API error code.

 

MSMQ-GETMESSAGEFAILED 

Failed to send the message to MSMQ Queue: {0}. 

  • Verify that the MSMQ server and MSMQ service is running.

  • Refer to the alert details and server log for the MSMQ API error code.

MSMQEWAY-SUSPENDED 

MSMQ Adapter is suspended. 

Adapter is no longer running. Restart the adapter. 

SNA 

SNALU62–CONNECTFAILED000001=Failed to connect. 

Occurs during the initial system connection establishment. 

  • System is down; start the system.

  • External configuration information may be invalid. You may need to verify the configured parameters.

Refer to the server log for further information. 

SNALU62–RECEIVE-FAILED000003=Failed to receive message.= 

Occurs when a collaboration attempts to receive a message, and no message is available to be received. 

  • Verify that a message is available to be received.

  • External configuration information may be invalid. You may need to verify the configured parameters.

  • Verify the connection logic.

 

SNALU62-SENDFAILED000002= Failed to send message.= 

Occurs when a destination is not ready to receive a message. 

  • There is a collaboration error. Verify the collaboration design is valid.

  • External configuration information may be invalid. You may need to verify the configured parameters.

TCP/IP and HL7  

TCPIPBASE-CONNECT-FAILED000001  

Failed to connect. 

  • An error has occurred when connecting to remote server. Check server log for details.

  • An error has occurred when TCP/IP server tried to bind to a configured port. Make sure that the configured port is not in use.

TCPIPBASE-CONNECT-ESTABLISHED000004  

Connection established.  

Not applicable 

TCPIPBASE-CONNECT-CLOSED000005  

Connection closed 

Not applicable 

TCPIPBASE_SERVER_IDLE_TIMEOUT_EXPIRED000008 

No messages were received from the HL7 client within the configured idle timeout period. Connection terminated. 

Verify that the HL7 client is running, and that the connection is valid. Restart the connection. You can also increase the idle timeout period in the Adapter's Connectivity Map properties. 

Alert Codes for Database Adapters

You can view alerts by using the Enterprise Manager. For details, refer To View the Sun Adapter Alert Codes.

Table 1–3 Database Adapter Alert Codes

Sun Adapter Name 

Alert Code 

Description 

User Action 

Database Adapters 

  • DB2 Connect

  • DB2 Universal

  • Informix

  • JDBC/ODBC

  • Oracle

  • SQL Server

  • Sybase

  • VSAM

DBCOMMON-CONNECTFAILED000001= Failed to connect to database {0} on host {1}. Reason: The Pooled connection could not be allocated: [{2}] 

Occurs during the initial database connection. 

  • Database is down; start the database.

  • External configuration information is invalid. You may need to verify the following:

    • Server name

    • Database name

    • User

    • Password

    • Port

DBCOMMON-CONNECTFAILED000002= Operation failed because of a database connection error. Reason: [{0}] 

Occurs while retrieving a connection from the database or the pool. 

Verify that the database has not terminated with unexpected errors. 

DBCOMMON-CONNECTFAILED000002= Operation failed because of a database connection error. Reason: [{0}] 

Occurs while retrieving a connection from the database or the pool. 

Verify that the database has not terminated with unexpected errors. 

DBCOMMON-CONNECTFAILED000003= Connection handle not usable. Reason:[{0}] 

The connection in the pool is stale and is not usable. 

Probably a database restart occurred causing the connection to be stale, retry the operation after the database is up. 

DBCOMMON-XARESOURCEFAILED000001= Unable to get XAResource for the database. Reason: [{0}] 

Could not obtain XAResource for the connection. 

Check if the database supports XA and has been configured for Distributed Transactions. 

 

DBCOMMON-XACONNECTFAILED000001= Failed to connect to database {0} on host {1}. The XA connection could not be allocated: Reason [{2}] 

Occurs during the initial database connection. 

  • DCheck if the database is configured for XA and if the database is running.

  • External configuration information is invalid. You may need to verify the following:

    • Server name

    • Database name

    • User

    • Password

    • Port

DBCOMMON-XASTARTFAILED000001= Unable to perform XAStart for the connection. Reason: [{0}] 

A connection error has occurred which caused XASTART to fail. 

Check if the database is running, and that there are no network issues. 

DBCOMMON-XAENDFAILED000001= XAEnd failed. Reason: [{0}] 

Error has occurred during a commit on XA connection. 

Look for the detailed error mentioned in the alert for the appropriate action. 

DBCOMMON-CANNOT-GETISOLATION- LEVEL=Unable to get isolationLevel for the transaction. Reason: [{0}] 

Could not read transaction isolation information of the connection. 

Transaction isolation is one of the following constants: 

  • Connection.TRANSACTION_RE AD_UNCOMMITTED

  • Connection.TRANSACTION_RE AD_COMMITTED

  • Connection.TRANSACTION_RE PEATABLE_READ

  • Connection.TRANSACTION_SE RIALIZABLE

  • Connection.TRANSACTION_N ONE


Note –

Confirm with the vendor that the getIsolation() method of the connection is implemented correctly.


Alert Codes for Web Adapters

You can view alerts by using the Enterprise Manager. For details, refer To View the Sun Adapter Alert Codes.

Table 1–4 Alert Codes for Web Adapters

Sun Adapter Name 

Alert Code 

Description 

User Action 

 

  • Sun Java System Application Server

  • WebLogic

EJB-ERRORENCOUNTERED000001 

Error encountered in EJB Adapter. Check debug logs for details. 

An error has occurred, such as 

  • EJB has not been deployed.

  • Configuration properties are not correct.

  • JNDI name is invalid.

  • OTD uses an incompatible version of the EJB.

Refer to the log for more information.