SAP service container not starting

[GoogleCodeExporter]

Hi

We have installed SAP connector(Cordys SAP R3 2.1.5.isvp) in the production 
environment which is on windows server 2008 64 bit, we also added all the 
required lib files and the jars required for SAP, still the the container is 
not getting started, i have also attached the log files

We have a development environment which has same configuration like 
production,but there it has no problem and it works fine. Also i came to know 
that the development environment is been connected  directly with SAP 
development Application and the production environment is been connected with 
SAP message severer.

Are there any changes/configuration to be made for SAP message server 
connection? 

Original issue reported on code.google.com by karthick...@simbustech.com on 18 Feb 2013 at 4:39

[GoogleCodeExporter]

Hi,

the below part of the log file tells that there is something wrong with your 
logon details. The connector failed to connecto to the SAP gateway. This might 
be either due to the port or the address of the gateway. To adjust that you 
need to modify the "SAP Application Server" connect string.

Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: 
SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
Connect_PM  GWHOST=10.250.2.72, GWSERV=sapgw01, SYSNR=01

LOCATION    CPIC (TCP/IP) on local host
ERROR       partner not reached (host 10.250.2.72, service 3301)
TIME        Sun Feb 17 20:19:44 201
RELEASE     640
COMPONENT   NI (network interface)
VERSION     37
RC          -10
MODULE      nixxi_r.cpp
LINE        8840
DETAIL      NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO       10061
ERRNO TEXT  WSAECONNREFUSED: Connection refused
COUNTER     1

Regards

Thomas

Original comment by te...@cordys.com on 18 Feb 2013 at 9:05

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi Karthick,

You should be able to provide a message server in the SAP application server 
field as well.
The port is typically derived by SAP from the system number, therefore it is 
3001 for your connection attempt. If you need a different port, you would need 
to specify a sap router string like for example
/H/host/S/service_port

The SAP application server field will accept such strings as well and parse 
them properly.

Regards

Thomas

Original comment by te...@cordys.com on 19 Feb 2013 at 9:46

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

If I recall correctly, you have to use a Dialog user.
Give that a try.

regards
Helmut

Original comment by hboec...@cordys.com on 19 Feb 2013 at 4:11

[GoogleCodeExporter]

re: ""partner not reached (host 10.250.2.72, service 3301)" here the port used 
is 3301 but it should take the port 3600"

That is not right. As you use sapgw01 the port to be used in indeed 3301.
Not sure if you know what effect your change in the "services" file will have.
But there should be an entry "sapgw01  3301/tcp".
On the SAP server you can verify if that ip address and port is actually bound 
by using "netstat -na" command.

Original comment by hboec...@cordys.com on 19 Feb 2013 at 4:20