Troubleshooting and support

Troubleshooting techniques and self-help information help you identify and solve problems quickly. This topic provides potential solutions for issues you would have with the SAP connector.

Getting EDI_DC40 IDOC control record structure with WebSphere Cast Iron SAP Connector

EDI_DC40 is a standard SAP structure used to store IDoc Control Record for Interface to External System information. With the SAP connector using non-Unicode SAP server as endpoint in WebSphere Cast Iron Studio version 7002 for the Receive IDoc and Send IDoc activities, supports Control record name as EDI_DC40.

Customer who are getting the EDI_DC as their standard structure name, are requested to use the latest version of 7501/7510 Studio and reconfigure the object in their orchestration and map it accordingly.

Older behavior:

With the Old Behavior for non-Unicode machine the control record name was EDI_DC instead of EDI_DC40.

-ALEREQ01 
|_SAPTransactorID 
|_qRECQueueName 
|_IDOC    
 |_@Begin    
 |_EDI_DC        
      |_@Segment        
      |_TABNAM        
      |_MANDT
………
………

New behavior:

With the new behavior for both Unicode and non-Unicode SAP server, the control record name will be EDI_DC40.

-ALEREQ01 
|_SAPTransactorID 
|_qRECQueueName 
|_IDOC    
 |_@Begin    
 |_EDI_DC40        
      |_@Segment        
      |_TABNAM        
      |_MANDT
………
………

Dependency JCo Jar files - Version Specific Information

Install and use the latest patch level of the SAP Java Connector 3.0. Latest version of JCo jar available: 3.0.14, IDoc version 3.0.12.

You need to have these 3 files: sapjco3.jar, sapjco3.dll (for Windows) or sapjco3.so (for Appliance), and sapidoc3.jar.

For downloading SAP JCo jar (2 files), follow these steps with specific to version:
  • Download latest the SAP Java Connector 3.0.14 from the SAP Service Marketplace at http://service.sap.com/connectors. You will find the download package with the latest patch level for various platform by navigating to SAP Java Connector > Tools & Services > Download SAP JCo Release 3.0. An installation guide is included in the download archive.
    • For Studio 32 bit Version, download the JCo jar zip file under Microsoft Windows and Windows Server > 32bit for 32 bit version of WebSphere Cast Iron Studio.
    • For Studio 64 bit Version, download the JCo jar zip file under Microsoft Windows and Windows Server > 64bit x86 for 64 bit version of WebSphere Cast Iron Studio.
    • For WebSphere Cast Iron Appliance, download the JCo jar zip file under Linux (for Intel compatible processors)> 64bit x86 for Appliance.
For downloading SAP IDoc jar (1 file), follow these steps with specific to version:
  • Download latest the SAP Java Connector 3.0.14 from the SAP Service Marketplace at http://service.sap.com/connectors. You will find the download package with the latest patch level for various platform by navigating to SAP Java Connector > Tools & Services > SAP Java IDoc Class Library.
    • For all platforms, SAP Java IDoc Class Library 3.0.12 zip file will contain the SAP IDoc jar file.

Exception thrown when trying to browse for IDoc/BAPI/RFC of an orchestration (new/existing) for 6.1.0.15 studio projects in later studio versions

Problem:

Null point exception is thrown when a 6.1.0.15 studio project is opened in any other later versions of studio and when a browse for IDoc/BAPI/RFC is done in a new or an existing orchestrations.

Error shown in studio error.log file:
WARNING: Unable to find entry: /.configuration-wizard -- err msg: Unable to locate  entry
      /.configuration-wizard java.util.concurrent.ExecutionException:
      java.lang.NullPointerException at
      java.util.concurrent.FutureTask.report(FutureTask.java:134) at
      java.util.concurrent.FutureTask.get(FutureTask.java:200) at
      com.approuter.studio.gui.FutureBusyView$1.run(FutureBusyView.java:72) at
      java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157) at
      java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627) at
      java.lang.Thread.run(Thread.java:798) Caused by: java.lang.NullPointerException at
      com.approuter.studio.connectors.sap.WSSapConnection.<init>(WSSapConnection.java:88) at
      com.approuter.studio.connectors.sap.endpoint.SapEndpointProjectNode$3.call(SapEndpointProjectNode.java:345)
      at
      com.approuter.studio.connectors.sap.endpoint.SapEndpointProjectNode$3.call(SapEndpointProjectNode.java:342)
      at java.util.concurrent.FutureTask.run(FutureTask.java:274)

Cause:

Enhanced authentication mechanisms in higher versions of Cast Iron Studio.

Solution:

After opening the project in later version of Studio, navigate to any of the respective Endpoints displayed on the right side of the project tab and come back to the Configure tab of the orchestration.

Now you are enabled with browsing for the IDoc/BAPI/RFC for that orchestration.

Supported formats of the date and time field values

The following table describes the supported formats of the date and time field values for all activities of the SAP connector:
Table 1. Formats for Date and Time field values
Field Input parameter (non-starter activities) Output parameter (starter and non-starter activities)
Date yyyy-mm-dd

or

yyyymmdd

 yyyymmdd
Time hh:mm:ss

or

hhmmss

 hhmmss

The supported formats for the input and output parameters of the date and time field values in the SAP connector version 6.0.x and earlier versions are: yyyy-mm-dd and hh:mm:ss, respectively.

Exception thrown when you deploy orchestrations with Receive RFC and Receive IDOC activities using the same RFC Program ID

Problem: When you deploy orchestrations with Receive RFC and Receive IDOC activities with the same SAP RFC Program ID, the following exception is thrown:

java.lang.RuntimeException: An attempt to start a JCoIDocServer failed. There might be an existing JCoServer with the same server configuration, else try restarting your server
at com.ibm.j2ca.sap.inbound.SapJCoServerBuilder.verfiyServerConfiguration(SapJCoServerBuilder.java:403)
at com.ibm.j2ca.sap.inbound.SapJCoServerBuilder.createServer(SapJCoServerBuilder.java:96)
at com.ibm.j2ca.sap.inbound.SAPEventListenerManager.buildEventListener(SAPEventListenerManager.java:149)
at com.ibm.j2ca.sap.inbound.SAPEventListenerManager.startEventListeners(SAPEventListenerManager.java:132)
at com.ibm.j2ca.sap.inbound.EndpointManager.addEndpoint(EndpointManager.java:68)
at com.ibm.j2ca.sap.SAPResourceAdapter.endpointActivation(SAPResourceAdapter.java:266)
at com.approuter.module.sap.activity.ReceiveIDOCActivity.activate(ReceiveIDOCActivity.java:222)
at com.approuter.maestro.activities.BaseModule.activate(BaseModule.java:296)
at com.approuter.maestro.vm.Program.start(Program.java:796)
at com.approuter.maestro.vm.Kernel.startOrchestration(Kernel.java:704)
at com.approuter.maestro.management.Loader$1.run(Loader.java:461)
at java.lang.Thread.run(Thread.java:736)

Cause: SAP JCo allows only one instance of JCoServer with a given set of server configuration to run within a Java virtual machine (JVM); another JCoServer with same server configuration cannot run in the same JVM. JCo throws an error indicating that the server cannot be restarted. The Receive IDOC activity and Receive RFC activity do not support the same SAP Program ID used during orchestration.

Solution: Ensure that you deploy orchestrations having Receive RFC and Receive IDOC activities using different SAP Program IDs, and create separate end points for IDOC/RFC.

Recommended configurations to avoid 'Maximum number of 202 conversations exceeded' error

When working with the SAP connector, the following are the recommended configurations to be done if the 'Maximum number of 202 conversations exceeded' error is displayed:

Error:

LOCATION   CPIC (TCP/IP) on local host with Unicode
ERROR      max no of 202 conversations exceeded
TIME       <Day> <Date> <Time> <Year>
RELEASE    720
COMPONENT  CPIC (TCP/IP) with Unicode

The following recommendations depend on the load and the number of parallel requests:

  1. Reduce the timeout value in the endpoint configuration so that the unused connections are terminated automatically.
  2. Configure Cast Iron runtime and SAP gateway to support more RFC connections.
    1. Set the environment value CPIC_MAX_CONV to >100 on Cast Iron runtime. Update maestro.sh to set the environment variable. The steps are described in Schedule A.
    2. Increase the profile value gw/max_conn and gw/max_sys on the SAP gateway to support many parallel connections. Also, if you run into memory bottlenecks increase the values of gw/max_overflow_size and gw/max_shm_req.
    3. Set maximum connections value in SAP endpoint to a realistic value. Depending on the load and parallel requests, appliance either generates or receives.
    4. Set the number of Server Instance value in SAP endpoint to 10.
  3. Sample Values:
    SAP-Gateway
gw/max_conn=2000, gw/max_sys=1200
gw/max_overflow_size =40000000, gw/max_shm_req = 200 (this is to adjust the memory allocation)
CPIC_MAX_CONV=5000

Schedule A:

  1. Log on into the appliance shell (contact IBM support to get appliance shell key in order to log on to the system shell).
  2. Go to the /usr/ironhide/bin folder. Take a back up of maestro.sh (copy maestro.sh to maestro.sh.old).
  3. Edit maestro.sh.
    move to line 
#  Version of java currently in use.
if [ -z $JAVA_HOME ]; then
  JAVA_HOME=/usr/java/default
fi
JAVA="${JAVA_HOME}/bin/java"
  4. Add the following line: 
    ## maximum SAP conversations allowed
export CPIC_MAX_CONV=500
  5. Save and exit.
  6. Exit system shell and run the command system restart in order to restart the appliance runtime.

Upgrading JRE from 32 bit to 64 bit

Problem: If you have an SAP project running on an earlier version of the appliance, when you upgrade the appliance to version 7.0 or later, the SAP projects will not start and the following errors occur:

  • Examples of errors thrown in WMC: 
    Start of Orchestration config-
url://SAP_BAPI/1.0/Default/Orchestrations/Orchestration failed:
java.lang.ExceptionInInitializerError: Error
getting the version of the native layer:
java.lang.UnsatisfiedLinkError: sapjco3
(/usr/ironhide/lib/thirdparty/libsapjco3.so:
wrong ELF class: ELFCLASS32).
    Required SAP JCO library is not found.
Install version 3.x SAP JCO library (.dll or .so based on platform)
  • Examples of exceptions recorded in the maestro.out log:
    java.lang.UnsatisfiedLinkError: sapjco3 (/usr/ironhide/lib/thirdparty/libsapjco3.so: wrong ELF class: ELFCLASS32)
	at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1030)
	at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:994)
	at java.lang.System.loadLibrary(System.java:507)
	at com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:481)
	at com.sap.conn.jco.rt.DefaultJCoRuntime.registerNativeMethods(DefaultJCoRuntime.java:347)
	at com.sap.conn.jco.rt.JCoRuntime.registerNatives(JCoRuntime.java:1108)
	at com.sap.conn.rfc.driver.CpicDriver.<clinit>(CpicDriver.java:954)
	at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at com.sap.conn.rfc.engine.DefaultRfcRuntime.getVersion(DefaultRfcRuntime.java:43)
	at com.sap.conn.rfc.api.RfcApi.RfcGetVersion(RfcApi.java:237)
	at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:215)
	at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:77)
	at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23)
	at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at com.sap.conn.jco.JCo.createJCo(JCo.java:52)
	at com.sap.conn.jco.JCo.<clinit>(JCo.java:26)
 at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at com.approuter.module.sap.SAPActivator.checkSAPInstalled(SAPActivator.java:101)
	at com.approuter.module.sap.activity.SAPBaseActivity.checkSapSetup(SAPBaseActivity.java:498)
	at com.approuter.module.sap.activity.SAPBaseActivity.generateSchemas(SAPBaseActivity.java:172)
	at com.approuter.module.sap.activity.SapSendRfcData.activate(SapSendRfcData.java:112)
	at com.approuter.maestro.activities.BaseModule.activate(BaseModule.java:301)
	at com.approuter.maestro.vm.Program.start(Program.java:768)
	at com.approuter.maestro.vm.Kernel.startOrchestration(Kernel.java:739)
	at com.approuter.maestro.management.Loader$1.run(Loader.java:455)
	at java.lang.Thread.run(Thread.java:738)
java.lang.ExceptionInInitializerError: Error getting the version of the native layer: java.lang.UnsatisfiedLinkError: sapjco3 (/usr/ironhide/lib/thirdparty/libsapjco3.so: wrong ELF class: ELFCLASS32)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:227)
 at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:77)
 at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23)
 at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at com.sap.conn.jco.JCo.createJCo(JCo.java:52)
 at com.sap.conn.jco.JCo.<clinit>(JCo.java:26)
at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at com.approuter.module.sap.SAPActivator.checkSAPInstalled(SAPActivator.java:101)
	at com.approuter.module.sap.activity.SAPBaseActivity.checkSapSetup(SAPBaseActivity.java:498)
	at com.approuter.module.sap.activity.SAPBaseActivity.generateSchemas(SAPBaseActivity.java:172)
	at com.approuter.module.sap.activity.SapSendRfcData.activate(SapSendRfcData.java:112)
	at com.approuter.maestro.activities.BaseModule.activate(BaseModule.java:301)
	at com.approuter.maestro.vm.Program.start(Program.java:768)
	at com.approuter.maestro.vm.Kernel.startOrchestration(Kernel.java:739)
	at com.approuter.maestro.management.Loader$1.run(Loader.java:455)
	at java.lang.Thread.run(Thread.java:738)
2013-08-22 09:18:25.013 SEVERE [T-10] [orc:SAP_BAPI/1.0/Default/Orchestrations/Orchestration] [com.approuter.module.common.util.LogHelper] Required SAP JCO native library is not found. Install version 3.x SAP JCO native library(.dll or .so based on platform).
java.lang.RuntimeException: java.lang.ExceptionInInitializerError: Error getting the version of the native layer: java.lang.UnsatisfiedLinkError: sapjco3 (/usr/ironhide/lib/thirdparty/libsapjco3.so: wrong ELF class: ELFCLASS32)
	at com.approuter.module.sap.activity.SAPBaseActivity.checkSapSetup(SAPBaseActivity.java:509)
	at com.approuter.module.sap.activity.SAPBaseActivity.generateSchemas(SAPBaseActivity.java:172)
	at com.approuter.module.sap.activity.SapSendRfcData.activate(SapSendRfcData.java:112)
	at com.approuter.maestro.activities.BaseModule.activate(BaseModule.java:301)
	at com.approuter.maestro.vm.Program.start(Program.java:768)
	at com.approuter.maestro.vm.Kernel.startOrchestration(Kernel.java:739)
	at com.approuter.maestro.management.Loader$1.run(Loader.java:455)
	at java.lang.Thread.run(Thread.java:738)
Caused by: java.lang.ExceptionInInitializerError: Error getting the version of the native layer: java.lang.UnsatisfiedLinkError: sapjco3 (/usr/ironhide/lib/thirdparty/libsapjco3.so: wrong ELF class: ELFCLASS32)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:227)
 at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:77)
 at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23)
 at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at com.sap.conn.jco.JCo.createJCo(JCo.java:52)
	at com.sap.conn.jco.JCo.<clinit>(JCo.java:26)
	at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at java.lang.Class.forNameImpl(Native Method)
	at java.lang.Class.forName(Class.java:182)
	at com.approuter.module.sap.SAPActivator.checkSAPInstalled(SAPActivator.java:101)
	at com.approuter.module.sap.activity.SAPBaseActivity.checkSapSetup(SAPBaseActivity.java:498)

Cause:

In the earlier versions of Cast Iron appliance (version 6.4 and earlier versions), 32 bit SAP JCo libraries were used. From Cast Iron appliance version 7.0 onwards, you must use the 64 bit SAP JCo libraries.

Solution:

You need to delete the 32 bit SAP JCo libraries, sapjco3.jar and libsapjco3.so, and load the 64 bit SAP JCo libraries.

Upgrading SAP JCo libraries:

In case of any issue after applying 64 bit JCo libraries, contact IBM Technical Support for further assistance.

Exception thrown when SAP server Host name is not correct

Problem: When SAP server Host Name is not correct, the below exception is thrown in JCo trace

Error: >Thu Jul 16 15:08:00,483< RfcException:
 Message: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=9.184.167.114|100|dev0028.492965 ASHOST=9.184.167.114 SYSNR=10 CODEPAGE=1100 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '9.184.167.114:3310' not reached
TIME Thu Jul 16 15:08:00 2015
RELEASE 721
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3283
DETAIL NiPConnect2:9.184.167.114:3310
SYSTEM CALL connect
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 2
 return code: RFC_FAILURE (1)
 error group: 102
 key: RFC_ERROR_COMMUNICATION

Exception thrown when SAP system number is not correct

Problem: When SAP system number is not correct, the below exception is thrown in JCO trace

Error: >Thu Jul 16 15:21:40,738< RfcException:
 message: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=9.184.167.115|100|dev0028.741310 ASHOST=9.184.167.115 SYSNR=15 CODEPAGE=1100 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '9.184.167.115:3315' not reached
TIME Thu Jul 16 15:21:40 2015
RELEASE 721
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3283
DETAIL NiPConnect2: 9.184.167.115:3315
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2
 return code: RFC_FAILURE (1)
 error group: 102
 key: RFC_ERROR_COMMUNICATION

Exception thrown when SAP client is not correct

Problem: When SAP client is not correct, the below exception is thrown

Error log shows as below:

Jul 16, 2015 3:25:21 PM com.ibm.j2ca.sap.SAPManagedConnection getJcoConnection
SEVERE: CWYAP1019E: An exception occurred while connecting to the SAP system. Error message: Initialization of destination 9.184.167.115|000|dev0028.145604 failed: Name or password is incorrect (repeat logon) on 9.184.167.115 sysnr 10 Explanation=An exception occurred while making the connection to the SAP application. The adapter cannot connect using the logon credentials that have been provided. UserAction=Refer to the exception message for more details.
Jul 16, 2015 3:25:21 PM com.approuter.studio.connectors.sap.endpoint.SapEndpointPanel testConnection2
SEVERE: Unable to connect to the endpoint. Please check the endpoint's information and try again. Detail: com.ibm.j2ca.base.exceptions.AuthenticationFailException: Initialization of destination 9.184.167.115|000|dev0028.145604 failed: Name or password is incorrect (repeat logon) on 9.184.167.115 sysnr 10

JCO trace shows as below:

<* RfcReceive >Thu Jul 16 15:25:21,155< failed *>
>>>> [1] <unknown> R/3 <ac: 6> >>> CLOSE (45412733)
RfcException raised by system [SD1|eccdev1]:
 message: Name or password is incorrect (repeat logon)
 return code: RFC_SYS_EXCEPTION (3)
 error group: 104
 key: RFC_ERROR_SYSTEM_FAILURE*> RfcReceive ... 
 handle = 1
 parameter = <null> 
 parameter = <null> 
 tables = <null>  
>>> RfcClose [1] >Thu Jul 16 15:25:21,158< ...

Exception thrown when SAP User Name is not correct

Problem: When SAP server user name is not correct, the below exception is thrown

Error log shows as below:

Jul 16, 2015 3:33:09 PM com.ibm.j2ca.sap.SAPManagedConnection getJcoConnection
SEVERE: CWYAP1019E: An exception occurred while connecting to the SAP system. Error message: Initialization of destination 9.184.167.115|100|cev0028.789483 failed: Name or password is incorrect (repeat logon) on 9.184.167.115 sysnr 10 Explanation=An exception occurred while making the connection to the SAP application. The adapter cannot connect using the logon credentials that have been provided. UserAction=Refer to the exception message for more details.
Jul 16, 2015 3:33:09 PM com.approuter.studio.connectors.sap.endpoint.SapEndpointPanel testConnection2
SEVERE: Unable to connect to the endpoint. Please check the endpoint's information and try again. Detail: com.ibm.j2ca.base.exceptions.AuthenticationFailException: Initialization of destination 9.184.167.115|100|cev0028.789483 failed: Name or password is incorrect (repeat logon) on 9.184.167.115 sysnr 10

JCO trace shows as below:

<* RfcReceive >Thu Jul 16 15:33:08,861< failed *>
>>>> [1] <unknown> R/3 <ac: 6> >>> CLOSE (45885421)
RfcException raised by system [SD1|eccdev1]:
 message: Name or password is incorrect (repeat logon)
 return code: RFC_SYS_EXCEPTION (3)
 error group: 104
 key: RFC_ERROR_SYSTEM_FAILURE*> RfcReceive ... 
 handle = 1
 parameter = <null> 
 parameter = <null> 
 tables = <null> 
>>> RfcClose [1] >Thu Jul 16 15:33:08,863< ...
<* RfcClose *>

Exception thrown when SAP Server Password is not correct

Problem: When SAP server password is not correct, the below exception is thrown

Error log shows as below:

Jul 16, 2015 3:40:13 PM com.ibm.j2ca.sap.SAPManagedConnection getJcoConnection
SEVERE: CWYAP1019E: An exception occurred while connecting to the SAP system. Error message: Initialization of destination 9.184.167.115|100|dev0028.879503 failed: Name or password is incorrect (repeat logon) on 9.184.167.115 sysnr 10 Explanation=An exception occurred while making the connection to the SAP application. The adapter cannot connect using the logon credentials that have been provided. UserAction=Refer to the exception message for more details.
Jul 16, 2015 3:40:13 PM com.approuter.studio.connectors.sap.endpoint.SapEndpointPanel testConnection2
SEVERE: Unable to connect to the endpoint. Please check the endpoint's information and try again. Detail: com.ibm.j2ca.base.exceptions.AuthenticationFailException: Initialization of destination 9.184.167.115|100|dev0028.879503 failed: Name or password is incorrect (repeat logon) on 9.184.167.115 sysnr 10

JCO trace shows as below:

>>>> [1] <unknown> R/3 <ac: 6> >>> CLOSE (46318530)
RfcException raised by system [SD1|eccdev1]:
 message: Name or password is incorrect (repeat logon)
 return code: RFC_SYS_EXCEPTION (3)
 error group: 104
 key: RFC_ERROR_SYSTEM_FAILURE*> RfcReceive ... 
 handle = 1
 parameter = <null> 
 parameter = <null> 
 tables = <null> 
 >>> RfcClose [1] >Thu Jul 16 15:40:13,842< ...
 <* RfcClose *>
Parent topic: SAP activities


Feedback | Notices


Timestamp icon Last updated: Wednesday, 15 June 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/SAP_troubleshooting.html