External programs get error 1006 using local server name

[Former Member]

I have a brand new Solution Manager EHP1 installation on Windows 2003sp2/SQL.

The installation succeeded ok, but I cannot configure STMS.

The reason appears to be that external commands (i.e. tp) are not working correctly.

If I execute in SM49 the external command 'ENV' and use the default host, it fails with error 1006

If I specify the target host and use the 'short' name of the host, e.g. SAPSMT it fails with the same error

If I specify the target host and use the fqdn of the host e.g. SAPSMT.saproot.local it works ok.

If I specify the target host as 'localhost' it also works ok.

The 'HOSTNAME' command responds with SAPSMT

There is only a single NIC, so its not anything to do with multiple NICs.

I'm running the latest kernel and sapxpg now and it still acts the same.

Type 3 RFC destinations to SAPSMT work ok.

I can't really get anything else to fail: just external commands with the short name (or default) as the target.

Has anyone seen this before and have a solution or workaround?

I am almost sure it will be a windows configuration problem, but I can't see what it could be.

Thanks, Andy.

[former_member4224 · Accepted solution]

Hi Andy!

Take a look if the RFC in SM59 called CALLTP_WindowsNT is working.

Maybe this note can help you: 1093054 External RFC server program cannot be started

I know cases where the parameter parameters rfc/use_gwstart and rdisp/wp_auto_restart have solved similar situation.

The parameter rfc/use_gwstart is not documented. If you try implement it, you probably get the message that this "parameter cannot be checked." But this is normal.

[Former Member · Accepted solution]

Hi,

Well... I left it with SAP all this week. 3 separate consultants tried to work out what was going wrong - no conclusion.

Today I decided to give up on them. I tried rfc/use_gwstart=1 and it worked!

Thanks very much indeed. I am going to try to find out why this should be the case on a brand new installation.

Cheers, Andy.

[markus_doehr2]

> The reason appears to be that external commands (i.e. tp) are not working correctly.

Use two entries in the hosts file like

<ip> <hostname>
<ip> <full-qualified-host-name>

and add at least one empty line after the last.

Markus

[Former Member]

Hi Markus, THanks for the input.

I tried this, but it doesn't change anything, unfortunately. (after flush hostname buffers etc etc)

Andy

[Former Member]

Could you check if the cause is the following security enforcement ?

-

---

SAP Note 1406178 - Error 1006 occurs when you execute an external command

-

---

cheers !

PRADi

[Former Member]

Thanks Pradi,

I've checked that note. However, the security enhancement isn't active.

This is a brand new installation and no such change has been made.

I have separately tried implementing the security enhancement and then opening it up to all hosts, all users, but it didn't change the error message I receive, so I de-implemented it.

Thanks, Andy.

[Former Member]

Hi,

The Note 686765 ( Security check when you execute external commands) states that these checks are intrinsic with WAS 6.20 and to deactivate them you need to apply corrections (relevant to the WAS ) in Note 864152 - Exception SECURITY_RISK with external command.

Meanwhile I shall keep you posted if I could find some solutions..

with regards,

PRADi

[Former Member]

Thanks Pradi, I will take another look. However, if I use the hostname 'localhost' it works, and if I use the hostname 'SAPSMT.saproot.local' it also works - which suggests this is not the issue, since these too would be closed down by the security file.

Thanks, Andy.

[Former Member]

Ok. The issue should be that these external programs are not abled to reach the hostname 'SAPSMT'

could you pls provide the output of the following command ?

niping -v -H SAPSMT

If your entry in hosts file looks like the following :

IP address SAPSMT.saproot.local SAPSMT

Please check by setting this as :

IP address SAPSMT SAPSMT.saproot.local

cheers !

PRADi

[Former Member]

Hi Pradi,

there are no entries in the HOSTS file related to this.

I do think this is the right area: here is the output of niping, which is suggesting that the address lookup of the ip address goes to the fully qualified domain name rather than the hostname.

E:\usr\sap\SMT\DVEBMGS00\exe>niping -v -H SAPSMT

Hostname/Nodeaddr verification:

===============================

Hostname of local computer: SAPSMT (NiMyHostName)

Lookup of hostname: SAPSMT (NiHostToAddr)

--> IP-Addr.: 10.115.227.36

Lookup of IP-Addr.: 10.115.227.36 (NiAddrToHost)

--> Hostname: SAPSMT.saproot.local

Lookup of hostname: SAPSMT (NiHostToAddr)

--> IP-Addr.: 10.115.227.36

Lookup of IP-Addr.: 10.115.227.36 (NiAddrToHost)

--> Hostname: SAPSMT.saproot.local

If I add the hostname SAPSMT to the hosts file (together with the alias as you suggested), it then gives:

E:\usr\sap\SMT\DVEBMGS00\exe>niping -v -H SAPSMT

Hostname/Nodeaddr verification:

===============================

Hostname of local computer: SAPSMT (NiMyHostName)

Lookup of hostname: SAPSMT (NiHostToAddr)

--> IP-Addr.: 10.115.227.36

Lookup of IP-Addr.: 10.115.227.36 (NiAddrToHost)

--> Hostname: SAPSMT

Lookup of hostname: SAPSMT (NiHostToAddr)

--> IP-Addr.: 10.115.227.36

Lookup of IP-Addr.: 10.115.227.36 (NiAddrToHost)

--> Hostname: SAPSMT

However, having made this change and restarted, I still get the problem.

Thanks for the help, by the way.

Andy

[Former Member]

""there are no entries in the HOSTS file related to this""

you should be using a DNS to resolve hostnames then. You need to correct it there.

The correct entry would like : IP address HOSTNAME FQDN

You need to set this at the place where the hostname is being resolved (if not local hosts file, at DNS)

cheers !

PRADi

[Former Member]

Hi Pradi,

This is exactly what I now have in my hosts file, as per my previous reply.

i.e.

10.115.227.36 SAPSMT SAPSMT.saproot.local

I have restarted the SAP instance, but the problem remains even though now I would expect the name to be resolved from the hosts file rather than the DNS - so DNS should be taken out of the equation.

this same windows configuration works fine for SAP 4.7 systems running on the same platform, by the way, so the 7.01 kernel or basis layer is doing things differently, and having a problem with it.

Thanks, Andy

[Former Member]

An excerpt from SAP Note : 129997 - Hostname and IP address lookup

-

---

If you use DNS, you have to make sure that the rule is followed. This means, that the name lookup and the reverse lookup of IP addresses back into hostnames must be configured in your DNS server in the following way:

Each hostname must have an "A" record in the correct zone file that specifies the IP address that belongs to that host. It follows, that the hostname must not be an alias.

-

---

When there is such a strong recommendation, why to ignore this point ?

Also I observe your hostname in capital letters , please check if all profile/where relevant the hostname is maintained in same case ? For completeness you may verify the following notes:-

-

---

Note 23538 - Problems due to inconsistent host name notation

Note 611361 - Hostnames of SAP servers

-

---

cheers !

PRADi

[Former Member]

Hi Pradi, Yes, I take your point. I wasn't involved in the DNS setup, and didn't click that my own server name is an alias in the DNS and the fqdn is the real name. I will talk to the windows admins to see if they can switch that position.

thanks, Andy