snc/enable parameter problems

[Former Member]

Hello,

The basic problem that we are facing is oss connection (RFC connection?) to sap from Solution Manager. To solve this, we activated parameter snc/enable=1 accordin Activating SNC on the SAP System Application Server manual. Then we stopped solman and started it again. Now we are in a situation that we cannot open solman with sap gui. When opening solman we get next error message.

Time Mon Aug 06

Component NI(network interface)

Release 640

Version 37

Module nixxi_r.cpp

Line 8724

Method NiPConnect2

Return Code -10

System Call SiPeekPendConn

Error no 10061

Error text WSAECONNREFUSED: Connection refused

Counter 3

We are using SUSE 10 with Maxdb.

Kind regards

Jukka Vesterinen

[markus_doehr2]

just putting snc/enable to the profile will allow only SNC connections, from SAPGUIs as well as from external connection.

What you wanted to do (I assume) is to use SNC for the connection between the saprouter at SAP and YOUR saprouter, right?

--

Markus

[Former Member]

Hello Markus,

When we added the snc/enable to the profile and restarted the Solman, this caused us latest problem. SAPGUI don’t open Solman, but gives a error message mentioned earlier message. First we are looking forward to get access to our Solman system with SAPGUI and then we can concentrate to the connection problem between our Solman and SAP. How can we change the snc/enaple parameter value back to 0 without SAPGUI? Or is tehere something else we can do to get SAPGUI open?

Basically we want to use Solman to download patches and updates to our ERP 2005 system. RFC connection between Solman and ERP seems to be working ok. All test lights are green. We are facing problems with saposs connection (SM59) (/H/147.204.2.5/S/sapdp99/H/oss001).

Our systems are behind small firewall (Pix) which is using pat towards Internet. Inside net we are using private ip-addresses.

We are beginners with Sap systems and we appreciate very much your assistance.

Kind regards,

Jukka Vesterinen

[markus_doehr2]

If you enable SNC on the server, you need to configure all clients/sapguis to use SNC also. SNC is used for encrypting the data between systems, it´s not enough to just enable it on the server but all systems connecting must be made SNC aware too.

To create a connection between your SolMan and SAP you don´t need SNC on the SERVER.

--

Markus

[Former Member]

Hello Markus,

Thank you for your quick response.

We have renamed profile HSM_DVEBMGS00_haukka.BAK to profile HSM_DVEBMGS00_haukka and restarted sap. With this procedure we can have now assess to Solman with SAPGUI. So at the moment the parameter snc/enable is not in use in our Solman.

Now we can concentrate on connection problem with RFC Destination SAPOSS (SM59)

Target system OSS

Message server address: /H/194.39.131.34/S/sapdp99/H/oss001

Group EWA

Trusted system: No

Status of secure protocol (SNC) Inactive

Logon:

Language EN

Client 001

User S0004165646

PW status Saved

Password ********

This is what connection test gives us:

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: sapserv2a: route permission denied (195.170.151.44 to oss001, sapmsOSS

Error Details LOCATION: SAProuter 37.15 on sapserv2a

Error Details COMPONENT: NI (network interface)

Error Details COUNTER: 1259141

Error Details MODULE:

Error Details LINE:

Error Details RETURN CODE: -94

Error Details SUBRC: 0

Error Details RELEASE: 640

Error Details TIME: Tue Aug 7 08:56:08 2007

Error Details VERSION: 37

Kind regards,

Jukka Vesterinen

[markus_doehr2]

This is what connection test gives us:

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: sapserv2a: route permission

denied (195.170.151.44 to oss001, sapmsOSS

you can´t connect "directly" to sapserv3 but you need to use a saprouter. This saprouter must be known by SAP.

- Start transaction OSS1

- use the menu "Parameter - Technical Settings"

- enter there YOUR saprouter in "Saprouter on customers site"

- save

--

Markus

[Former Member]

Hello Markus,

Thank you for your quick response.

Actually we don’t have saprouter. Can we build up the connection to SAP without saprouter straight from Solman?

I have also tried connection from Solman to message server:

/H/147.204.2.5/S/sapdp99/H/oss001

Here is connection test error message according mentioned server:

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: timeout while pending for route completion

Error Details LOCATION: SAP-Server haukka_HSM_00 on host haukka (wp 3)

Error Details DETAIL: NiErrSet

Error Details COMPONENT: NI (network interface)

Error Details COUNTER: 72

Error Details MODULE:

Error Details LINE:

Error Details RETURN CODE: -12

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Tue Aug 7 11:11:25 2007

Error Details VERSION: 38

Kind regards,

Jukka Vesterinen

[markus_doehr2]

You NEED a saprouter...

check

http://service.sap.com/access-support

and the FAQ there.

Basically you need to open an OSS call if you chose one of the available possibilities, the SAP network team will then enable your saprouter to access their internal systems.

--

Markus

[Former Member]

Hello Markus,

Thank you very much for your advices.

I have now sent a fax (Remote Connection Data Sheet) to sap for opening oss connection (vpn) to our systems. This is under process so connection is not yet open.

I have also downloaded SAPROUTER_8-20001567.SAR file and unpacked it to folder /usr/sap/saprouter. Then we have made saprouttab file including following information:

P 10.0.0.206 194.39.131.167 *

P 194.39.131.167 10.0.0.206 *

When we try to start saprouter with command saprouter -r we get following error message:

• ERROR => CTrcOpen: fopen dev_rout

-

-

---

trc file: "dev_rout", trc level: 1, release: "700"

-

-

---

Wed Aug 8 13:41:17 2007

SAP Network Interface Router, Version 38.10

command line arg 0: saprouter

command line arg 1: -r

trcfile dev_rout

main: pid = 25056, ppid = 24308, port = 3299, parent port = 0 (0 = parent is not a saprouter)

***LOG Q0I=> NiIBindSocket: bind (98: Address already in use)

• ERROR => NiIBindSocket: SiBind failed for hdl 0 / sock 3

(SI_EPORT_INUSE/98; I4; ST; 0.0.0.0:3299)

• ERROR => main: NiBufServerHandleForAddr failed (rc=-4)

*****************************************************************************

*

• LOCATION SAProuter 38.10 on 'haukka'

• ERROR service '0.0.0.0:3299' in use

*

• TIME Wed Aug 8 13:41:17 2007

• RELEASE 700

• COMPONENT NI (network interface)

• VERSION 38

• RC -4

• MODULE nixxi.cpp

• LINE 3174

• DETAIL NiIBindSocket

• SYSTEM CALL bind

• ERRNO 98

• ERRNO TEXT Address already in use

• COUNTER 2

*

*****************************************************************************

Should saprouter start although the connection to sap is not jet opened?

Ystävällisin terveisin / Kind regards,

Jukka Vesterinen

[markus_doehr2]

> port = 0 (0 = parent is not a saprouter)

> ***LOG Q0I=> NiIBindSocket: bind (98: Address already

> in use) [nixxi.cpp 3174]

> *** ERROR => NiIBindSocket: SiBind failed for hdl 0 /

This means, that a saprouter is already running.

The saprouter and the "connection opening" don't relate with each other. The saprouter is the physical connection, opening the connection in the OSS is the logical one.

--

Markus