Skip to Content

Are you facing disconnections (sql/database error 0, 11, 121, -1 or 10054) with your SAP system?

The following points might help you to solve this issue! 🙂

1. Refer to Dale’s presentation: Analyzing Network Errors on SQL Server.

2. Follow all the steps in the SAP KBA 1478133.

3. Some of the following points are common errors that are prone to cause this issue:

  • Using a ODBC client instead the SQL Native Client;
  • Using older versions of the SNAC (always use at least the same version of your database instance);
  • Older versions of DBSL and SAP Kernel;
  • Running old versions of SQL Server (always run the latest Service Pack and the latest Security update, hotfixes and cumulative updates provided by Microsoft – see Note 62988 and KBA 1733195).
  • Hardware problems, outdated NIC drivers, Server Memory, etc (hardware, physical network, etc);

4. You can perform the following steps to try to avoid those errors:

  1. On the server side, increase the registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
    TcpMaxDataRetransmissions to 10 {up from the default setting of 5}.
  2. On the client side, both the “Keep Alive” and “Keep Alive interval” can be safely increased via the SQL Server Configuration Manager tool.
    The numbers are in milliseconds and the defaults are 30000 and 1000 respectively.
    Increase “Keep Alive” to 90000 and “Keep Alive interval” to 5000.

5. For further information, double check Notes 1794178 and 1593183.

6. Is your SAP system running on VMware? If yes, also check:

Related Spaces:


In order to view the contents of the SAP Notes and KBAs, you will need to be logged into Service Marketplace.


Hope you like this blog and any comments/suggestions are welcome! 🙂

Best regards,

Eduardo Rezende

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. M. Abdul Jamil

    Dear Eduardo,

    Thanks for sharing these useful points to resolve the mentioned issue of MS SQL. I am also facing issue (10054) on PRD system on daily basis but our db is oracle. May I use above solution for oracle.


    SM21 log

    Operating system call recv failed (error no. 10054)

    Regards,

    (0) 
    1. Eduardo Rezende Post author

      Hello Abdul,

      Some of the recommendations also applies for Oracle: old client/database, old kernel/DBSL, hardware problems, …

      The SAP on Oracle space might be more helpful for your scenario.

      Regards,

      Eduardo

      (0) 

Leave a Reply