Data engine not starting on the HA hub.

Document ID : KB000008321
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The probe data_engine on the hub HA is not connecting to the database or the UMP portal also not able to open got an error 404.

Environment:
Any environment that is using Local System account on a remote server that needs access the UIM database.
Cause:

Using the domain user account on the probe data engine instead a SA user on the Microsoft SQL UIM database and the nimbus robot watcher on the HA hub or UMP portal is running as Log On as Local System account, when you start the probe data engine or wasp and get the string from the primary data_engine and try to connect to the Database the user that the windows will try to use is the user that is connected to the server. 

The message that will appears on the data_engine log and also the wasp log will be like this:

Open [Microsoft OLE DB Provider for SQL Server] Login failed for user 'CA\masru02$'.
de: COM Error [0x80040e4d] IDispatch error #3149 - [Microsoft OLE DB Provider for SQL Server] Login failed for user 'CA\masru02$'

 

Resolution:

add on the Microsoft SQL database the permission for the server as below:

USE [master];
CREATE LOGIN ['CA\masru02$] FROM WINDOWS;
GO
USE [msdb];
CREATE USER ['CA\masru02$] FOR LOGIN ['CA\masru02$]
ALTER ROLE [TargetServersRole] ADD MEMBER ['CA\masru02$]
GO

#########

Add to primary server, HA hub and UMP portal
CA\masru01$

CA\masru02$

CA\masru03$

Or if you don't want to add this you must open the Nimsoft Robot Wathcer go to Log On, choose the "this account" and choose the domain user that has the SA permission on the database.

The HA data_engine and also the wasp probe will always read and write information on the Microsoft SQL database.

 

Additional Information:

https://stackoverflow.com/questions/2806438/login-failed-for-user-domain-machinename

https://blogs.msdn.microsoft.com/sql_protocols/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections/