on 02-24-2006 7:48 AM
I have created a scenario involving a RFC sender communication channel and file adapter (Receiver). When i activate the communication channel, it registers a server program in XI. When i call an RFC using a RFC destination pointing to the registered program, it works for the first time and i get 'successful' status in XI Message monitoring. but the status of registered program in 'smqs' transaction code, changes to 'waiting' and any RFC destination pointing to the registered program gives "program ZBWIP24_3 not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY". In otherwords, the registered program and RFC destination points to it hangs completely. Do any one experienced the same issue and solved it?. Can anyone throw some light on that issue?.
hi,
try restarting the XI server
and then have a look at question 25 SAP note: 821267
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
my views...
The scenario is RFC(R/3) --> XI --> File.
it is an Sync call(RFC) getting forwarded to an ASYNC call to the File. Is it waiting for the reposne ?
Could you pls send the RFC request to a BPM, open a sync-async bridge, and send a response back to the R/3 system after the file is written...steps in the BPM would be
1. Receive RFC call(open a sync-async bridge)
2. map to file message(if required)
3. send file
4. map to rfc response
5. send rfc response(close the sync-async bridge)
As for the current status of the destination. Change the sender comm. channel program id....activate it...
switch it back to the original value and activate again...this should hopefully bring the status of the Destination to a working condition.
Thanks,
Renjith.
Hi Arul,
How are you making sure that the RFC call is asynchronous?
Are you using the "CALL FUNCTION func STARTING NEW TASK task " ?
IF yes, the documentation says the following
<b>The asynchronous RFC does not support communication with external systems or programs in other programming languages.</b>
and a TCP/IP destination denotes an external system....
Thanks,
Renjith.
User | Count |
---|---|
78 | |
9 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.