During installation of?NMS 7.5 with MS SQL Server and named instances, during post configuration step, data_engine?application crash is seen in the event logs, then the installation fails.
Example output of appcrash below
Faulting application name: data_engine.exe, version: 220.127.116.11, time stamp: 0x51829655
Faulting module name: data_engine.exe, version: 18.104.22.168, time stamp: 0x51829655
Exception code: 0x80000003
Fault offset: 0x000000000018f682
Faulting process id: 0xa10
Faulting application start time: 0x01cf680582195877
Faulting application path: e:\nimsoft\probes\slm\data_engine\data_engine.exe
Faulting module path: e:\nimsoft\probes\slm\data_engine\data_engine.exe
Report Id: e5efc0c6-d3f8-11e3-80c1-0050568641e1
Faulting package full name:
Faulting package-relative application ID:
2014-05-05 12:21:41,425 WARN? com.nimsoft.install.nimcommon.probe.ProbeController:waitForResponse:349 [Thread-64]? - nametoip failed: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = 'data_engine'
2014-05-05 12:21:43,926 ERROR com.nimsoft.install.nimcommon.probe.ProbeController:waitForResponse:360 [Thread-64]? - Failed to communicate with probe 'data_engine' in the allotted time.
2014-05-05 12:21:43,926 ERROR com.nimsoft.install.NmsConfigurer:install:238 [Thread-64]? - Caught exception for configuring nmserver: null
This is seen with with named instances.
When specifying an MS SQL Server instance name during installation, it is not being written to the data_engine.cfg file correctly - most likely due to the backslash being processed incorrectly
If you?check the data_engine.cfg you will see that the name is wrong.
You can manually edit the?data_engine.cfg to include the correct database connection string,
When the installation process attempts to restart data_engine again, the installation?will progress correctly, deploying the remainder of the NMS probes or you can rerun the installation process again and the installation will progress correctly.