Wily Enterprise Manager Service not Started in Windows 2008 Server

[Former Member]

Hi All,

Our Solution Manager is in EHP1 SP21 and OS-Windows 2008 Server.

We installed Wily Enterprise Manager 8.0. and found 1 non-fatal error in the installation log. The service is not starting.

However it works fine for Windows 2003 Server.

Can anyone encountered with the same kind of problem?

This is the latest log file information:

******************************************************

Summary

Installation: Successfulwith errors.

387 Successes

0 Warnings

1 NonFatalErrors

0 FatalErrors

Action Notes:

Execute ANT Script: Script:

Status: ERROR

Additional Notes: ERROR - E:\usr\sap\ccms\wilyintroscope\install\em.installer.exec.ant15.xml:425: Timeout: killed the sub-process

*******************************************

Thank you in advance.

Regards

Sanjai

[Former Member]

I have same issue:

Execute ANT Script: Script:

Status: ERROR

Additional Notes: ERROR - E:\usr\sap\ccms\wilyintroscope\install\em.installer.exec.ant15.xml:425: exec returned: 1

But, I'm getting this on Windws Server 2003 Enterprise x64 Edition.

Pl. suggest the fix.

Thanks/Rakesh

[Former Member]

HI There,

I have the same and followed the note: 1273028, also check the files ServiceWrapper.jar and ServiceWrapper.dll are present in folder lib C:\usr\sap\ccms\wilyintroscope\lib, if not download the

ServiceWrapperWindowsAMD64SAP.zip from the above mentioned note for Introscope EM 8.0.1.1 and ServiceWrapper_822.zip for version 8.2.

Hope it helps

regards

Hari

[Former Member]

Note 1273028 - Introscope 8 Release Notes resoved this issue.

Known problems in all Releases 8.x

2. Windows Server 2008 is not yet officially supported by CA Wily for the Enterprise Manager. If you want to install the Enterprise Manager anyway, set the "Windows 2003 compatibility mode" for the installer before launching it. To activate this mode, right click on the installer.exe file in the Windows Explorer, select tab "Compatibility", activate the check box for compatibility mode and select Windows 2003. If you do not set this, the installer will consider your OS as Unix and install shell scripts (no suffix) instead of batch files (.bat) and leave out some files for Windows Service registration.

If the windows service still fails to start please check if files ServiceWrapper.jar and ServiceWrapper.dll are present in folder lib. If not download them from attachment of this note.

The service should start although giving an error message regarding the ServiceWrapper.dll. You can ignore this error.