Services won't start

[Bob Gulien]

I installed a test-machine to facilitate a Sap-upgrade.
This machine is a copy of a production machine, but is not on the network.
It is stand-alone with a Windows XP workstation coupled via a switch to the L1000.
I cannot connect (with SAP) to the testmachine. I copied all the relevant
services in /etc/services. When I look on the regular machine, I see that the
services are listening on the ports:
tcp 0 0 *.sapmsL03 *.* LISTEN
tcp 0 0 *.diagmond *.* LISTEN
tcp 0 0 *.sapgw00 *.* LISTEN
tcp 0 0 yoda.sapgw00 156.5.64.8.3086 ESTABLISHED
tcp 0 0 yoda.sapgw00 156.5.64.8.3087 ESTABLISHED
tcp 0 0 yoda.sapgw00 156.5.64.8.3088 ESTABLISHED
tcp 0 0 yoda.sapgw00 156.5.64.8.3089 ESTABLISHED
tcp 0 0 *.sapdp00 *.* LISTEN

But on the testmachine none of the above services are present, at least not
with netstat -a
The nsswitch.conf is set to files.
Sap comes back with: partner not reached ("hostname", service sapdp00)


Extract of the /etc/service file on the testmachine:

sapdp00 3200/tcp # Sap
sapdp01 3201/tcp # Sap
sapdp99 3299/tcp # Sap
sapgw00 3300/tcp # Sap
sapgw01 3301/tcp # Sap
sapmsL03 3600/tcp # Sap
sapmsL02 3600/tcp # Sap
sapmsL01 3601/tcp # Sap
sapmsL00 3601/tcp # Sap

Can anyone shed some light on this

[Michael Tully]

I'm no expert with SAP, but you are starting network related ports. Without a network connection ports will not be able to listen. Why not give the system a different IP address and place it on the network?

What is this switch that you have this XP workstation connected?

[Bob Gulien]

The switch is a Catalyst 2820 (Cisco).
I have placed it out of the network, because it's an 1 on 1 copy of a production system. The way SAP works, you don't want 2 copies with the same name on the system.
The machine now has it's own little network, with just one workstation attached.

[Michael Tully]

When the system boots, what is mentioned in the /etc/rc.log for these background processes? Do they have any logging ?
Are there any entries in /etc/inetd.conf file that are missing? (/etc/services file does not start/stop services, it is merely a reference file)

You confused me with your statement about "but is not on the network"

[Bob Gulien]

Sorry about the confusion.
No I cannot find anything strange in the rc.log.
The inetd.conf is the same as on the donormachine.

[Steve Steel]

Hi

1) Is there anything in /var/adm/syslog/syslog.log

2)What about the sap logs such as

dev_rfc
r3monupd.log
writetrace.log

/usr/sap/trans/log

3)Try starting SAP manually


Steve Steel

[Jeff Schussele]

Hi Bob,

Do you have the appropriate SAP entries in the /etc/inetd.conf file on that test system?

As mentioned /etc/services is just a reference file, the actual commands that run for the connections have to be in the inetd.conf file.
Compare the entries on the Prod system to the test system.

Rgds,
Jeff

[Steve Steel]

Hi


There is no doubt that this is caused by the sap not starting . There must be a difference

On the working machine and then on the test machine
grep -il sap /etc/*

Check for the same files as answers and then check the contents

Then on the test machine
ll -d /*/sap if you do not know where the sap is installed

find sapinstalldirectory -name *.log

look for start???.log where ??? is the sap identifier

check it.
or post it and all other valid logs found .


SEE ALSO
http://www.openitx.com/archives/search.asp?l=sap-r3-basis&s=&sbj=partner+not+reached&f=&au=&t=


http://www.cul.de/data/sapr3pr.pdf


http://www.sapfans.com/sapfans/forum/basis/messages/9253.html


Steve Steel

[Steve Steel]

Hi

Sorry mistake

Log for startup can be in home of sap user

Example

$HOME/startsap??????.log

Want to see log.

Steve Steel

[Massimo Bianchi]

Hi,
'im thinking that your saprouter sting is wrong.


What did you put in the connection string ?
What is the SAP System Number ?


On the server itself, are you able to start a GUI (mabe the java one?)



Does SAP starts ???

ps -ef | grep disp+work
ps -ef | grep ms
ps -ef | grep so


I suspect that you did some wrong entry in the /sapmnt/SID/profile/DEFAULT and the other profiles.

Are there the same name as in productrion, using the virtual ones iif necessary?

A partner not reached can be caused also by firewalls, are you sure that there is no firewall on the XP (it is installed by default) and on your server ?

Massimo

[Bob Gulien]

Thank's for all the replies.
Inetd.conf doesn't start the sap services, so no entry's there. Sap must do this from somewhere else.
I will ask SAP about this.
Funny thing is that the logs don't mention any failure on starting services.
Every communication between workstation and server are OK, only the sapdp00 will not start to listen and so the workstation cannot connect.
SAp starts OK on the server (database, OS-collector and the instance).
I have installed saprouter. Works fine and sees the workstation....but still wants the sapdp00 service.