data-engine probe cannot be started

Document ID : KB000111934
Last Modified Date : 30/08/2018
Show Technical Document Details
Issue:
The data_engine probe has lost port and pid and cannot be started (red status).

Depending on the case, you can see similar lines to below ones logged in "data_engine.log" file (loglevel 5):

Scenario 1: "password" parameter is either missing or blank:

Aug 20 12:04:40:214 [10408] 3 de: [BasicCredentials::ReadConfiguration] Reading configuration from data_engine.cfg setup
Aug 20 12:04:40:214 [10408] 2 de:    provider=xxxxx
Aug 20 12:04:40:214 [10408] 2 de:    server=xxxxxxxxx,xxxx
Aug 20 12:04:40:214 [10408] 2 de:    database=CA_UIM
Aug 20 12:04:40:214 [10408] 2 de:    user=xxxxx
Aug 20 12:04:40:214 [10408] 2 de:    parameters=xxxxx
Aug 20 12:04:40:214 [10408] 2 de:    servicename=
Aug 20 12:04:40:214 [10408] 2 de:    port=xxxxx
Aug 20 12:04:40:214 [10408] 1 de: Connection Interface OK - ADO Version: 6.3
Aug 20 12:04:40:214 [10408] 1 de: Recordset Interface OK
Aug 20 12:04:40:214 [10408] 1 de: Command Interface OK
Aug 20 12:04:40:231 [10408] 0 de: [main] Open - 1 errors
Aug 20 12:04:40:231 [10408] 0 de: (1) Open [Microsoft OLE DB Provider for SQL Server] Login failed for user 'xxxxx'.

Aug 20 12:04:40:231 [10408] 0 de: COM Error [0x80040e4d] IDispatch error #3149 - [Microsoft OLE DB Provider for SQL Server] Login failed for user 'xxxxx'.
Aug 20 12:04:40:231 [10408] 1 de: Database script - processing 3 database scripts
Aug 20 12:04:40:231 [10408] 1 de: Database script - Module: [ NIS_BASE            ], File: [scripts\sqlserver_nis_base_create.sql], run check: [yes], run script: [ no]
Aug 20 12:04:40:231 [10408] 0 de: COM Error [0x800a0e7d] Unknown error 0x800A0E7D - [ADODB.Recordset] The connection cannot be used to perform this operation. It is either closed or invalid in this context.
Aug 20 12:04:40:231 [10408] 0 de: COM Error [0x800a0e7d] Unknown error 0x800A0E7D - [ADODB.Recordset] The connection cannot be used to perform this operation. It is either closed or invalid in this context.



Scenario 2: "password" parameter is present, but there are some password encryption errors logged:

Aug 21 13:48:20:906 [2956] 3 de: [BasicCredentials::ReadConfiguration] Reading configuration from data_engine.cfg setup 
Aug 21 13:48:20:906 [2956] 2 de: provider=xxxxx
Aug 21 13:48:20:906 [2956] 2 de: server=xxxxxxxx,xxxx 
Aug 21 13:48:20:906 [2956] 2 de: database=xxxxx
Aug 21 13:48:20:906 [2956] 2 de: user=xxxxx
Aug 21 13:48:20:906 [2956] 2 de: password=****** 
Aug 21 13:48:20:906 [2956] 0 de: (nimDecrypt) decoding of encrypted string failed. 
Aug 21 13:48:20:906 [2956] 0 de: (NimCryptographerCfgKeyReadEncryptedValue) failed to decrypt value. RC=1 
Aug 21 13:48:20:906 [2956] 0 de: Did not receive a valid connection string from data_engine (using cached: yes) 
Aug 21 13:48:20:906 [2956] 2 de: parameters=Network Library=dbmssocn;Language=us_english
Aug 21 13:48:20:907 [2956] 1 de: Connection Interface OK - ADO Version: 6.3 
Aug 21 13:48:20:907 [2956] 1 de: Recordset Interface OK 
Aug 21 13:48:20:907 [2956] 1 de: Command Interface OK 
Aug 21 13:48:20:944 [2956] 0 de: [main] Open - 1 errors 
Aug 21 13:48:20:944 [2956] 0 de: (1) Open [Microsoft OLE DB Provider for SQL Server] Login failed for user 'xxxxx'
Aug 21 13:48:20:944 [2956] 0 de: COM Error [0x80040e4d] IDispatch error #3149 - [Microsoft OLE DB Provider for SQL Server] Login failed for user 'xxxxx'. 
Aug 21 13:48:20:944 [2956] 1 de: Database script - processing 3 database scripts 
Aug 21 13:48:20:944 [2956] 1 de: Database script - Module: [ NIS_BASE ], File: [scripts\sqlserver_nis_base_create.sql], run check: [yes], run script: [ no] 
Aug 21 13:48:20:945 [2956] 0 de: COM Error [0x800a0e7d] Unknown error 0x800A0E7D - [ADODB.Recordset] The connection cannot be used to perform this operation. It is either closed or invalid in this context. 
Environment:
UIM 8.5.x
 
Cause:
This problem can be caused if data_engine.cfg file was corrupted or manually wrong edited.
Resolution:
There are 3 possible solutions available:

1- Try to open the probe configuration using IM or AC consoles and reconfigure the password;

2- Restore the data_engine.cfg file from a working backup;

3- If you have a lab/test environment, you can set the password in another UIM environment and then copy the password encryption string from the .cfg file from that environment.

If problem persists after executing these actions, please contact CA Support.