We are working through a new deployment with a always on MSSQL DB. For the Root Server/WebReports to work well on Windows connecting to this SQL, we had to enable the “multi subnet” checkbox in the ODBC settings. However, it seems that WebUI doesn’t use the same ODBC connections because the connection settings are stored in …\BigFix Enterprise\BES WebUI\WebUI\db_config.json and we see the WebUI having issues connecting to the DB.
{"server":"xxxxx","port":"xxxxx","user":"xxxxx","password":"xxxxx","database":"BFEnterprise","options":{"encrypt":false,"instanceName":"xxxxx"},"hostname":"xxxxx"}
Can any options be added (either to this file manually or in the WebUI when configuring the database) to allow for multisubnet connection support?
@cstoneba, good use case. Have you worked a support case with L2 yet regarding this matter? If not, that’d be the 1st step, but a BigFix Idea (aka RFE) may be needed. If you create a BigFix Idea, please make sure to post that here so that others can vote it up.
Yes, CS0202681 was created. Based on that result I can open an Idea if something doesn’t exist in the app today (but here’s hoping…).
1 Like
@dexdexdex any undocumented options for the WebUI database config that might pass-through for this?
1 Like
We tried MultiSubnetFailover=True on the WebUI config page, which did add it to the json but it appears SQL didn’t see it.
Here is the json it created with obvious masking.
{“custom1”:“MultiSubnetFailover”,“customValue1”:“True”,“server”:“blah.blah.com”,“port”:“1600”,“user”:"********************************",“password”:"*******************************************************",“database”:“BFEnterprise”,“options”:{“MultiSubnetFailover”:“True”,“encrypt”:false,“instanceName”:“MSSQLSERVER”},“hostname”:“blah.blah.com”}