cancel
Showing results for 
Search instead for 
Did you mean: 

Calling RFC's using SAP .NET connector

Former Member
0 Kudos

Hello,

We have a .NET project that calls RFC's using the SAP .NET connector. Initially it looked like it works fast and reliably, but when we got to more extensive multi-user load testing we get the following problem:

If 2 users are connecting together, after about 15 refreshes of the web page that calls the rfc, the IIS hangs. If we debug we see the following exception:

<i>CPIC-CALL: 'CMRCV' LOCATION CPIC (TCP/IP) on local host ERROR internal error TIME Mon Jan 03 14:32:33 2005 RELEASE 620 COMPONENT NI (network interface) VERSION 36 RC -1 MODULE ninti.c LINE 1094 DETAIL NiPRead SYSTEM CALL recv ERRNO 10038 ERRNO TEXT WSAENOTSOCK: Socket operation on non-socket COUNTER 30</i>

Any ideas as to what my be causing this?

Thanks,

Yoni

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

I am getting this same error :

CPIC-CALL: 'CMRCV' LOCATION CPIC (TCP/IP) on local host ERROR internal error TIME Mon Jan 03 14:32:33 2005 RELEASE 620 COMPONENT NI (network interface) VERSION 36 RC -1 MODULE ninti.c LINE 1094 DETAIL NiPRead SYSTEM CALL recv ERRNO 10038 ERRNO TEXT WSAENOTSOCK: Socket operation on non-socket COUNTER 30

can you tell me what changes you made in .net code that its working fine now.

Former Member
0 Kudos

Hi Guys,

My Project, we are planning to call RFC function module through .net connector. As per the requirement, the other system will call 200 times/per Job the RFC function module through .net connector. Per day around 5 Jobs with different time.

Just i would like to know the following things,

1. Is it .net connector is reliable?

2. Is there any code optimization, i can look into .net connector or ABAP side?

3. What type of failure may occur, while using .net connector?

Appreciated your help.

Note: Due to client willingness, We can't elimate the .net connector. mainly i am looking into reliable & optimzation of code and problems.

Thanks and Regards,

Arun

Former Member
0 Kudos

OK, it seems as there were some problem in the .NET code that had nothing to do with the SAP .NET connector. We fixed them and now it works like a charm.

Thanks to all who responded,

Yoni

Former Member
0 Kudos

Hi Yoni,

my application is running fine, but in different times I get the same message and has to restart the application.

Can you tell me what changes you made in .net code that its work fine now ?

Thanks and Regards,

Jürgen

Former Member
0 Kudos

Hi All,

I too get the same error.

I have a ASP.NET Windows Service. I have used the SAP.NET Connector, generated a SAP Proxy and am using that to connect to SAP.

I call a selection of BAPI's (RFC's) based on data in transaction tables in my SQL Server database.

I would be very grateful if those of you that have suffered from this error and have fixed it could provide there fixes.

Kindest Regards

reiner_hille-doering
Active Contributor
0 Kudos

I don't know what's exactly wrong here, but you must be extremely carefull with multithreaded calls to .NET connector (which can easily happen in ASP.NET). E.g. you cannot share a Connection object for concurrent calls.

Former Member
0 Kudos

May I ask how are you logging on with 2 users? are they logging on with the same user id? If they are, try and used pooled connections and see if it solves your problem. From the error message it seems more like a network unavailability problem...but it's worth a try.