XI RFC call failing

Hello,
   I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
   I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
   In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
   Does anyone have any idea why this is so?
Thanks,
Murtaza.
Message was edited by:
        Murtaza Madraswala

Hi Amitabha,
   I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
Time Stamp Status Description
2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-06-18 15:17:54 Success Message successfully put into the queue.
2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
2007-06-18 15:17:54 Success The message status set to DLNG.
2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
2007-06-18 15:17:54 Success MP: entering
2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
2007-06-18 15:17:55 Success MP: leaving
2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
2007-06-18 15:17:55 Success The message status set to DLVD.
   The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
   I appreciate your help. Please let me know if you have any clues.
Thanks,
Murtaza.

Similar Messages

RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABH

Hi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart

First RFC call failed, config not loaded. Check the System landscape configuration.

Dear Experts,
We are getting below error on portal while using the BEX query in BI system.
Error:
BEx Web Application
Error: First RFC call failed, config not loaded. Check the System landscape configuration.
Exception occurred while processing the current request; this exception cannot be handled by the application or framework
Failed to process request; contact your system administrator
To facilitate analysis of the problem, keep a copy of this error page
We are sorry for the inconvenience.
As the ITS & WEB AS connection tests go successful on object created for BI system in portal.
Kindly suggest me on this issue..
Thanks,
Bharath.

Hi Bharath,
Please go through the below SAP Note and let me know if this helps.
1903392 - Error: First RFC call failed, config not loaded
BR,
Anurag

RFC call failed : Error when opening an RFC connection

Hi,
As a result of "Start Data Collection" operation in the t-code RZ70, I have got this error.
"RFC call failed : Error when opening an RFC connection"
Others things are with success message.
Regards,
Bala Raja

hi
check this links
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
also check Tcode: SLDAPICUST.
run tcode SLDCHECK? any error?
Thanks
Rodrigo
PS: If useful reward points

RFC call failing due to UNICODE implementation

Hi
We are trying to connect to a SAP system using the JCO (SAP-JAVA Connectivity). We are passing the user name as an input parameter and in turn the SAP system send back the no. of item (ABAP Type integer) pending for the user name to the java and its inserted/updated in Oracle DB (which does accept the unicode characters).
It was all wokring fine untill the SAP system has been migrated to Unicode upgrade. Now the RFC call is getting failed from our system. On analysis we found with debug, that the user name is not getting accepted by the SAP system and throwing the error -says Exception in thread "main" com.sap.aii.proxy.framework.core.BaseProxyException: Conversion error between two character sets., error key: RFC_ERROR_SYSTEM_FAILURE and at the SAP end the error says "Conversion of "UNAME" from code page 4103 to 4102 is failed". The unicode change in SAP system cannot be reverted back due to some constraints.
Can you please help, how can we pass the user name as encoded in character set 4102 or any other solution so that it can be accepted by SAP and run the Function module and return the data.
Many Thanks
Snehil Joshi

Check RFC destination in Tx SM59. You must have one tab for unicode settings.
Regards.

RFC Call failing at SAP because of output schema (Response) sent from Biztalk

Hi,
I have deployed the Request/Response message with SAP. Getting RFC Request from SAP in a Request-Response Port. After processing the message, sending it throght same port.
At SAP side the reponse got failed for below error:
Action in response message is
http://Microsoft.LobServices.Sap/2007/03/Rfc/Z_TEST_RFCResponse. Expected Action is
http://Microsoft.LobServices.Sap/2007/03/Rfc/Z_TEST_RFC/response.
I checked my schema file (created by Consume Adapter Services ), there it shows action as
http://Microsoft.LobServices.Sap/2007/03/Rfc/Z_TEST_RFC/response. But still why it is passing RFCResponse at SAP end?
Thanks, Girish R. Patil.

Hello Girish,
Since you are using receive request-response port, it is not possible to mention the action in physical port,
So, You need to assign the Action in Orchestration...For that you use the message assignment shape...inside it write the following code...this will work...!
Response(WCF.Action) = "http://Microsoft.LobServices.Sap/2007/03/Rfc/Z_TEST_RFC/response";
Where Response is name of the response message...!
Regards,
Naveen.

RFC call fails while implementing Inovis EDI. ' NO AUTORITY FOR CONNECTION

Hi All,
We are implementing 'Inovis's' EDI solution. I have narrowed done the error to note 618941. It is telling me to modify the SEC file to allow a RFC_REMOTE_EXEC call.The SEC file came down in the form of a physical file. So I am really not sure what to do here. I don't know where this file should reside. Any ideas?
Thanks!!
Diana

I figured it out. Thanks.

UPGRADE : RFC call to subst_save_upgeval_db failed with key UPDATE_ERROR

Hello.
We are upgrading our NW 7.01 to NW 7.3 ABAP.
In Postprocessing phase MAIN_POSTP/CREATE_UPGEVAL we encounter the following error:
ERROR: RFC of "subst_save_upgeval_db" failed
key: ERROR UPDATE
message: EXCEPTION UPDATE_ERROR RAISED
Here is the troubleshooting ticket:
This trouble ticket was created by SAPup on 20111125120155
SAPup broke during phase CREATE_UPGEVAL in module MAIN_POSTP / Post Processing
Error Message: RFC call to subst_save_upgeval_db failed with key UPDATE_ERROR (UPDATE_ERROR): EXCEPTION UPDATE_ERROR RAISED
Summary of SAPup:
SAPehpi Release:        lmt_002
SAPehpi Version:        SAPup release lmt_002 version 41.001
Start Release:          701
Target Release:         730
Summary of host system details:
SID:                    TA1
Host:                   sapta1
MS Host:                sapta1
GW Host:                sapta1
Start Path:             /usr/sap/TA1/DVEBMGS02/exe
Kernel Path:            /usr/sap/TA1/DVEBMGS02/exe
Summary of operating system details:
OS Type:                Linux X86_64
OS Version:             2.5
Summary of database details:
Database Type:          ora
Database Version:       11.2.0.2.0
Summary of RFC details:
Host:                   sapta1
GW Host:                sapta1
Client:                 000
Destination:            TA1
Language:
System No.:             02
here is the PHASES.LOG:
1 ETQ201 Entering upgrade-phase "CREATE_UPGEVAL" ("20111125120352")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSR3
4 ETQ399   auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_POSTP/CREATE_UPGEVAL'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'STORE_DB'
4 ETQ359 RFC Login to: System="TA1", Nr="02", GwHost="sapta1", GwService="sapgw02"
4 ETQ232 RFC Login succeeded
Do you have anu ideas ?

Here is the dev_rd log:
Fri Nov 25 14:07:04 2011
***LOG S23=> GwIDisconnectClient, client disconnected (020) [gwxxrd.c     10423]
***LOG S74=> GwIDisconnectClient, client disconnected ( sapta1) [gwxxrd.c     10434]
***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c     10451]
***LOG S0I=> GwIDisconnectClient, client disconnected ( SAPCPIC) [gwxxrd.c     10464]
LOCATION    SAP-Gateway on host sapta1.sap.fr.alten.com / sapgw02
ERROR       connection to partner 'localhost.localdomain:0' broken
TIME        Fri Nov 25 14:07:04 2011
RELEASE     720
COMPONENT   NI (network interface)
VERSION     40
RC          -6
MODULE      nixxi.cpp
LINE        4850
DETAIL      NiIRead: 127.0.0.1:0
SYSTEM CALL recv
COUNTER     58

RFC call to spda_get_stack_info failed.

Hi All,
When carry out the system upgrade from 47x200 to 701 EHP4 SR1,
has a error in get stack info in the preparation step.
From windows 2003 x32 MSsql 2000 upgrade to windows 2008 R2 and MS sql 2008 R2.
Error message set: 'RFC call to spda_get_stack_info failed with key
RFC_ERROR_SYSTEM_FAILURE (SYSTEM_FAILURE): Error ST_MATCH_FAIL occured.
P1=element-start P2=sp-stacks P3= P4=element-start P5=SMSDXML P6='
Thanks.

Hello,
this error is happening because you're using an old version of SAPup and/or an old version of the Upgrade FIX file. Please make sure you're running the very last version of these files and repeat the process from the beggining.
Also the file ../EPS/in/SMSDXML.xml is actually not the XML file you want to use, it is a for R/3 release with
SAP_BASIS 4.x, the EHP stack configuration for start releses 6.20 and higher, these text files do not match anymore.
This can contribute for EHP_INCLUSION phase failing. Have you renamed it? It usually is a long file name, for example: SMSDXML_EP1_20111002154601.221.xml. Please make sure you or someone have not made manual changes in this xml.
I hope this information helps.
Best regards,
Tomas Black

Itanium: Rfc call for SXMI_XMB_SYSLOG_READ fails Error INVALID_DATE_TIME

I have a distributed NetWeaver 2004S Environment: Main SAP Instance and Database are located in a CST Time Zone on the same machine. A dialog SAP instance, installed on an HP-UX Itanium Host, is located in a PST Time Zone, but, the system clock set for CST time - 2 hours behind the main SAP instance host system clock time.
My application is installed on the HP-UX Itanium Host and connects to the local (dialog) SAP instance, and makes RFC library calls to collect data. For Syslog data, the RfcCallReceive call is made to function SXMI_XMB_SYSLOG_READ with all the required input parameters. This call succeeds for the first time, but, fails all subsequent times if the call is repeated at 1 minute interval. Following error message is returned:
gid:105 key:INVALID_DATE_TIME
The date times on start and stop times are correct - they match very well with the system clock time.
Now, if I increase the repetition interval from 1 minute to 5 minute, the Rfc call to the function SXMI_XMB_SYSLOG_READ succeeds for the repeated calls.
Please note that the Rfc application was compiled on an HP PA-RISC development machine, and, uses ARIES emulator to run on HP Itanium Host.
There is another piece of information I can provide here if that helps: I am able to make 1 minute spaced repeated Rfc call to SXMI_XMB_SYSLOG_READ function with success on a PA-RISC dialog instance of another SAP deployment that has the main SAP instance plus database on one machine in a CST time zone, and, the dialog SAP instance hosting the application on PA-RISC host on a different machine, but, in the same CST time zone.

Hi Manoj,
The Application and the dialog instance are on the same machine - HP-UX IA64. This is what TZ has on this host
TZ=CST6CDT
How do I synchronize the application and the SAP dialog instance - they are located on the same physical machine?
The main instance and the database are on another machine - SunOS5.10 sparc. This is what TZ has on that host
TZ=US/Central
The date on HP-UX IA64 (dialog instance) is
date
Fri Nov 21 13:13:35 CST 2008
The date on SunOS5.10 sparc (Main Instance + Database) is
date
Fri Nov 21 13:13:35 CST 2008
Please note that the dialog instance and the main instance are located geographically in PST and CST time zones - being 2 hours apart.
I appreciate very much your effort. Looking forward to the follow-up.
Thanks

RFC call ended with "Communication Failure" exception (Function call failed; could not find the function

Hi All,
I am getting error while executing oDATA service from SAP Netweaver Gateway
Error details:
RFC call ended with "Communication Failure" exception (Function call failed; could not find the function
I am using SAP NG 740
Project is created in Gateway system using SEGW having Map to Datasource option used.
in SPRO manage alias, I had seleted Local App option. Screen attached
I had tried all troubleshooting like delete and add service and alias in "/IWFND_MAINT_SERVICE".
but still getting same error for all service.
Kindly advise.
Regards
Vivek

Hello Vivek,
Service builder would have also generated code for RFC Exception handling to catch exceptions raised when communication fails between your GW and BE for some reasons.
Handling is done for 1. System Failure 2. Communication Failure & 3. Business Failure;
Put a BP in your DPC or DP_EXT class where exception code is written to check what exactly is has caused communication failure.
Check if that RFC is existing in that destination or not.
For your reference : Code would be something like this. Put BP here and check the problem.
* Error and exception handling
IF lv_subrc <> 0.
* Execute the RFC exception handling process
   me->/iwbep/if_sb_dpc_comm_services~rfc_exception_handling(
     EXPORTING
       iv_subrc            = lv_subrc
       iv_exp_message_text = lv_exc_msg ).
ENDIF.
Go inside this method and check to get info on what has to be done to resolve issue.
Check carefully what has gone wrong and fix it accordingly.
No need of adding service & deleting as problem is not because of that.
Regards,
Ashwin

Fail in RFC call to PI

Hi,
I have a problem with communication of RFC call and PI
The situation is:
ECC calls RFC from report and by the background method with destination to PI.
but...the rfc stays fixed in transaction SM58...and the PI don't receive any message...
The message in SM59 call transaction is:
com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup rfc sender sm58
We have used the follows structure:
PI 7 with SP 9 - AIX + Oracle
SAP ECC 6.0 - AIX
Thank''s a lot for any help...
Sandra

Hi Sandra,
Great! I'm glad this worked.
I would only use this as a temporary solution though.
This happened because the SAP R/3 Business System that you've specified in your Integration Builder Configuration doesn't match the system (SID and client) that you're sending from. I would recommend correcting the Configuration and then checking this flag again. It's safer that way, because right now you could make calls from any R/3 system and XI would accept it.
To correct the Configuration, you'll likely need to:
1) Create a Business System for the R/3 system that you're making the RFC call from. If it's DEV client 100, you would create a Business System called DEV_100 for example.
2) Redo your configuration with this Business System.
3) Check the 'Verify Sender System' flag again in your configuration.
Thanks,
J Wolff

Error in START_SHDI_FIRST... RFC logon fails

Hello All,
I cannot get past a step in the enhancement package 4 installation. The step is called: START_SHDI_FIRST. The error says to troubleshoot by looking at 2 logs, STARTSFI.LOG and DEVTRACE.log.   extracted below.
The problem can be described this way. The step begins as the installer tries to start the shadow system.   The first attempt stopped and I could see that the shadow was not started. I used the information in note 525677 to manually start the shadow and could verify that it was starting.
The screen says to retry until I can logon to the shadow.   I am able to logon as user SAP* with password pass in client 000.   I am not able to logon as myself and receive the message: Logon not possible (error in license check).
As SAP* I use the transaction SLICENSE, and could see that the maintenance certificate had expired. I loaded that certificate without an error.
I also see that the hardware key information is missing. SAP* is not allowed to update that information.
I believe that no other user will be able to logon as long as the license is an issue.   The installer is trying to do a remote logon to verify that the system is up (my interpretation) .
I also see this information in the shadow system dev_W1 log.
M *** ERROR => ThMsGetHardwareId: ThOpcodeToMsg failed (1) [thxxmsg.c    3095]
M ***LOG Q16=> ThGetMsHwId, DpMBufHwIdGet (HWID_PENDING) [thxxmbuf.c   511]
M *** ERROR => SlicLikeyGetHardwareKey: no hwid from MSG server: -1 [sliclikey.c 1301]
M *** ERROR => likey_get_validity_dates: Error getting the hardware key. You might find some information in file "dev_ms" on the message server
M
M Thu Jul 29 15:18:28 2010
M *** ERROR => ThCheckReqInfo: message send/receive failed [thxxhead.c   17580]
M
M Modeinfo for User T8/M1
So, am I correct in seeing that the missing hardware key is the problem in the shadow system?   Any ideas would be appreciated, otherwise I will clear the systems out and start over. Thanks.
Pat.
Below is the DEVTRACE   (extract)
Directory: /usr/sap/TEH/EHPI/abap/log
Name:       DEVTRACE.LOG
trc file: "dev_disp.new", trc level: 1, release: "701"
sysno      15
sid        TEH
systemid   324 (IBM iSeries with OS400)
relno      7010
patchlevel 0
patchno    69
intno      20020600
make:      single threaded, ASCII, 64 bit, optimized
pid        103802
Thu Jul 29 14:54:58 2010
kernel runs with dp version 243(ext=110) (@(#) DPLIB-INT-VERSION-243)
length of sys_adm_ext is 364 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (15 103802) [dpxxdisp.c   1287]
     shared lib "dw_xml.so" version 69 successfully loaded
     shared lib "dw_xtc.so" version 69 successfully loaded
     shared lib "dw_stl.so" version 69 successfully loaded
     shared lib "dw_gui.so" version 69 successfully loaded
     shared lib "dw_mdm.so" version 69 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3615
MtxInit: 30000 0 0
Thu Jul 29 14:54:59 2010
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value : -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation std
<ES> Info: use normal pages (no huge table support available)
EsStdUnamFileMapInit: ES base = 0x7000000b0000000
EsStdInit: Extended Memory 4096 MB allocated
<ES> 1023 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
Thu Jul 29 14:55:00 2010
WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   13279]
DpSetProcessPriority: Run priority for work process startup adjusted to 20
DpSetProcessPriority: Run priority for work process startup adjusted to 20
Thu Jul 29 14:55:01 2010
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2519]
ERROR => NiPConnect: SiConnect failed for hdl 2 / sock 9
    (SI_ECONN_REFUSE/79; I4; ST; 10.127.0.100:3615) [nixxi.cpp    2519]
ERROR => MsIAttachEx: NiBufConnect to omni/3615 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c   1816]
Thu Jul 29 14:55:19 2010
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Thu Jul 29 14:55:53 2010
***LOG Q0I=> NiPConnect: connect (79: Connection refused) [nixxi.cpp 2519]
ERROR => NiPConnect: SiConnect failed for hdl 3 / sock 10
    (SI_ECONN_REFUSE/79; I4; ST; 10.127.0.100:3615) [nixxi.cpp    2519]
ERROR => MsIAttachEx: NiBufConnect to omni/3615 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Thu Jul 29 14:56:34 2010
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5007]
trc file: "dev_ms", trc level: 1, release: "701"
[Thr 01] Thu Jul 29 14:54:56 2010
[Thr 01] MsSOsPrivInit: Run priority adjusted to 12
[Thr 01] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid   324 (IBM iSeries with OS400)
relno      7010
patchlevel 0
patchno    63
intno      20020600
make:      multithreaded, ASCII, 64 bit, optimized
pid        103801
[Thr 01] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 103801) [msxxserv_mt. 1853]
[Thr 01] Thu Jul 29 14:54:57 2010
[Thr 01] SigISetDefaultAction : default handling for signal 20
[Thr 01] ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3239]
[Thr 01] *** ERROR => NiIBindSocket: SiBind failed for hdl 1 / sock 7
    (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:3615) [nixxi.cpp    3239]
[Thr 01] *** ERROR => MsSCommInit: NiBufListen(3615) (rc=NIESERV_USED) [msxxserv_mt. 10222]
[Thr 01] *** ERROR => MsSInit: MsSCommInit (internal) [msxxserv_mt. 1903]
[Thr 01] *** ERROR => main: MsSInit [msxxserv_mt. 5983]
[Thr 01] ***LOG Q02=> MsSHalt, MSStop (Msg Server 103801) [msxxserv_mt. 6030]
trc file: "dev_rd", trc level: 1, release: "701"
Thu Jul 29 14:55:00 2010
Shared memory semaphore administration area size = 10608
Thu Jul 29 14:55:06 2010
***LOG S00=> GwInitReader, gateway started ( 103807) [gwxxrd.c     1758]
systemid   324 (IBM iSeries with OS400)
relno      7010
patchlevel 0
patchno    68
intno      20020600
make:      single threaded, ASCII, 64 bit, optimized
pid        103807
gateway runs with dp version 243(ext=110) (@(#) DPLIB-INT-VERSION-243)
gateway (version=701.2009.09.28)
gw/local_addr : 0.0.0.0
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
Thu Jul 29 14:55:09 2010
CCMS: Checking Downtime Configuration of Monitoring Segment.
Bind service sapgw15 (socket) to port 3315
GwPrintMyHostAddr: my host addresses are :
1 : [10.127.0.100] omni (HOSTNAME)
2 : [127.0.0.1] LOOPBACK (LOCALHOST)
Full qualified hostname = omni.plastekgroup.com
DpSysAdmExtCreate: ABAP is active
DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
MtxInit: -2 0 0
Thu Jul 29 14:55:47 2010
GwDpInit: attached to gw_adm at 700000080599e90
Thu Jul 29 14:55:48 2010
DpSetProcessPriority: Run priority for gwrd adjusted to 12
AN EXTRACT OF STARTSFI_LOG
Directory: /usr/sap/TEH/EHPI/abap/log
Name:       STARTSFI.LOG
1 ETQ201 Entering upgrade-phase "START_SHDI_FIRST" ("20100729145436")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '14', GwService = 'sapgw14'
4 ETQ399 Environment variables:
4 ETQ399   dbs_db4_schema=<null>
4 ETQ399   auth_shadow_upgrade=<null>
4 ETQ399 Set environment for standard connect:
4 ETQ399 ENV: dbs_db4_schema=SAPR3
4 ETQ399 ENV: auth_shadow_upgrade=0
4 ETQ399 Set RFC variables for standard connect:
4 ETQ399 System-nr = '14', GwService = 'sapgw14'
4 ETQ399 Set tool parameters for standard connect:
4 ETQ399   default TPPARAM: DEFAULT.TPP
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'MAIN_SHADOW/START_SHDI_FIRST'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'DEVTRACE.LOG'
4 ETQ399 Set environment for shadow connect:
4 ETQ399 ENV: dbs_db4_schema=SAPR3
4 ETQ399 ENV: auth_shadow_upgrade=1
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '15', GwService = 'sapgw15'
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399   default TPPARAM: SHADOW.TPP
4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"
4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
2 ETQ399 Starting shadow instance
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2 ETQ399 Stopping shadow instance
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
2 ETQ231 RFC Login failed
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
2 ETQ231 RFC Login failed
2 ETQ353 Starting system
3 ETQ399 Executing command: 'startsap SID(TEH) INSTANCE(15) PROFILE('/usr/sap/TEH/EHPI/abap/TEH/SYS/profile/START_DVEBMGS15_omni')'.
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="TEH", Nr="15", GwHost="omni", GwService="sapgw15"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-1"
2EETQ399 Starting shadow instance failed
2EETQ399 Test RFC failed finally

Hi,
You are getting this error because your hardware key in the license installed in slicense is wrong. Since upgrade tries to login with ddic user and if there is problem with license then only SAP* user is allowed.
Please perform below steps to resolve the problem. Check at OS level what is the hardware key, if the hardware key that is present in slicense is different then generate a permanent license of that hardware key and apply it in shadow instance. After that check whether you are able to login with user other than SAP*, if yes, then repeat the phase.
Please perform above steps and let us know the result.
Thanks
Sunny

SOAP Receiver adapter error. SOAP CALL Failed

Hi ,
I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
SOAP: call failed
SOAP: error occured: java.net.ConnectException: Connection timed out
Message log is as below.
Any clue ?
Thanks & Regards,
Mathew
2005-10-31 18:59:58
Success
output
1130810398454
The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
2005-10-31 18:59:58
Success
output
1130810398458
Using connection AFW. Trying to put the message into the request queue.
2005-10-31 18:59:58
Success
output
1130810398458
Message successfully put into the queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message was successfully retrieved from the request queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message status set to DLNG.
2005-10-31 18:59:58
Success
output
1130810398460
Delivering to channel: CC_CALCULATOR
2005-10-31 18:59:58
Success
output
1130810398564
SOAP: request message entering the adapter
2005-10-31 19:03:07
Success
output
1130810587497
SOAP: call failed
2005-10-31 19:03:07
Error
output
1130810587497
SOAP: error occured: java.net.ConnectException: Connection timed out
2005-10-31 19:03:07
Error
output
1130810587498
Exception caught by adapter framework: Connection timed out

Hi Mathew,
Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
Prasad

Error in starting SAP GUI as part of an Java RFC call from a PC

Hi,
We are on the 4.6C version of SAP and have the latest basis kernel patches that allow an RFC connection to start the SAP GUI. The program that I am running externally is java using the 3.0.1 JCo. The OS of the PC I am using is Windows XP. The SAPGUI version is 7.10 patch level 11.
The program seems to be working properly as the command prompt window goes grey as if there is another window being opened but then I get back this error message and I do not see the GUI.
The message I am getting back is:
Exception in thread "main" 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)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.startSAPGui(MiddlewareJavaRfc.java:1853)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1285)
at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:661)
at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:171)
at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:44)
at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:160)
at com.sap.conn.jco.rt.RfcDestination.initializ(RfcDestination.java:766)
at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:794)
at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:32)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:865)
at GISToSAPWO_Test.get_wo_call(GISToSAPWo.java:91)
at GISToSAPWO_Test.main(GISToSAPWO_Test.java:206)
I have been all over trying to find the solution to this and have come up empty. Any help will be greatly appreciated. If this is the wrong forum for this please let me know and I will re-post.
Thank you in advance for any information you can pass on about the issue,
Mark

Hi Greetson,
Thank you in advance for your response. It is greatly appreciated.
1) In a way yes. I am using the connection setting USE_SAPGUI = 1. This is suppose to start the GUI prior to starting the RFC's program run. If this is not correct please let me know.
2) The code is part of the JCo and the RFC library from what I have read. If this is not correct please let me know.
3) I am only testing from my PC at this moment. I have re-installed my SAP GUI and am now at patch level 13 on 7.10.
4) The application passes in the connection information which includes username and password along with the parameters for the RFC call. I would like the SAP GUI to open without the user having to re-enter his/her username and password. I thought that once the RFC is called using the dialog users credentials that the GUI would then open using the connection. I have used the java pooled connection method and it still does not open the GUI.
5) The purpose is to pass Equipment objects, Functional Location objects and Leak Id objects to an RFC to open a list screen from IW39, List Maintenance Order transaction, for display of each at one pass, as well as open Excel with data from classification for the Leak Id's.
Hope this sheds some light on the problem I am having. Please let me know if more information is needed.
Best regards,
Mark

XI RFC call failing

Similar Messages

Maybe you are looking for