Hostname issue on rfc connection

[Former Member]

Dear All,

When I'm executing transaction "SSAA", I've received an abap dump.

Below is the error log:

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

An error occurred when executing a Remote Function Call.

"CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=497#Unable to determine host address:

NiHostToAddr failed "

Status of connection.... "CODE=CM_PRODUCT_SPECIFIC_ERROR -1 -1 SAPCODE=497

CONV= "

Internal error code.... "RFC_IO5"

There is an error in the communication system. To clarify

and resolve the error, contact your system administrator.

Last error logged in SAP kernel

Component............ "NI (network interface)"

Place................ "SAP-Gateway on host idesdev / sapgw00"

Version.............. 38

Error code........... "-2"

Error text........... "hostname 'id3tdc00' unknown"

Description.......... "NiHsLGetNodeAddr: hostname cached as unknown"

System call.......... " "

Module............... "nixxhsl.cpp"

Line................. 223

The error reported by the operating system is:

Error number..... " "

Error text....... " "

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

I've check the start profile, instance profile and the default profile. All are showing the correct hostname and system number. The hostname in the server is also showing correctly. When I ping the localhost, it is showing the correct hostname as well.

Please advice where I can locate the wrong hostname to make the amendment.

Thanks.

Regards,

John

[Former Member]

We also found out today that the wrong server name that appears in the short dump comes from the entry in table TPFID, but I couldn't find out yet how to correct that one. I'm looking for any report to fill it (as we ran RSSTAT98 to fill SAPWLSERV with active instance info).

[Former Member]

I've also come across this problem - Table TPFID has the incorrect host details which causes various problems in my system. Please let me know if you found a way to change these values...

Thanks

[JPReyes]

I just reply to that on the new thread,

Regards

Juan

[Former Member]

SSAA Then choose Utilities -> Configure system landscape. Then decide which systems you want to administer with the System Administration Assistant. When you save the settings, a transport request is created. You also have the option of including only the new systems in the existing configuration. Transport this request to all systems and confirm the relevant settings in each system. Then you can administer all your systems using the System Administration Assistant.

can please check STMS is properly configured or not ?

Edited by: Samrat Dangeti on Apr 18, 2008 3:33 PM

[Former Member]

I think the suggestion given by Samrat might be even more useful.

Regards.

Ruchit.

[Former Member]

Dear All,

I'm running my system in IDES system. I created client 300 with the copy of SAP_ALL profile from client 000.

When I login to transaction "FINB_TR_DEST", I've noticed that a RFC is pointing to "id3tdc00". Thus, this makes me believe that this is a default rfc that comes with IDES.

By the way, I'm only running the system on 1 landscape (single system).

Maybe I've missed something while doing the post installation?

I'll try on the advice by Samrat tonight.

Thanks for all your advices.

Regards,

John

[Former Member]

Dear Samrat,

I've selected utilities >> configure system landscape.

However, I've received the error below:

Activate task area: Customer range

However, when i proceed to goto >> Tasks areas >> activate

And I've selected "BASIS" package as an example. When I click on "Copy entry", i've received "Activation Error".

As for STMS, I have created a virtual system (QAS) connected to my DEV. I've tried to transport some sample program, and the transport works fine, thus eliminating the problem with transport path issue.

Regards,

John

[Former Member]

Dear John,

I'm having the exact same problem on SSAA in IDES.

But I could activate the Task Area using package BV instead of Basis.

I found this entry in TADIR, under object name "bapicustomer_idrange", package is BV.

However, I still get that dump in program SAPLSENV.

I also ran the program RSSTAT98 to fill the table SAPWLSERV with the correct active instance, and then deleted the others... but I still get the same error.

Hope this helps.

Regards,

Erika

[JPReyes]

add that host "'id3tdc00" with its IP address to the hosts file at \windows\system32\drivers\etc\hosts.

Regards

Juan

[Former Member]

can you please check if all the RFC in sm59 configured under internal connection are showing same host name i.e, local host name also do test connection

(only guesswork)

Samrat

[Former Member]

Dear Samrat,

The internal connection are pointing to the correct hostname. Connection test is working fine.

Regards,

John

[Former Member]

can you please run rscoll00 program in se38 and check SSAA tcode

Samrat

[Former Member]

Dear Juan,

"id3tdc00" is the wrong hostname. The correct hostname should be "idesdev". I have added "idesdev" in the host file and the logs from SM59 shows that "idesdev" is pointing to the correct IP.

In default, instance and start profile, "idesdev" is listed as the hostname.

Samrat, I'm sorry if I didnt list out in detail. I can access "SSAA" tcode. However, when I click on the execute button, the abap dump is displayed.

I have executed "rscoll00" but the error still is coming.

Regards,

John

[JPReyes]

OOhhh i get you now....

Was id3tdc00 and old server or you localhost?... have you tried to delete and recreate the RFC?

Regards

Juan

[Former Member]

can you check the enry in table SAPWLSERV

[Former Member]

Dear Juan,

Hehe... Glad you noticed. 😃

I'm not very sure of "id3tdc00". It might have been from an old server. But I'm not sure. How shall I identify which RFC that I should modify?

Samcat, table "SAPWLSERV" is showing the correct hostname and system number.

Regards,

John

[JPReyes]

Well SSAA connects to systems configured in the tasks... so i think the problem might be that some of the tasks are pointing to a system that do not exist anymore... therefore the RFC is failing.

Hope that help

Juan

[Former Member]

Hello John,

SSAA links up with CCMS for a lot of its tasks. So the clue might be in RZ21 transaction. May be you can go to Rz21. Then from menu check Overview of segments.There may be you might find entry which is causing the error.

Regards.

Ruchit.