Wily Introscope offline no matter what :-(

[symon_braunbaer]

Dear Experts,

we have a big problem - Wily Introscope is suddenly shown as Offline in step 4 of solman_setup.
I fixed many issues that might have caused this, but now he doesn't have any excuse and still shows offline!

Funny thing is, that with the same settings, it works flawlessly in the Development Solution Manager and we are having the problem in the production system!

Checked a ton of notes - one says to change the port which is nonsense, we have port 6001 and it is fine, I checked the connection with nc. Another note says to update Java for Introscope. But this is totally not clear for me:

1. We do not have the symptom 404 error in IntroscopeEnterpriseManager.log
2. As mentioned - it works perfectly in the development Solution Manager - with exactly the same software
3. Notes 2608940 and 2615293 speaks about replacing Java for Introscope, says that it only supports Java 11 and then gives links to Java 8 ?! Something smells here definitely...

And of course I tried all tricks like restarting Wily, attempting to Discover it again, etc.

Please kindly help us to solve this, as we have 3 systems we have to connect to the Solution Managers. Many thanks!

[symon_braunbaer]

P. S.: I decided to attempt to update the JVM of Wily according to note 2608940. And after that it was finally true, that Wily Introscope is unavailable - it didn't even start with the new JVM version !! All this is soooo frustrating 😕

[Vera_Jiang88]

Dear Customer,

[Vera_Jiang88]

Dear Customer, Could you please confirm if you have noticed any errors in the latest solman JAVA defaultTrace? Additionally, I would like to inquire if the wily webview is accessible in your browser.

[Vera_Jiang88 · Accepted solution]

Dear Customer, 

The 404 error in the defaultTrace is a known issue which has been recorded in KBA 2352112 - Enterprise Manager is offline in Infrastructure Preparation due to error 'com.sap.smd.introscope.em.IntroscopeException: http status code 404' - SAP Solution Manager 7.1 and 7.2. 

Best regards,
Vera Jiang 

[symon_braunbaer · Accepted solution]

Hello Vera,

MANY THANKS for letting me know to check the defaultTrace log files! This was the turn point in solving the problem!! Based on the error message, I found note 2352112 by myself on Friday and after taking a careful look at everything, Wily is now FINALLY detected as online in step 4! Thank you so much for helping me to solve this after such a long combat! The cause for the issue was anything but obvious...

[mamartins]

Which version do you have?

Version 10.8 have a slight difference regarding the installation procedures. Please check SAP note  3247270 - Introscope 10.8 Release Notes:

Please don't forget to update the Management Modules (without this procedure, SOLMAN will never be able to connect), and specially call the osgiindex.bat / osgiindex.sh scripts!

Other relevante SAP notes:

• 2557578 - How to install/uninstall Introscope Enterprise Manager 10.x - Windows/Unix
• 2512694 - How to correctly import/discover the Introscope Enterprise Manager (EM) into SAP Solution Manager
• 3297242 - Support Introscope EM 10.8 on SOLMAN_SETUP
• 2560977 - CA Introscope Enterprise Manager compatibility in SAP Solution Manager 7.1 / 7.2

[symon_braunbaer]

Hello Vera,

many thanks for your answer. I am gonna check the trace, as you suggested.
Nevertheless, Wily Introscope is perfectly available and fully usable in a browser.

Do you know where is the log for the Discover EM process in solman_setup ?

Thanks again!

[Vera_Jiang88]

Dear Customer, the wily EM is trying to connect to the solman JAVA system in the failed step, so it's suggested to check latest SOLMAN JAVA defaultTrace under /usr/sap/<SID>/<instance>j2ee/cluster/server0/log/default trace (latest).

[symon_braunbaer]

Dear Vera,

I had a look at the defaultTrace logs. They are flooded with this error message:

However, there is no problem to access the port on OS level:

Please explain