I am trying to configure IBM BigFix replication server (DSA). after installation complete I am getting below error.
Replication connection attempt failed for server ServerName: Database Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user Domain\User’. (28000:18456)
both servers SQL/IEM services are running domain user account.
I am able to telnet between primary & secondary server via port 1433
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\FillDB> added domain user name and password.
Antivirus also disabled for testing purpose.
System DSN tested with same domain account.
both the server SQL version are the same (SQL 2012)
So I know somewhere I am missing something. need help to resolve the issue
That is certainly a strange case, and it sounds like you’ve already checked everything I would think of.
Any piece of the password that might cause the client to have trouble parsing it (like embedded nulls, Unicode text, something like that)?
– Oh yeah, maybe “the backslash in registry” issue? On my DSA I’m not using Domain accounts for replication, so I’m not certain…but maybe you need to enter the credential as “domain\\username” in the registry?
Oh ya registry entry also included…Even I have changed system DSN for BES_ enterprise from NT authentication to SQL authentication and restarted IEM servers and checked IEM admin tool but I am getting the below error.
Fri, 07 Aug 2015 13:36:25 +0530 – 772 – Unexpected exception: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Hi yuvarajdass, did you find any resolution to your problem ? I am facing the same issue and i have verified the things that you have already mentioned. Still I am facing the same challenge.
yes…by sql admin i am able to authenticate,i want to change to NT authentication…I checked with below guide and ran odbcad32.exe and change the congiguration of bes_bfenterprise but no luck
Assuming your BES Server services are running in the default of LocalSystem, first verify the System account is authorized to log on to SQL natively. Easiest way to do that is to open a system command prompt with the Microsoft Sysinternals tool ‘psexec’, as in Psexec -s cmd.exe
Then, use sqlcmd.exe to connect to the database (I don’t recall the sqlcmd syntax but it’s pretty straightforward).
If that works, then you’ve verified the System account can access sql. It looks like you’ve checked the DSN, but be sure to check both 32- and 64-bit DSN via both
\windows\system32\odbcad32.exe
And
\windows\syswow64\odbcad32.exe