Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ''. (28000:18456)

Usage and Config Platform
1

Hello all,

on Tuesday, I did an installation of Bigfix server on one of our Windows 2012 servers. All went fine.
After half a day, we could not add sites anymore. Therefore we did a full uninstall of the server/console/… and even reinstalled the server from scratch.

From that moment on, I have retried installation of Bigfix 10 times now but unfortunately it is not working anymore :frowning:

If I look in the BESRelay log file, we see this content :

Thu, 11 Feb 2016 12:42:32 +0100 - Main Thread (2836) - BES Root Server version 9.2.6.94, built for Windows x86_64, starting
Thu, 11 Feb 2016 12:42:32 +0100 - Main Thread (2836) - OpenSSL Initialized (Non-FIPS Mode)
Thu, 11 Feb 2016 12:42:32 +0100 - Main Thread (2836) - Using OpenSSL crypto library libBEScrypto64 - OpenSSL 1.0.1p-fips 9 Jul 2015
Thu, 11 Feb 2016 12:42:32 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:32 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:42:34 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:34 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:42:39 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:39 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:42:44 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:44 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:42:49 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:49 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:42:54 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:54 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:42:59 +0100 - Main Thread (2836) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:42:59 +0100 - Main Thread (2836) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:02 +0100 - 2252 - BES Root Server received stop request
Thu, 11 Feb 2016 12:43:03 +0100 - Main Thread (1672) - BES Root Server version 9.2.6.94, built for Windows x86_64, starting
Thu, 11 Feb 2016 12:43:03 +0100 - Main Thread (1672) - OpenSSL Initialized (Non-FIPS Mode)
Thu, 11 Feb 2016 12:43:03 +0100 - Main Thread (1672) - Using OpenSSL crypto library libBEScrypto64 - OpenSSL 1.0.1p-fips 9 Jul 2015
Thu, 11 Feb 2016 12:43:03 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:03 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:05 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:05 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:10 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:10 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:15 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:15 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:20 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:20 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:25 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:25 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:30 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:30 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:35 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:35 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:40 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:40 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:46 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:46 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:51 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:51 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:43:56 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:43:56 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:44:01 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:44:01 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:44:06 +0100 - Main Thread (1672) - Startup failed: error testing database connection: Database Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘’. (28000:18456)
Thu, 11 Feb 2016 12:44:06 +0100 - Main Thread (1672) - Will retry in 5 seconds
Thu, 11 Feb 2016 12:44:11 +0100 - Main Thread (1672) - Successfully connected to database
Thu, 11 Feb 2016 12:44:12 +0100 - Main Thread (1672) - Signature Algorithms: sha256, sha1
Thu, 11 Feb 2016 12:44:12 +0100 - Main Thread (1672) - Download Algorithms: sha256, sha1
Thu, 11 Feb 2016 12:44:13 +0100 - Main Thread (1672) - Successfully read server signing key
Thu, 11 Feb 2016 12:44:13 +0100 - Main Thread (1672) - Successfully read client CA key
Thu, 11 Feb 2016 12:44:19 +0100 - 3120 - Does not seem like the computer is joined to a domain. Windows Session Credentials Logon is unavailable.

The strange thing is the fact that the error lines state that the user is ‘’ (empty), eventhough we put the username during the installation.

With MS SQL server management we can enter the database without any issue from the same server.

Who can help us out with this issue ?

Greetings and thanks in advance,

Davy

2

As an addition: during the installation, the databases “BESReporting” and “BFEnterprise” do get created !!!

3

Did you try to connect through the ODBC drivers? 32-bit/64bit?
Check if this is working.

4

When you uninstalled BigFix, did you use the BigFix remover tool? If you didn’t, maybe there’s something in the registry left over that’s causing the issue?

–Mark

1 Like
5

Hey all,

Yes, ODBC is ok.
Yes, we used the uninstaller. We even started from clean scratch OS’s many times.

Yesterday late we installed a clean OS and a clean SQL Server 2012 on the same PC. Even in that case, the procedure fails !!

Two items I have been dreaming about this night, which might be faulty :

  1. Do we need to create the databases ourselves before starting the setup ?
  2. Could it be because I’m working with the installer of Patch6 ? Instead of maybe starting with the first non-patch version ?

Why am I doubting about item 1 above ? When I tried our FIRST installation on a fresh OS, in fact he UPGRADED the existing database which was still there from the test server. So in fact, this was seen as a non-clean install at that moment.

Please help out. Otherwise I think we need to make a PMR ;-(

Greetings and thanks in advance,

Davy

6

The only think I can think of is that the user account to log on in the DB does not have any creating rights, is locked, does not exist… ?

Our DB is a remote DB and we have 2 DBA’s who gave us the accounts etc. So can’t help you with the set up of the DB. But I know that they didn’t create the DB, so I don’t think you need to create them before the set up.

I did a fresh install with the 9.2.6 last week, so that isn’t a issue.

1 Like
7

I just tried option 2, version 9.2.5. Same issue … :frowning:
Our DBA’s tell me accesses are OK.

Question : if access would not be right, why is he able to create the two other databases correctly ?

8

Did you remember to install the client on the BigFix server machine as well? The client is required to be on the BigFix server machine in order for the server machine to function properly. Can you please check and let us know.

9

Hello, yes, I did.
But the issues are occuring BEFORE the client needs to be installed.
If I continue installing Console and Client after installing the server, the Console is almost empty. There are no sites at the bottom and even the Licensing sites is not available.

10

Hey guys,

quick follow up …
I retried the installation today. After installation has finished, I went into the ODBC DSN connections, in which I found 6 DSN’s. Three are 32-bit, three are 64-bit.

When I open each of them, I changed the login from NT admin to the sa user and password. Then I performed the steps described Here !

When I did this all, when starting the console, the missing parts are there…

As conclusion : I have the feeling the DSN’s are created wrongly during the installation, even if I entered SQL server with correct userid and password…

Greetings,

Davy

1 Like