I am useing Bigfix 11.0.4. When trynig to update to 11.0.5, The preupdate ask me for my user and password for the DB and fail with ouot it with error:
***
Database Error: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Cannot open database "BFEnterprise" requested by the login. The login failed. (37000: 4,060)
[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'DOMAIN\SERVERBIGFIX$'. (28000: 18,456)
I didnt’ found anywhere where it is configure with which user to use and where “SERVERBIGFIX$” is configure.
I looked for files like “fillDB” and other I saw on google and looked in the registery… Where can I found exectly to which db name on which server and with which user it is trying to login?
That would be the Domain account for your server - which indicates your ODBC connection is configured to use 'Windows Integrated Authentication', in which case the connections will be made using the "Log On As" account for the Services; when they are configured with the default of 'LocalSystem', this COMPUTERNAME$ account is what is used for the SQL connection.
If you want to connect with a service account (named user) and Windows Integrated authentication, you would change the 'Log On As' account for the BESRootServer, BESFillDB, BESGatherDB, and BESWebReports Services to use that account for logon.
To change the credentials for the BigFix database connection, run the following steps:
Open the registry key on main server.
Update the credentials:
For "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\Database", change "User" and "Password" values as required.
For "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\FillAggregateDB", change "Username" and "Password" values as required.
Restart the BigFix Services (ie. BES Root Server, BES FillDB and BES Web Reports services)
4.Note:* After the BES FillDB and BES Web Reports services are restarted, the "Password" values are obfuscated.
Alternately, you can update the credentials using the BES Admin tool. For example:
Hi Jason, Thanks for the reply. Sadly, I think there is strange problem with the DB configuration on my server. I couldn’t find anything in the registery under those keys. Also can’t find any thing on th files under bugfix. Yet, The DB is up and everythig work… I think I will have to investigate a little to understand whats going on here,
Are you sure that there is explicit configuration at all? We don’t have one for example. If you don’t then the connection is automatically made with the account that is configured to run the respective windows services. Also, worth noting that the recommendation is to run upgrades with account that has SA access to the SQL server - for example, that is not allowed on our side permanently but for upgrade we request temporary SA rights for the svc account that is configured to run the services with and we “run as” the installers with that account (the account would probably also require admin rights to the OS itself, as software installs usually do). Hope it helps you.