Problem with ODBC connections

Usage and Config Platform
1

(imported topic written by SystemAdmin)

Hi, second problem of the day (although this one has been happening for a long time),

We currently have a setup where the BES server is not located on the same server as the SQL database. This was running fine, but now we have a major problem that when the SQL server or the BES server is rebooted, noone can log onto the BigFix console and more importantly, no relays communicate with the server (or at least the information is not getting inputted from the server to the DB)

In ODBC it is currently set to use SQL Authentication to connect to the DB and this used to work fine. Now we have to force it to use NT Authentication to get the relays/server to communicate with the SQL server. Once they have communicated, we can then switch it back to SQL Authentication and our operators can log back in.

Does anyone know why this would happen?

Many thanks

Edit: We sometimes have to run a dos command to restart all of the BES relay services to kick start things into action.

2

(imported comment written by BenKus)

Hey Craig,

This appears to be related to some ODBC issue. Couple notes:

  • The BES Consoles connect directly to the remote database (they don’t connect directly with the BES Server unless they are sending out actions). Are you saying if you restart the BES Server, the consoles can’t connect anymore? If so, that is very strange.

  • The “FillDB” service on the BES Server is responsible for connecting to the database and putting results from clients into the database. It connects in the same way as the BES Consoles.

So it sounds like what happens is that the SQL Server won’t accept SQL Authentication connections after start-up… Which is also strange, but we can certainly investigate more.

I suggest you start a support case at enterprisesupport@bigfix.com and one of our support technicians will take a look at your configurations and see if they can find the issue.

Ben