Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

RFC Connection problem

Former Member
0 Likes
2,722

Hi All,

We have .NET program(Using c#) which uses RFC's. We used 2 years RFC's without any problem until We have been upgraded our system from EHP4 FOR SAP ERP 6.0 / NW7.01 to ECC 6.0  EHP6.

Hello;
we have .net program which uses zping rfc connection to our sap systems

Program firstly checks for connecton from start for 3-4 seconds, after
that connection drops we can see from icm logs.

on .Net pogram http://192.168.10.61:1000/sap/bc/soap/rfc (for ABQ
system)

on web page and . net program it goes
http://192.168.10.61:1000/sap/bc/soap/wsdl11?sap-client=100&services=ZPING

in here we use rfc's which starts with zmst* .

best regards








ICM logs;
[Thr 6316] NiIRead: hdl 205 received data (rcd=331,pac=1,RAW_IO)
[Thr 6316] NiIRead: SiRecv failed for hdl 205/sock 8108
[Thr 6316] (SI_ECONN_BROKEN/0; I4; ST; P=172.16.0.153:50445;
L=192.168.10.61:1000)[Thr 6316] NiICloseHandle: shutdown and close
[Thr 6316] IcmConnClose: Connection 3/158 closed
[Thr 6316] IcmConnFreeContext: context 3 released
[Thr 6316] IcmServDecrRefCount: srvsapqa.konyaseker.com.tr:1000 - new
serv_ref_count: 0
[Thr 6316] REQ TRACE END: 3/158/2
[Thr 6316] IcmWorkerThread: Thread 3: Waiting for event

172.16.0.153 --> .net application
192.168.10.61 --> SAP QAS system

Steps for Reconstruction



Please help me...

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,424

After kernel update,

using rz10 we add parameter;

icm/HTTP/expect_100_close_on_error = false

The problem has been solved.

2 REPLIES 2
Read only

Former Member
0 Likes
1,425

After kernel update,

using rz10 we add parameter;

icm/HTTP/expect_100_close_on_error = false

The problem has been solved.

Read only

0 Likes
1,424

And the details are in SAP note 1737707. The .NET application can also be changed to avoid the problem.

https://service.sap.com/sap/support/notes/1737707