cancel
Showing results for 
Search instead for 
Did you mean: 

Systems error- restart not possible

Former Member
0 Kudos

Hi,

I'm trying a synchronous ABAP Proxy to RFC scenario.

Have triggered the proxy report and got the values in XI but the RFC is not called and error flag in SXMB_MONI says" System error-restart not possible".

I'm getting 2 entries in SXMB_MONI:

1) Proxy interface as sender.

2) RFC as sender.(System failure during Jco call)

Any would be appreciated.

Regards,

Anish

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Anish,

If error is in intermediate step or mapping than restart of the message is not possible. You have to start again sending message from proxy.

Thanks,

Prateek

Former Member
0 Kudos

Hi Prateek,

I have run the proxy several times and I get the same error.

Some more info:

When debugging the proxy report I get " CX_AI_SYSTEM_FAULT" exception and before calling the proxy it asks for SAP Web application server username and password.

Regards

Anish

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Anish,

Please have a look at these..

cheers,

Prashanth

Former Member
0 Kudos

Hi,

On doing Test Connection for AI_RUNTIME_JCOSERVER in SM59, I get different errors everytime.

a) program AI_RUNTIME_TXT not registered

b) max no of 100 conversations exceeded .

Help me in fixing this.

and surprisingly the scenario worked for once.

Regards,

Anish

Message was edited by: Anish Abraham

moorthy
Active Contributor
0 Kudos

Hi Anish,

<i>***2) RFC as sender.(System failure during Jco call)</i>

Check the Queue, by double clicking the Queue id in the SXMB_MONI/SMQ2. Then try to execute th LUW of that. Probably, you can see this error in the Queue Monitor itself " JCO Failure..".. If so go to SM59->

a. Go to TCP/IP Connections-> AI_RUNTIME_JCOSERVER->double click

b. Test the RFC destination. If connection is failure then it should be fixed. You may need to delete the entry and recreate the same . Still error may be required to restart the server.

If so, it may be because of Java Virtual Memory problem, no of parallel processes assigned in the Visual Admin..

And one more thing- Is your scenario is ABAP proxy->XI->RFC ???

Hope this helps,

Regards,

Moorthy

Former Member
0 Kudos

Hi Moorthy,

I tried remove and creating AI_RUNTIME_JCOSERVER many times and restarted the XI server also but it didn;t help me.

My scenario is ABAP Proxy -> XI -> RFC

Please help.

Regards,

Anish

Former Member
0 Kudos

Hi Anish,

The Program ID used for the AI_RUNTIME_JCOSERVER is not registered.

It must be working before because this Program ID was registered. Please ask your Basis person to see if the Program Id is registered.

Regards

Vijaya

Former Member
0 Kudos

Hi Vijaya,

The error message is not consistent.

I have checked with the BASIS team and confirmed that AI_RUNTIME_TXT ( program ID) is created in JCoRFC settings in Visual Admin

Please help.

Regards,

Anish

Former Member
0 Kudos

Hi Anish,

For the error you have described in SM59,

On doing Test Connection for AI_RUNTIME_JCOSERVER in SM59, I get different errors everytime.

a) program AI_RUNTIME_TXT not registered

The only reason can be that this program ID is not registered. Please can you show that to your Basis team.

Is there any other error that you are getting?

Regards

Vijaya

Former Member
0 Kudos

Hi Vijaya,

As I mentioned the error is not consistent. Sometimes in "Test Connection" I get success result also. We have created AI_RUNTIME_JCOSERVER in Visual admin again but no help.

When I run the proxy report "cx_ai_system_fault" exception is getting raised at the same time I get 2 entries in SXMB_MONI of XI server:

(a) Proxy as sender interface

(b) RFC as sender interface

both messages with " System error- restart not possible" flag and (b) has a detailed error message:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>

<SAP:P1>Error opening an RFC connection.</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connection.</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Hope this would give you a better idea about the sceanrio.

Regards,

Anish

Former Member
0 Kudos

Hi Anish,

Please can you reactivate both your adapters. RFC and XI Proxy. Just make some changes and reactivate them.

Also Set the RfcAdapter J2EE service property 'initialRfcClientConnectCheck' from 'true' to 'false'. (This in VA)

Then check if your AI_RUNTIME_JCOSERVER is giving successful results.

Run the scenario after this and let me know the error if you are getting any

Regards

Vijaya

Former Member
0 Kudos

Hi all,

Thanks for all your help and suggestions!

It is working now :-).

Thanks a lot Vijaya for you help!

I gave "initialRfcClientConnectCheck -> false" in the RFC adapter (Advanced)itself and it threw the same error!

I'm not able to point out what did the trick but it is working now!

Thanks again

Anish

Former Member
0 Kudos

Dear Anish,

Since you got values in XI. The problem might be with the receiver side.

" <i>2) RFC as sender.(System failure during Jco call)</i>'

I am confused here since RFC is in receiver side of your scenario.

Since the RFC is not yet called,

    • Check the RFC connection in SM59.

    • Check whether import has occured properly at receiver side,

regards

Mahesh