JCO-Java application unable to open a Frontend GUI session

[Former Member]

Hello,

<P>

I am having a problem opening a GUI session on a client PC through the JCo java call. It works on some PC's when I am logged in, but not on my PC. But other persons who login on my PC do not have a problem with the application opening a GUI session. I am at a loss. I have had a basis consultant look into this and he could not find a reason for the problem. I have submitted a customer message to SAP and am being told to file this issue in the forum, so here it is. If this is the wrong forum, please let me know which forum would be the correct one.

</P>

<P>

Problem:</br>

For test purposes, I have created a Java application using the SAP standalone SAPJCO3 vers. 3.0.1. The R/3 backend is 4.6C. The SAPGui version is 7.1 patch level 13 installed on a Windows XP Pro client PC. The application is supposed to start a Frontend GUI session as part of the initial process. This is not working on all PCu2019s for all users. The following are scenarios for two different users on two different PCu2019s, logged on and executing the Java application. The parameters for the Java application are: User, Password, and System Id in this order on the command line after the Java applicationu2019s name. The system Id in our example is PRP in uppercase. This problem happens while connecting to any of our R/3 instances.

</P>

<P>

Testing of the issue:</br>

Scenario 1:</br>

User gmcghie: This user is the primary user of his/her PC. This PC has not had its registry entries cleaned up for a long time. Starting the Java application from the Windows command line with the supplied parameters, the program is executed and makes the initial connection with the R/3 backend. When the R/3 system sends back a request to start the GUI session, the SAP Logon is executed and opens on the PC. Nothing seems to happen after this.

<P>

Here is the JCO exception from the log file:

JCoException eDest: (136)com.sap.conn.jco.JCoException: (136) JCO_ERROR_ILLEGAL_STATE: Launching SAP GUI failed, though it was requested (error message: Communication with SAPGUI timed out)

</P>

<P>

When you right click on the SAP Logon icon that is in the Windows System Tray on the PC you see an entry that shows a session for Client 000. This is the wrong client being called by the application. The client being called is 600 in this particular scenario.

</P>

<P>

Here is the connection string sent to backend for scenario 1:</br>

TYPE=A DEST=PRP USER="gmcghie" PASSWD=********** CLIENT=600 LANG=E ASHOST=10.212.120.53 SYSNR=00 TRACE=1 PCS=1 USE_SAPGUI=2

</P>

<P>

Scenario 2:</br>

User mshin: This user is the primary user of his/her PC. This PC has had the OS re-installed on it within the last few years, hence the registry is likely more clean. Starting the Java application from the Windows command line with the supplied parameters, the program is executed and makes the initial connection with the R/3 backend. When the R/3 system sends back a request to start the GUI session, the SAP Logon is executed and opens on the PC. The connection is made to Client 600 and the process ends. The screens that appear above for the other scenario are not present when the connection is successful. The log file is not included for this as it was empty because it succeeded.

</P>

<P>

Here is the connection string sent to backend for scenario 2:</br>

TYPE=A DEST=PRP USER="mshin" PASSWD=********** CLIENT=600 LANG=E ASHOST=10.212.120.53 SYSNR=00 TRACE=1 PCS=1 USE_SAPGUI=2

</P>

I have the same issue on my PC as the first scenario.

<P>The steps I took to try to get this to work are as follows.</br>

1. Un-installed and re-installed the SAPGui, several times with no change.</br>

2. Compared the registry settings of SAPGui between working and non-working PCu2019s. These were essentially the same.</br>

3. Compared the system variables between working and non-working PCu2019s. These were essentially the same.</P>

It should also be noted that if user u2018gmcghieu2019 from scenario #1 logs into another PC, the program executes correctly (for most other PCs but not all). Finally, if user u2018mshinu2019 from scenario #2 (certain other users as well) logs into Windows on the primary PC for user u2018gmcghieu2019 from scenario #1, and user u2018gmcghieu2019 is used to connect to SAP using the Java program, the program executes correctly. It seems that this would indicate some problem with the useru2019s Windows account on certain PCs.</P>

Why is the connection information being dropped? How is the process of opening the SAPGui on the frontend done?</P>

Any help with this issue is greatly appreciated.</P>

Thanks,</br>

Mark Shirkey

[Former Member]

Created Customer Message and got answer. There were settings in Windows Registry for starting the SAP Logon Launch Pad which had to have a value of 1.

[Former Member]

Created Customer Message and got answer.