Issues during the configuration of Introscope EM 8

[former_member182034]

Dear experts,

I have installed the wily Introscope Manger 8 and the Introscope Enterprise Manager service is not running on window server 2008. please check the below logs.

Installation Summary

-------

Installation: Successful.

396 Successes

0 Warnings

0 NonFatalErrors

0 FatalErrors

when I tried to start the service then getting below issue.

E:\usr\sap\ccms\wilyintroscope>net start IScopeEM
The Introscope Enterprise Manager service is starting.........
The Introscope Enterprise Manager service could not be started.
A service specific error occurred: 1.

the status of SAP Note 1273028 is:

The requested SAP Note is either in reworking or is released internally only

Regards,

[TomCenens · Accepted solution]

Hi

The relevant SAP note you mention contains an attachment zip file that is needed to fix the issue (if that is the root cause).

If that's the case you have a few options:

• Wait till SAP releases the note again
• Create a customer message and request SAP to either briefly release the note again or check with them to get the necessary attachment available for download
• Find someone who has this Wrapper zip file ~might not be so easy

Best regards

Tom

[former_member182034 · Accepted solution]

hi tom,

now SAP Note 1273028 - Introscope 8 Release Notes is available. I just download the ServiceWrapperWindowsAMD64SAP.zip and put ServiceWrapper.jar and ServiceWrapper.dll files in lib folder.

when I am trying to start the service IScopeEM then getting below issue

Is the Introscope EM 32 system because the exe file(ServiceWrapper32.exe) and when I put the files ServiceWrapper_822.zip in lib folder then service started successfully.

how can I resolve this issue.

Regards,

[Former Member · Accepted solution]

Hello Abdul,

Try with these dll and jar file attached to sap note 1588773 - Wily Introscope 8.2 service fails to start on a 64-bit Windows system

BR,

SAPFan

[former_member182034 · Accepted solution]

hi dear,

I am getting below issue when I am trying to start the Introscope Enterprise Manager.exe

Wrapper Started as Service
Java Service Wrapper Standard Edition 32-bit 3.3.6
Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights Reserved.
http://wrapper.tanukisoftware.org
Licensed to CA Wily Technology for Introscope Enterprise Manager
Launching a JVM..
WrapperManager: Initializing...
Warning: Unable to load the Wrapper's native library 'ServiceWrapper32.dl
The file is located on the path at the following location but
could not be loaded:
E:\usr\sap\ccms\wilyintroscope\.\lib\ServiceWrapper32.dll
Please verify that the file is readable by the current user
and that the file has not been corrupted in any way.
One common cause of this problem is running a 32-bit version
of the Wrapper with a 64-bit version of Java, or vica versa.
This is a 64-bit JVM.
Reported cause:
E:\usr\sap\ccms\wilyintroscope\lib\ServiceWrapper32.dll: Can'tload IA 32-bit .dll on a AMD 64-bit platform
System signals will not be handled correctly.

while getting below error.

EMWebServer] The web server was unable to bind to a port.  This could be caused by another EM process binding to the same port.  Exception: Address already in use: JVM_Bind

Please find the attached file for complete log of IntroscopeEnterpriseManager.log

regards,

Message was edited by: M. Abdul Jamil

intrscope.txt.txt.zip

[Former Member · Accepted solution]

Hello Abdul,

Did service started finally ? Note contains info:

NOTE:  There may be a warning regarding ServiceWrapper.dll.  You can safely ignore this warning.

Provide system even log for the service.

BR,

SAPFan

[Former Member · Accepted solution]

Hi,

Looks like service started by port number is used by other process.

Check post https://scn.sap.com/thread/1885658

:

Hello Ejersbo,

Use the command : netstat -abn to check which process is occupying the WebView port (default is 8081).

You can stop the process which is occupying the port, or you can change this port to another:

1. Open the file config/IntroscopeEnterpriseMAnager.properties for editing.

2. Change the property introscope.enterprisemanager.webserver.port to a different port.

3. Save the file.

4. restart the EM to activate the change.

Kind regards,

Allam Drebes

BR,

SAPFan

[former_member182034 · Accepted solution]

hi Dear,

Please find the log of this service.

The Introscope Enterprise Manager service terminated with service-specific error 1 (0x1).

please also find attached logs of netstat-abn and xml view of IScopeEM.

port is configured in IntroscopeEnterpriseManager.properties

introscope.enterprisemanager.webserver.port=8081

please check the logs

EMService.log

INFO   | jvm 1    | 2013/03/07 23:06:14 |  ***PollingWorker - doTask(): sleep interrupted
STATUS | wrapper  | 2013/03/07 23:06:14 | <-- Wrapper Stopped
STATUS | wrapper  | 2013/03/07 23:06:15 | --> Wrapper Started as Service
STATUS | wrapper  | 2013/03/07 23:06:15 | Java Service Wrapper Standard Edition 32-bit 3.3.6
STATUS | wrapper  | 2013/03/07 23:06:15 |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights Reserved.
STATUS | wrapper  | 2013/03/07 23:06:15 |     http://wrapper.tanukisoftware.org
STATUS | wrapper  | 2013/03/07 23:06:15 |   Licensed to CA Wily Technology for Introscope Enterprise Manager
STATUS | wrapper  | 2013/03/07 23:06:15 | 
STATUS | wrapper  | 2013/03/07 23:06:15 | Launching a JVM...
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager: Initializing...
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager: 
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'ServiceWrapper32.dll'.
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           The file is located on the path at the following location but
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           could not be loaded:
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:             E:\usr\sap\ccms\wilyintroscope\.\lib\ServiceWrapper32.dll
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           Please verify that the file is readable by the current user
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           and that the file has not been corrupted in any way.
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           One common cause of this problem is running a 32-bit version
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           of the Wrapper with a 64-bit version of Java, or vica versa.
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           This is a 64-bit JVM.
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           Reported cause:
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:             E:\usr\sap\ccms\wilyintroscope\lib\ServiceWrapper32.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager:           System signals will not be handled correctly.
INFO   | jvm 1    | 2013/03/07 23:06:15 | WrapperManager: 

IntroscopeEnterpriseManager.log

3/07/13 01:30:38 PM ACT [INFO] [Manager.Extension] Locating EM Services...
3/07/13 01:30:38 PM ACT [INFO] [Manager.EMWebServer] EM webapps port: 8082
3/07/13 01:30:38 PM ACT [INFO] [Manager.EMWebServer] EM max server threads: 100
3/07/13 01:30:38 PM ACT [INFO] [Manager.EMWebServer] EM webapps directory: E:\usr\sap\ccms\wilyintroscope\webapps
3/07/13 01:30:38 PM ACT [INFO] [Manager.EMWebServer] EM webapps checks for new webapps every 60 seconds
3/07/13 01:30:39 PM ACT [INFO] [Manager.EMWebServer] Deployed web application: CA Styles r 2.1
3/07/13 01:30:40 PM ACT [INFO] [Manager.EMWebServer] Deployed web application: CA Styles R5.1.2
3/07/13 01:30:40 PM ACT [INFO] [Manager.EMWebServer] Deployed web application: CEM URL Adapter
3/07/13 01:30:40 PM ACT [INFO] [Manager.EMWebServer] Deployed web application: Introscope Online Documentation
3/07/13 01:30:40 PM ACT [INFO] [Manager.EMWebServer] Deployed web application: Introscope WebView
3/07/13 01:30:43 PM ACT [INFO] [Manager.EMWebServer] Deployed web application: Workstation WebStart
3/07/13 01:30:43 PM ACT [WARN] [Manager.Bootstrap] No Management Modules were loaded.
3/07/13 01:30:43 PM ACT [INFO] [Manager.HighConcurrencyTransportServer] Starting High Concurrency Transport Server
3/07/13 01:30:43 PM ACT [ERROR] [Manager.PostOfficeHub] Server failed to start listening for incoming default socket connections on port 6001
3/07/13 01:30:43 PM ACT [INFO] [Manager.EMWebServer] Shutting down EM Web Server...
3/07/13 01:30:43 PM ACT [INFO] [Manager.EMWebServer] EM Web Server shutdown complete.
3/07/13 01:30:44 PM ACT [INFO] [Manager] Shutting down data persistence subsystem
3/07/13 01:30:48 PM ACT [ERROR] [Manager] Can't delete data\1362679590000.spool even after 50 tries
3/07/13 01:30:48 PM ACT [INFO] [Manager] Shutting down the Isengard server
3/07/13 01:30:48 PM ACT [INFO] [Manager] Orderly shutdown complete.

Regards,

Message was edited by: M. Abdul Jamil

xml_view_Of_Service.txt.zip

netstat-abn.txt.zip

[Former Member · Accepted solution]

Hello Abdul,

Server failed to start listening for incoming default socket connections on port 6001

In second log this port  is used by java.exe app.

I've found note for Unix OS but I suggest to change the port number

1712079 - Wily Introscope Enterprise Manager fails to start on Unix due to conflict on port 6001

BR,

SAPFan

[former_member182034 · Accepted solution]

hi dear,

fyi..here. solman is installed on window server 2008 64bit.

Regards,

[Former Member · Accepted solution]

Hello M. Abdul,

I know that's note is for Unix but in the log is info about 6001 port is used by the other app. Please try to change it and re-run service again.

BR,

SAPFan

[Former Member · Accepted solution]

Hello M. Abdul,

I know that's note is for Unix but in the log is info about 6001 port is used by the other app. Please try to change it and re-run service again.

BR,

SAPFan

[Former Member · Accepted solution]

Hello M. Abdul,

I know that's note is for Unix but in the log is info about 6001 port is used by the other app. Please try to change it and re-run service again.

BR,

SAPFan

[Former Member · Accepted solution]

Hello M. Abdul,

I know that's note is for Unix but in the log is info about 6001 port is used by the other app. Please try to change it and re-run service again.

BR,

SAPFan

[Former Member · Accepted solution]

Hello M. Abdul,

I know that's note is for Unix but in the log is info about 6001 port is used by the other app. Please try to change it and re-run service again.

BR,

SAPFan

[former_member182034 · Accepted solution]

hi Dear,

I change the port but still same please check the attached.

Logs.txt.zip

[Former Member · Accepted solution]

Please check how many times you tried to start EM services (via services or command line).

Regards,

Roman

[TomCenens · Accepted solution]

Hi Jamil

Both 6001 and 8081 are in use by Java.exe. Which port(s) did you change in your configuration?

You should not use 6001 nor 8081. It looks like you changed 8081 into 8082 in your log file but what about the configuration for the 6001 port, did you change that also?

/usr/sap/wilyintroscope/config

IntroscopeEnterpriseManager.properties

introscope.enterprisemanager.port.channel1=6001

Best regards

Tom

[former_member182034 · Accepted solution]

hi Tom and other,

I just uninstalled the Wily introscop 8.2.4 and install the 8.2.3. there is not showing service(Introscope Enterprise Manager) in services.msc.

while log of wily inroscope

Connection Initiator listening...
 [Manager.MMHotDeployEntity] Will monitor E:\usr\sap\ccms\wilyintroscope\deploy for new files every 60 seconds
[Manager] Introscope Enterprise Manager started.

You can check the whole log from attached file and tell about service which is not created.

and I am also getting the below issue in Diagnostic Setup --> Managed System

The SMD Agent 'solman' hasn't been found!

Regards,

Logs.txt.zip

[Former Member]

Check <Introscope home>/logs/IntroscopeEnterpriseManager.log file for errors or attach it to message.

Regards,

Roman

[former_member182034]

Dear Roman,

Please find the attached logs.

Regards,

IntroscopeEnterpriseManager.txt.zip

IntroscopeEnterpriseManager_old.txt.zip

[Former Member]

Please attach screenshot from SOLMAN_SETUP -> Basic Configuration -> Landscape Data tab.

Regards,

Roman

[former_member182034]

Dear,

Please find the said attachment.

now Introscope service is started.

Please check below image.

Please also find the latest log.

Regards,

IntroscopeEnterpriseManager.txt.zip

[Former Member]

On windows you must have Introscope EM service registered as Windows service. Please check start/stop it from there.

First check that no other Introscope EM processes are running from Task Manager. After that try to start it as Windows service and check result.

Regards,

Roman

[former_member182034]

hi roman,

as i mentioned in my previous reply me that Introscope Enterprise Manager service is start/stop successfully. please check the InteroscopeEnterpriseManager.txt.zip from my last reply.

ax.nl.message.vm.not.loaded=LaunchAnywhere either could not find a Java VM, or the Java VM on this system is too old. LaunchAnywhere requires a Java 2 VM in order to launch Introscope.

Please send me link of JAVA 2 VM.

Regards,

Message was edited by: M. Abdul Jamil