New Nimsoft Server installation (7.x) fails to start

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Symptoms

During a fresh install of NMS server on Windows 2008 or Windows 2012 sometimes the last step of starting the Nimsoft Server fails.

Some customers report seeing messages such as:

1) Unable to start NMS server
2) Error communicating with controller

When you check the iaoutput.txt that is located in the c:\tmp\ai directory you see the following types of entries:

Sample 1:

2014-04-14 16:08:40,532 INFO  com.nimsoft.install.nimcommon.step.NMInstallationStepLogImpl:notifyStepComplete:46 [Thread-64]  - step_complete: notifier_id: nm_server_configure_controller
2014-04-14 16:08:40,532 INFO  com.nimsoft.install.nmserver.action.impl.NMServerConfigureController:doConfigure_preNMSStartup:382 [Thread-64]  - Successful configuration of pre-NMS modules.
2014-04-14 16:08:40,548 INFO  com.nimsoft.install.nimcommon.process.NimProcessExecutionUtils:execCommandLineCommon:60 [Thread-64]  - working_dir: C:\Program Files (x86)\Nimsoft
Nimsoft Robot Watcher installed.
CreateService failed - The account name is invalid or does not exist, or the password is invalid for the account name specified. (0x421)

Sample 2:

2014-04-14 16:08:40,969 INFO  com.nimsoft.install.nmserver.action.impl.NMServerConfigureController:waitForProbeToRespondCommon:2419 [Thread-64]  - Waiting for 'controller' probe to respond.
2014-04-14 16:08:42,108 WARN  com.nimsoft.install.nimcommon.probe.ProbeController:waitForResponse:349 [Thread-64]  - nametoip failed: (80) Session error, Unable to open a client session for 192.168.157.3:48000: Connection refused: connect
2014-04-14 16:08:45,649 WARN  com.nimsoft.install.nimcommon.probe.ProbeController:waitForResponse:349 [Thread-64]  - nametoip failed: (80) Session error, Unable to open a client session for 192.168.157.3:48000: Connection refused: connect
2014-04-14 16:08:49,175 WARN  com.nimsoft.install.nimcommon.probe.ProbeController:waitForResponse:349 [Thread-64]  - nametoip failed: (80) Session error, Unable to open a client session for 192.168.157.3:48000: Connection refused: connect
2014-04-14 16:08:52,700 WARN  com.nimsoft.install.nimcommon.probe.ProbeController:waitForResponse:349 [Thread-64]  - nametoip failed: (80) Session error, Unable to open a client session for 192.168.157.3:48000: Connection refused: connect

When you check Windows Services (services.msc) you do NOT see the Nimbus Robot Watcher Service.

For some reason the installer was unable to create the service.

keywords: install installation fails tcpip windows service Nimsoft Robot Watcher NimbusWatcherService CreateService failed Connection refused: Unable to start NMS server Error communicating with controller New Nimsoft Server (7.x) fails start

Solution

You can use the windows SC command line utility to manually create the service and then start it.

sc create NimbusWatcherService binpath= "C:\Program Files (x86)\Nimsoft\bin\nimbus.exe" start= auto DisplayName= "Nimsoft Robot Watcher" depend= "tcpip"

Once this is done you should be able to go into Windows services and then start the service as usual.




















keywords: install installation fails tcpip windows service Nimsoft Robot Watcher NimbusWatcherService CreateService failed Connection refused: Unable to start NMS server Error communicating with controller

Environment

Release:
Component: CAUIM