DSA Server Upgrade Failing - Error 08004: 911 Database 'MASTER' does not exist (v11.0.6)

1

Background: We are currently upgrading our BigFix environment from version 11.0.2.125 to 11.0.6.137. The primary Root Server upgraded successfully without any issues. However, when running the exact same installer on our DSA (DR) Server, the InstallShield Wizard fails during the configuration phase.

The Error: The installer throws the following popup error and rolls back:

Database Error: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Database 'MASTER' does not exist. Make sure that the name is entered correctly. (08004: 911)

Environment Details:

  • BigFix Version: Upgrading to 11.0.6.137

  • SQL Server: Remote/Custom IP (10.xxx.xxx.xxx) using a custom port (19444).

  • Collation: Suspected Case-Sensitive (CS) collation, hence why the uppercase MASTER is being rejected while lowercase master would normally succeed.

Troubleshooting Steps Already Performed: We suspected the installer was pulling an uppercase MASTER string from a configuration file or login property, but we have verified and corrected the following:

  • Windows Registry: Checked HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\Enterprise Server\Database. The Database string is correctly set to BFEnterprise (not MASTER).

  • ODBC System DSNs: Checked both 32-bit and 64-bit System DSNs (e.g., bes_bfenterprise). The "Change the default database to:" checkbox is unchecked. It is not hardcoded to uppercase MASTER. (We are correctly ignoring User DSNs).

  • SQL Login Properties (SSMS): We ensured the following three accounts have their Default database explicitly set to BFEnterprise and have both the public and sysadmin server roles ticked:

    1. The sa account.

    2. The NT AUTHORITY\SYSTEM account.

    3. The specific Windows User Account executing the installer (whoami).

  • OS Permissions: The setup .exe is actively being "Run as Administrator".

  • Network Connectivity: Verified successful Ping and Telnet to 10.xx.xx.xx on port 19444.

  • FillDB Logs: We see replication errors (Invalid object name 'webui.apcontrol' and version mismatch errors) on the DSA server, but we understand this is a normal symptom of the Primary being on 11.0.6 while the DSA is stuck on 11.0.2.

The Question: Despite explicitly setting the default databases to BFEnterprise and verifying the Registry/DSNs, the ODBC Driver 18 connection string in the installer is still somehow forcing a connection to uppercase MASTER.

Has anyone encountered this specific casing issue with the new ODBC Driver 18 during a DSA upgrade? Is there another hidden configuration file (like a besinstall.iss or similar temporary setup file) where this uppercase string might be cached or hardcoded?

Any insights would be greatly appreciated!

2

Wow, everyone, now this is how one writes a problem report.

I really, really wish I had something useful in response, but ...at least let me bump this back up to the top of 'new' on the forum.

2 Likes
3

Is the specific Windows User Account executing the installer also in the db_owner role (different from dbo)?

1 Like
4

Purely a shot in the dark, but I have occasionally seen differences between launching a program with “Run as Administrator” vs launching it from an Administrator command shell. It shouldn’t matter but… well… ¯_(ツ)_/¯

1 Like
5

Would suggest to verify the database of the secondary server meets the requirements about collation: