Error on WAS no. 10054 SAP Basis System: Operating system call

[olaf_reiss]

Hi sdn,

we got the following error message in the syslog of the WAS:

SAP Basis System: Operating system call recv failed (error no. 10054)

The system still works. What can we do?

Thanks.

Best Regards,

Olaf Reiss

[Former Member]

Dear Friends,

I have the same problem on the following system environment.

Kernel 7.42

MaxDB 7.9.08.xx

ECC6.0 EhP7

SAP GUI 7.40 PL 3

Windows 7

Fritzbox 7490 ADSL or 6360 Cable

First SAP GUI freezes, then the message "WSAECONNRESET: Connection reset by peer" appears.

The error is very common, after approximately 5 - 20 minutes, if I connect from home via VPN.

In SM21 I get the message: "Betriebssystem Aufruf recv gescheitert (errno 10054) WSAECONNRESET"

If I connect to the internet via LTE, I have no problems with connection.

What I have already done:

- Change MTU size

- changed rdisp/keepalive to 280

- disable the firewall in windows and the router firewall

- read the mentioned sap notes

- tried with mac OSx and Windows 8.1

- test with niping

I haven't the slightest idea, what to do now.

I know, it is a network problem. But what can I tell my network administrator he should do?

Regards,

Daniel

[Former Member]

I had the same problem.

Workaround which used for me.

To use the servername and not the IP Adress in the SAP Logon information.

BR

Marcus

[Former Member]

Hi,

I am getting the below error

Connection reset by peer.....

We are moving data from SQL to SAP BW using SAP BODS....

when we run the job in SAP BODS, We are getting above error...

Please Help me ..

Many Many Thanks In Advance...

Regards,

Divyesh Patel

[patelyogesh]

I had same issue and I have to install Microsoft Visual c++ 2005 SP1 Redistributable package and restart instance.

Please let me know if this works for you.

Cheers,

Yogesh

[Former Member]

Siddhesh, Sanujit, you suggestion of restarting the whole system worked for me.

Thank you

Gandham Sai Kiran

[patelyogesh]

Hello Everyone,

I think there is nothing to do with this error on SAP side.

Try to ping your server from client PC and see you are getting Reply time out.

Ping with -t option so it will keep repeat ping request.

This is pure network connectivity issue with SAP server.

Regards,

YP

[frank_lauerbach]

Hello,

I had the same problem with a WAS.

Transaction SMICM did not work and web sites could not be displayed.

In SM50 a job for sending emails was running very long, because in SOST were many emails.

The connection to mailserver did not work, that's ok, because it is a dev system.

After I canceled the job for sending emails ICM was running and it had maximum number of processes.

Perhaps it helps somebody.

Greets

Frank

[Former Member]

HI

Please refer SAP note number 997535.

[jonathon_sells3]

Are you sure that's the right note? "Note 997535 - DB02: Problems with History Data."

We are getting the same problem on the Central instance and all app servers.

ECC 6.0 running kernel 159. Windows Server 2003 x64 with SQL Server 2005 SP2.

Clients are Windows XP with SAPGui 7.10 Patch 5.

[Former Member]

Thank you Maria.

I think my initial assessment is more justified now... this seems to be something that is specific to the windows platform.

Do update if you find a resolution and I will do the same.

Thanks,

Eric

[Former Member]

Hi All

WSAECONNRESET 10054 error

means

Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

[http://msdn.microsoft.com/en-us/library/ms740668(VS.85).aspx|http://msdn.microsoft.com/en-us/library/ms740668(VS.85).aspx]

So we need find some parameters in Windows Server thats can tune WinSocket and I think we'll solve our issue.

Any suggestions?

Edited by: petr shvadronov on Dec 12, 2008 6:32 PM

[Former Member]

Thaniks for the response Maria.

We are seeing this in our CRM 2007 SPS04 Kernel 180 (but now 179 is all that is available SMP).

what is your platform if I may ask. we are W2K3/SQL. I have not seen this on previous work on AIX... just curious if you were alsoon Windows.

thanks,

Eric

[MPGraziano]

Erik

We are running Windows 2003 Sql 2004 64bit OS

Maria

[Former Member]

Maria,

what patch level of kernel will resolve this issue in NW70?

I am currently at NW70 PL180 and am still experiencing this error.

Please advise,

Eric

[MPGraziano]

Not sure , but when I went around the block with SAP , with the errors , they mentioned that by applying the next stack of SPs, and Kernel Patches , should resolve the problem

we are ECC 6.0 Kernel 179 only on our dev server and we are still receiving the error AND I just finishing applying YE 2008 SPs and Kernel Patch

So SAP theory is definitly wrong

Maria

[Former Member]

I have the same problem. Anybody solved this issue?

[Former Member]

I had the same error registered in Solution Manager, while we were attempting to synchonize our 7 servers (CRM, Portal, T-Rex and DataBases). All the services were up, but the web platform wasn't working. We returned the clock difference between servers and the platform started working.

The only trace about the issue is the error mentioned above. Do you have some suggestions about it?

[Former Member]

Hello guys,

I also eperienced the error:

SAP-Basis System: Operating system call recv failed (error no. 10054)

when installing SAP NetWeaver Composition Environment 7.1 Trial Version SP1 Preview on:

- VMware Workstation

- Windows XP Professional SP2

- MaxDB Database include int CE 7.1 Trial

What can I do??

Regards,

Manuel

[former_member433984]

by itself 10054 (An existing connection was forcibly closed by the remote host) is not dramatically error and does not prevent SAP system from working as it means that remote process connected to the socket suddenly finished his connection. What the reason for this (NI connection lost, process termination or something else) must be analyzed in dev traces and probably in network scans.

As Harrison Holand told in his post:

>I got a similar error when a SAPGui disconnected suddenly from the Web AS Server. >This disconnection was due to a restart on the front-end computer without logging out >of SAP first.

I.e. you can easily reproduce the issue if you kill your SAPGUI process. But again the SAP server remains running.

see also notes

<a href="https://service.sap.com/sap/support/notes/155147">Note 155147 - WinNT: Connection reset by peer</a>

<a href="https://service.sap.com/sap/support/notes/545177">Note 545177 - FAQ: Preliminary steps in analyzing RFC connections</a>

<a href="https://service.sap.com/sap/support/notes/500235">Note 500235 - Network Diagnosis with NIPING</a>

for details and troubleshooting

[Former Member]

Hi all,

I am still having the same problem with a new plataform which is SAP NW 2004s SP7 and Oracle 10.2.0.2.

<b>SAP-Basis System: Operating system call recv failed (error no. 10054)</b>

I restarted J2EE and it was not solved. Anyone had found a solution?

tks.

Daniel Silva

[Former Member]

Hi,

I got the same error Message as Danial Silva.

I have installed SAP NW 2004s SR1 with Oracle 10.2.0.2.

Java Version is 1.4.2_13

Any solutions?

Johannes Weiß

[LeonardoAraujo]

Same thing here.

I've installed ABAP and JAVA app servs in the same machine and I cannot start it. I get this error...

SAP-Basis System: Operating system call recv failed (error no. 10054)

but I got to be honest. the first error I get is...

SAP-Basis System: In table TCPDB, there are 0 entries

Any help is greatly appreciated.

Leo

[former_member221634]

Neither of those messages will keep your SAP from coming up - the TCPDB message just means that there are no code pages in the TCPDB table.

[Former Member]

I remember having the same error in our SAP hosting service for several SAP systems: different versions and platforms, always the same error msg.

In some cases the user experienced disconnections in the SAP Gui Frontend, in another cases the problem was not critical and the error didn't show up explicitly.

In that time we asked the network specialists to make an extended and detailed analysis of the WAN to find out what was happening. I remember they changed some parameters and the problem got solved. I suggest to contact your network specialists and work with them, monitoring and looking the sent and received packages by the network protocol and find the solution as well.

Jessica.

[Former Member]

Use se38, execute RSCPINST program and update database -F5 (button Activate)TCPDB table will be updated. Regards.

[Former Member]

Check If your database is installed in this computer.

If not, check If the database server or database is available.

Regards.

[MPGraziano]

by running this report, will this correct the RECV error?

maria

[Former Member]

HI all,

I also have the same problem, and i find the reason,however it may be suit of myself only. As so far,i don't know how to resolve the problem.

The problem occurs when i have installed the Kaspersky Anti-Virus,but not occurs when i have installed the Kaspersky Internet Security.

Message was edited by:

hefang he

[Former Member]

I agree with you

I think it's the problem of kaspersky

but i can'y solve it

[torsten_blank2]

Hi,

I`ve got the same error message after installing upgrade und patches for MaxDB from 7.5 to 7.6. Before that i install Netweaver 04 SP21 (System WinXp SP2) and everything works fine. Now after system has startet the DB is offline, also the nodes. Info: Everthing is installed local.

Edit: Our Basisadministrator solved the problem by setting some things

Edited by: Torsten on Feb 7, 2008 10:53 AM

[former_member97532]

Hi Olaf

were you able to resolve this problem. I am facing this error continously in the app log and have not been able to resovle it. I am trying to configure IPC with CRM and I get a CPIC error return code 679. I have done everthing correctly and feel that rfc connctions error is due to 10054 error.

• LOCATION SAP-Gateway on host crm01 / sapgw01

• ERROR connection to partner broken

*

• TIME Wed Nov 09 09:51:13 2005

• RELEASE 640

• COMPONENT NI (network interface)

• VERSION 37

• RC -6

• MODULE ninti.c

• LINE 789

• DETAIL NiPRead (192.168.2.05/4238, hdl 😎

• SYSTEM CALL recv

• ERRNO 10054

• ERRNO TEXT WSAECONNRESET: Connection reset by peer

• COUNTER 11612

[Former Member]

Hi all,

Thanks for the information, but I'm still not able to solve this problem. I'm not formilar with this stuf. I have deleted my complete WAS 6.40 and installed it agian, but I still get the same error.

Can someone help me with staps how to solve this problem.

Kind Regards,

Richard

[Former Member]

Is there someone who already solved this problem?

[former_member185954]

Hello all,

I think this syslogd entry is common and occurs whenever an open TCP/IP connection is abruptly closed.

As far as I know TCP/IP it does have a system call named 'recv' check the following link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/recv_2.asp

Regards,

Siddhesh

[Former Member]

Hi All,

This is a common problem and I agree to Siddhesh. In past I have experienced the same and restarting the SAP instance has solved the problem.

Regards,

Sanujit

[former_member97532]

Hi Sanujit

I have tried your suggestion and have also configured dispatcher properties file correctly but have not been able to resolve the issue.

Any input will be great

thx

deekshant

[former_member97532]

Hi Richard

were you able to resolve this issue. I am having the same problem and have not been able to resolve it. I am trying to configure ipc with crm restarting windows or ipc services does not help.

your input would help

cheers

deekshant

[Former Member]

Hello all,

I think this error appears when system goes off the network. Run SAP and unplug the network cable and then you will see this error.

Regards

Imran

[MPGraziano]

If this is a common problem and restarting the instance resolves this, THIS IS NOT a viable solution as we cannot regularily restart a production instance.

This error occurs in ALL my servers dev, qas and prdn.

There should be a better solution? any ideas?

maria

[MPGraziano]

The link is quit informative, has anyone explored the tcp/ip configurations and made corrections here to get the RECV error to go away?

[MPGraziano]

First off, we can be restarting a production system randomly, as this message occurs regularily!

I have also found from some of my research and reply from SAP that the newer Kernel should be addressing these issues (?)

I am in the process of applying the YE patches. Time will tell if this error disappears.

Maria

[Former Member]

Hi,

I have also the same error after the creation of a jdbc alias in the WAS 6.40 sp9 server.

Kind Regards,

Richard Middelburg

[Former Member]

I have installed R/3 Enterprise ABAP on Windows : Oracle without any problem, but when I tried to install (J2EE Component)Java Addin I am facing similar problem that is mentioned in the forum & it states as following in the Syslog : <b>" SAP Basis System: Operating system call recv failed (error no. 10054)"</b>.

Pls. assist me in resolving the problem.

Cheers,

Jeetu

[Former Member]

I got a similar error when a SAPGui disconnected suddenly from the Web AS Server. This disconnection was due to a restart on the front-end computer without logging out of SAP first.

[Former Member]

Hi,

I am having the same error and I'm interested in a possible solution for it as well.

It happens on a SAP Web AS 6.40 SR1 MaxDB on a Win2003 SE.

thanks

Javier

[Former Member]

Same problem for me... Any solution for this so far ?

[Former Member]

Hi,

I've got the same error with WAS 6.40 ABAP/JAVA SR1 on Win2003 server with MSSQL

I can't find what is going on.

So, i am interested in the solution as well

Björn

[alfonso]

Im also interested in the solution.

[Former Member]

I would also like to know the reason for this error message (since my syslog also showes this error)

[olaf_reiss]

Which version have you installed. I colud be fixed with WAS6.40 SP9.

Best Regards,

Olaf Reiss

[Former Member]

Sorry, but I do have WebAS 640 SP9 (running on Windows 2003 server with MaxDB) installed.

[kyo_choi2]

Where did you find the SP9 for the MAXDB version of WAS 6.4?