Other Errors

The following errors occur only rarely. The descriptions below aim to help you to analyze and eliminate these errors.

The SAProuter receives incorrect data. This can happen if the route is too short or if the system overlooks the fact that the connection is to a SAProuter rather than a backend connection.
The SAProuter receives the route information too late (TCP/IP connection setup was successful).
The SAProuter is the client and it receives an incorrect response from the server.
The SAProuter is the server and it receives the data from the client too early.
SNC not active for a forwards connection
SNC not active for a backwards connection

Incorrect data sent to the SAProuter

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 09:55:36 2007 CONNECT FROM C10/- host 10.66.66.90/34506 (host1.company.corp)` `Thu Jun 14 09:55:36 2007 INVAL DATA C10/- route expected` `Thu Jun 14 09:55:36 2007 DISCONNECT C10/- host 10.66.66.90/34506 (host1.company.corp)`

The client issues the error message below.

Syntax Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host1'
*  ERROR       internal error
*
*  TIME        Thu Jun 14 09:55:36 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -93
*  MODULE      nirout.cpp
*  LINE        2664
*  DETAIL      NiRClientHandle: route expected
*  COUNTER     4
***********************************************************************

End of the code.

Background and Further Analysis

The client program sends incorrect data to the SAProuter. This is usually the case if the client assumes that it is already communicating with the target system but the connection was actually established to an SAProuter that has to wait for a route first. Check the parameters for the connection setup on the client.

Route sent too late

The connection setup (connect) was successful but the client sends the route to the SAProuter too late, or the client assumes that it is already connected to the server and is waiting for data, or the timeout -W is exceeded.

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 12:27:27 2007 CONNECT FROM C11/- host 10.66.66.90/35087 (host1.company.corp)` `Thu Jun 14 12:27:32 2007 CONNECT ERR C11/- no route received within 5s` `Thu Jun 14 12:27:32 2007 DISCONNECT C11/- host 10.66.66.90/35087 (host1.company.corp)`

The client issues the error message below.

Syntax Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host1'
*  ERROR       connection timed out
*
*  TIME        Thu Jun 14 12:27:32 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -5
*  MODULE      nirout.cpp
*  LINE        6519
*  DETAIL      RTPENDLIST::timeoutPend: no route received within 5s
*              (CONNECTED)
*  COUNTER     5
***********************************************************************

End of the code.

Background and Further Analysis

This error can occur if the client does not send the route quickly enough after the TCP/IP connect to the SAProuter. This might be caused by the client hanging temporarily.

Incorrect response from the server

If a server-side program other than a SAProuter responds, or if the back end responds, the SAProuter cannot use t he response. It needs another SAProuter as the server.

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 13:59:43 2007 CONNECT FROM C9/- host 10.66.66.90/46915 (host1.company.corp)` `Thu Jun 14 13:59:43 2007 CONNECT TO S9/17 host 10.66.66.91/3253 (host2)` `Thu Jun 14 13:59:43 2007 CONNECT ERR S9/17 invalid data form server during route completion` `Thu Jun 14 13:59:43 2007 DISCONNECT S9/17 host 10.66.66.91/3253 (host2)`

The client issues the error message below.

Syntax Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host1'
*  ERROR       internal error
*
*  TIME        Thu Jun 14 13:59:43 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -93
*  MODULE      nirout.cpp
*  LINE        2694
*  DETAIL      NiRClientHandle: invalid data from server 'host2' during
*              route completion
*  COUNTER     3
***********************************************************************

End of the code.

Background and Further Analysis

Check the parameters for the connection setup on the client.

Data received too early from the client

If the SAProuter, as the server, receives data from the client before the route is established, the following entries appear in the log file:

SAProuter Log File
`Thu Jun 14 14:15:00 2007 CONNECT FROM C10/- host 10.66.66.90/52640 (host1.company.corp)` `Thu Jun 14 14:15:00 2007 CONNECT TO S10/18 host 10.66.66.91/3253 (host2)` `Thu Jun 14 14:15:00 2007 CONNECT ERR C10/18 invalid data form client during route completion` `Thu Jun 14 14:15:00 2007 DISCONNECT C10/18 host 10.66.66.90/52640 (host1.company.corp)`

The client issues the error message below.

Syntax Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host1'
*  ERROR       internal error
*
*  TIME        Thu Jun 14 14:15:00 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -93
*  MODULE      nirout.cpp
*  LINE        2688
*  DETAIL      NiRClientHandle: invalid data from client
*              'host1.company.corp' during route completion
*  COUNTER     5
***********************************************************************

End of the code.

Background and Further Analysis

The client program is behaving incorrectly. Check for a more recent version of the client program.

Data received too early from the server

The log file contains the following entries:

SAProuter Log File
`Thu Jun 14 13:59:43 2007 CONNECT FROM C9/- host 10.66.66.90/46915 (host1.company.corp)` `Thu Jun 14 13:59:43 2007 CONNECT TO S9/17 host 10.66.66.91/3253 (host2)` `Thu Jun 14 13:59:43 2007 CONNECT ERR S9/17 invalid data form server during route completion` `Thu Jun 14 13:59:43 2007 DISCONNECT S9/17 host 10.66.66.91/3253 (host2)`

The client issues the error message below.

Syntax Syntax

SAProuter Error Message

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host1'
*  ERROR       internal error
*
*  TIME        Thu Jun 14 13:59:43 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -93
*  MODULE      nirout.cpp
*  LINE        2694
*  DETAIL      NiRClientHandle: invalid data from server 'host2' during
*              route completion
*  COUNTER     3
***********************************************************************

End of the code.

Background and Further Analysis

Check the version of the SAProuter on the server side and update the program if necessary.

SNC not active for a forwards connection

The log file contains the following entries:

Client Side
`Thu Jun 14 17:16:40 2007 CONNECT FROM C18/ host 10.66.66.90/30891 (host1.company.corp)` `Thu Jun 14 17:16:40 2007 CONNECT TO S18/10 host 10.18.211.3/3299 (10.18.211.3) (p:CN=D039768, O=SAP-AG, C=DE)` `Thu Jun 14 17:16:40 2007 CONNECT ERR S18/10 forwarding route failed NIESNC_FAILURE` `Thu Jun 14 17:16:40 2007 DISCONNECT C18/10 host 10.66.66.90/30891 (host1.company.corp)`

Server Side
`Thu Jun 14 17:16:40 2007 CONNECT FROM C9/- host 10.18.211.3/1168 (host3.wdf.sap.corp)` `Thu Jun 14 17:16:40 2007 DISCONNECT C9/- host 10.18.211.3/1168 (host3.wdf.sap.corp)`

SAProuter Error Message on Client Sire

Syntax Syntax

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host3'
*  ERROR       SNC processing failed:
*              SNC not enabled
*
*  TIME        Thu Jun 14 17:16:40 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -104
*  MODULE      nisnc.c
*  LINE        566
*  DETAIL      NiSncOpcode: NISNC_REQ
*  COUNTER     2
***********************************************************************

End of the code.

Background and Further Analysis

The SAProuter on the server side has not activated SNC. Restart the SAProuter on the server side with the option -K mysncname.

SNC not active for a backwards connection

The log file contains the following entries:

Client Side
`Thu Jun 14 17:08:19 2007 CONNECT FROM C9/ host 10.66.66.90/30883 (host1.company.corp)` `Thu Jun 14 17:08:19 2007 CONNECT TO S9/17 host 10.18.211.3/3299 (10.18.211.3)` `Thu Jun 14 17:08:19 2007 CONNECT ERR S9/17 NIESNC_FAILURE on 'SAProuter 39.1 (SP3) on 'host3''` `Thu Jun 14 17:08:19 2007 DISCONNECT S9/17 host 10.18.211.3/3299 (10.18.211.3)`

Server Side
`Thu Jun 14 17:08:19 2007 CONNECT FROM C12/- host 10.18.211.3/1119 (host3.wdf.sap.corp)` `Thu Jun 14 17:08:19 2007 CONNECT TO S12/20 host 10.66.66.91/3253 (host2)` `Thu Jun 14 17:08:19 2007 CONNECT ERR C12/20 NIECONN_BROKEN on 'SAProuter 39.1 (SP3) on 'host3''` `Thu Jun 14 17:08:19 2007 DISCONNECT C12/20 host 10.18.211.3/1119 (host3.wdf.sap.corp)`

SAProuter Error Message on Client Sire

Syntax Syntax

***********************************************************************
*  LOCATION    SAProuter 39.1 (SP3) on 'host3'
*  ERROR       SNC processing failed:
*              SNC not enabled
*
*  TIME        Thu Jun 14 17:08:19 2007
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -104
*  MODULE      nisnc.c
*  LINE        586
*  DETAIL      NiSncOpcode: NISNC_ACC
*  COUNTER     4
***********************************************************************

End of the code.

Background and Further Analysis

The SAProuter on the client side has not activated SNC. Restart the SAProuter on the client side with the option -K mysncname.

More Information

SNC - Secure Network Communication

Option -K <mysncname>