Error When Calling Up IGS (ListenerRfc: unknown interpreter)

[Former Member]

Hello,

in WAD we are using IGS server from exteranl server.

Today i am getting the following errors when opening the web templates.

Error When Calling Up IGS (ListenerRfc: unknown interpreter)

Chart CHART_1: Internal error when communicating with the IGS

What could be the reason of these errors?

please let me know.

Regards,

Ravi

[matthias_gemmel]

Hi Ravi,

as stated above it seems that Multiplxer and Portwatchers don't "hear" each other. A reason for that could be the mux ip entry in the igs.xml file. If this IGS is a result of a system copy this entry may be wrong.

When trying to use the HTTP administration with patch 16 or higher please note that you must specify administration="X" in the LISTENERHTTP entry in igs.xml as stated in note 959358.

Regards

Matthias

[Former Member]

Upgrading from IGS 7.000 to 7.002 fixed the IGS problem mentioned above.

[Former Member]

hi,

Transaktion SM59 --> TCP/IP-Connection --> search for: GFW_ITS_RFC_DEST and IGS_RFC_DEST --> change button --> at „ProgrammID“ IGS.XXX (XXX = your SystemNo.)

hope this helps!

Quan

[Former Member]

Thank you very much.

I met the same issue like that, and fortunately I got it over with your instruction.

Cheer up.

[arun_ev]

Hi Ravi,

Is this server configured with the correct rfc connection at the BW end? Check the RFC connection you have configured. Check that the SAP IGS service is started on your external system. Also use http://<hostname on which IGS is installed>:<http port through which IGS connects>. if u get a display then the IGS is fine. Execute graphics_charts_igs_test in SE 38. This should give u a graph output if IGS is running fine.

Regards,

Arun

PS:Award points if answer is useful

[Former Member]

Greetings -

Did you ever get resolution on this? I've installed IGS and can't get any graphics to work - same error.

I've gone through the OSS notes, google, etc. I've troubleshot the MUX and it looks like the Portwatcher isn't "hearing" the request.

excerpt from portwatcher 0 log:

[Thr 2057] Fri Dec 23 12:40:07 2005

[Thr 2057] [Portwatcher::Ping] Ping was unsuccessfull 1 times

seems like something real basic isn't right. Any ideas? These default ports - I run on AIX - 40080, 40000 and 40001 aren't supposed to be put into my services file right? Doesn't the http port hand off to these?

[Former Member]

Hi,

Have you resolved the problem I am also facing the same problem even after updating to patch level 16.

Extract of log file is

-

---

trc file: "/usr/sap/BP1/DVEBMGS00/igs/log/pw_bwprod01_0.trc", trc level: 1, release: "640"

-

---

[Thr 01] Thu Jul 27 18:58:28 2006

[Thr 01]

[Thr 01] [PortwatcherMain::Initialize] Internet Graphics Service 6400.0.16.0

[Thr 01]

[Thr 01] [PortwatcherMain::Initialize] Configuration:

[Thr 01] [PortwatcherMain::Initialize]

[Thr 01] [InterpreterManager::LoadInterpretersFromPath] Interpreter [/usr/sap/BP1/DVEBMGS00/igs/lib/bwgis_mt.

so] of type [BWGIS] loaded and enabled

[Thr 01] Thu Jul 27 18:58:29 2006

[Thr 01] [InterpreterManager::LoadInterpretersFromPath] Interpreter [/usr/sap/BP1/DVEBMGS00/igs/lib/xmlchart_

mt.so] of type [XMLCHART] loaded and enabled

[Thr 01] [InterpreterManager::LoadInterpretersFromPath] Interpreter [/usr/sap/BP1/DVEBMGS00/igs/lib/gfwchart_

mt.so] of type [CHART] loaded and enabled

[Thr 01] [InterpreterManager::LoadInterpretersFromPath] Interpreter [/usr/sap/BP1/DVEBMGS00/igs/lib/imgconv_m

t.so] of type [IMGCONV] loaded and enabled

[Thr 01] [InterpreterManager::LoadInterpretersFromPath] Interpreter [/usr/sap/BP1/DVEBMGS00/igs/lib/zipper_mt

.so] of type [ZIPPER] loaded and enabled

[Thr 2057] Thu Jul 27 18:59:29 2006

[Thr 2057] [Portwatcher::Ping] Ping was unsuccessfull 1 times

[Thr 2057] Thu Jul 27 18:59:59 2006

[Thr 2057] [Portwatcher::Ping] Ping was unsuccessfull 2 times

Please help

Thanks

Rajeev Goel

[former_member188975]

Hi Ravi,

It may be that the IGS engine is not functioning or is turend off due to any other changes on your external server. You may want to check with your Basis team.