Operating system call recv failed (error no. 131 )

[Former Member]

Hi

Our background jobs have been cancelled; log shows as below

09/27/2009 20:32:21 Communication error with the external tax system (VERTEX O) FS 864 S

09/27/2009 20:32:21 Communication error with the external tax system (VERTEX O) FS 864 E

09/27/2009 20:32:21 Communication error with the external tax system (VERTEX O) FS 864 S

When I check the system log at 20:32:21 it shows the below errors

20:32:21 evfepr02_EPR_00 RD *Q0I Operating system call recv failed (error no. 131 )*

20:32:21 evfepr02_EPR_00 RD S23 Connection to CPI-C client 023 was closed

20:32:21 evfepr02_EPR_00 RD S74 > Partner LU name:

20:32:21 evfepr02_EPR_00 RD S0R > Host: 10.176.123.174

20:32:21 evfepr02_EPR_00 RD S0I > Partner TP Name: sic4010_

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R49 Communication error, CPIC return code 020, SAP return code 223 20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R5A > Conversation ID: 20477512

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R64 > CPI-C function: CMSEND(SAP)

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R49 Communication error, CPIC return code 002, SAP return code 679

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R64 > CPI-C function: CMINIT(SAP)

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R49 Communication error, CPIC return code 002, SAP return code 679

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R64 > CPI-C function: CMINIT(SAP)

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R49 Communication error, CPIC return code 002, SAP return code 679

20:32:21 evfepr02_EPR_00 BTC 17 100 ZBMCUSER R64 > CPI-C function: CMINIT(SAP)

This disconnection happens now and then but not frequently;

Can you please let me know what the root cause is and resolution for the same?

Thank-you

Edited by: Kasinath Parepally on Sep 28, 2009 8:24 PM

Edited by: Kasinath Parepally on Sep 28, 2009 8:26 PM

[Former Member]

One other thing . . .. go to SMGW. Select the GOTO menu and Logged on Clients. Check to make sure Vertex is listed (several times for us) with Connection Status OK.

[Former Member]

We have Vertex O series as well and encountered similar when setting up Vertex. After establishing RFC connection, check the Vertex logs- look for Vertex/O series/Log folder and Vertex/SIC/Log/Time.log or sic.log. O Series folder will throw basic messages, SIC/Sic.log will give specific error messages with XML on each transaction, and SIC/Time.log will give timings as to how long it took to complete a transaction.

Does your Vertex O series have it's own box or does it share with SAP? In my experience, we ended up setting the timeout to a higher threshold while increasing priority/timeslice on the server.

Is your Vertex O series webservice and central sharing the same memory pool? Consider separating into two different pools.

Hope that helps.

[Former Member]

Check rfc connection to vertex is working. If you have app servers make sure rfc connection will work from all

app servers. If not you have to check the env variables of that server. May the job try to execute from a app server where VERTEX rfc isnt working

Thanks

Prince Jose

[Former Member]

Hi Jose

Thanks for quick response

As you suggested I did check RFC connections in SM59 it is working. I did also check in SMGW registered program is shown.

As I said in previous message issue is not persisting all the times; it happens now and then not frequently.

Can you please let me know further.

Thank-you