Differences when installing 8.2 from scratch and updating 8.1 to 8.2

(imported topic written by SystemAdmin)

Hello,

I went through an issue when installing BES 8.2 onto my production platform as trying to enable any site opened an error window with the following message (see attachement.)

As a previous 8.1 version didn’t display this error when enabling a site, I was able to update it to 8.2. This time, no error was displayed when enabling a site. But a few side effects appeared, the most annoying one being forced to enter the operator’s password for each action :frowning:

So I decided to test more carefully both solutions:

  • on a VM named fltems81 I installed BES Server 8.1.617 with its own license. I then updated the server to 8.2.1093, then installed the console and agent.
  • on a VM named fltems82 I installed BES Server 8.2.1093 with its own license, then installed the console and agent.

(Both VMs have the same kind of configuration, Windows Server 2008 R2 with a static IP on the same subnetwork; on both VMs I let BES install its own SQL Server instance.)

Obviously I got the same results as before i.e. when connecting the console on fltems82 I systematically get an error message when trying to enable a site, whereas I have no problem when I enable a site on fltems81 (which–yes it’s kind of difficult to follow me–runs actually the same version of BES.) I use only the first ‘admin’ operator account I created on the servers.

So I had a look first at line 586 of wizards.js:

584: function EnableExternalSite( siteURL )

585: {

586: external.EnableExternalSite( siteURL );

587: }

It does not talk to me much but googling about “bigfix externalsite” led me to .exfm files.

And here I noticed differences between both installations. On fltems81 there are two directories that don’t exist on fltems82 : C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\bfsites\actionsite_0_4 and 0_5. Both directories contain 130 .exfm files which are related to TEM sites.

Now if I transfer a few .exfm to my workstation, I’m able to add them to Bigfix console with Tools / Add External Site Masthead. After the importation I can enable the corresponding site without any error message. (But I’m not sure if it actually works fine after this operation.)

So (if anybody followed me to this point) do you know what process is in charge of creating or downloading these .exfm files on the server and why it fails on a clean 8.2 installation? It would help me a lot!

Thank you by advance,

Pierre-Yves

(imported comment written by BenKus)

Hi Pierre,

This might be related to a licensing issue that was recently fixed… Can you try again with 8.2 and see if it is fixed?

Ben

(imported comment written by SystemAdmin)

Hi Ben,

Thank you for your fast answer.

I reverted my 8.2 VM back before BES installation but now when I run the server setup I get the following error when the installer tries to generate the masthead from my BESLicenseAuthorizationFile:

‘key values mismatch (class CertificateDoesNotMatchPrivateKey)’

so I can’t get further.

I’ll try to get a new BESLicenseAuthorizationFile and I keep you informed.

Regards,

Pierre-Yves

(imported comment written by SystemAdmin)

Hi Pierre-Yves,

Do you still have the problem, i.e. getting an error message when trying to enable a site with a fresh 8.2 install ?

I also have exactly this problem since beginning of december and still haven’t solved it. I recreated my BESLicenseAuthorizationFile several times but always the same problem at the end.

Regards,

(imported comment written by SystemAdmin)

Hi David,

I created a new BESLicenseAuthorizationFile and now I’ve got a different error message when trying to enable any site:

“There was an error enabling the site. It appears your server is not able to connect to IBM’s content servers. Please check the internet connection (including proxy settings) and try again.”

However my fltems82 VM does have internet connectivity, I’m able to reach any IBM or external Web site from it. Maybe the problem comes (yet) from the ‘IBM’s content servers’ themselves? How can I check?

Regards,

Pierre-Yves

(imported comment written by SystemAdmin)

Hem… OK. I restarted the server (the whole VM I mean) a few times without any success.

But some lines in BESrelay.log were confusing:

Tue, 10 Jan 2012 13:54:43 +0100 - 2160 - Database Connection failed: Database Error:

Microsoft

SQL Native Client

SQL Server

Cannot open database “BFEnterprise” requested by the login. The login failed. (37000:4060)

Microsoft

SQL Native Client

SQL Server

Login failed for user ‘NT AUTHORITY\SYSTEM’. (28000:18456)

Tue, 10 Jan 2012 13:54:43 +0100 - 2148 - Connection failed: Database Error:

Microsoft

SQL Native Client

SQL Server

Cannot open database “BFEnterprise” requested by the login. The login failed. (37000:4060)

Microsoft

SQL Native Client

SQL Server

Login failed for user ‘NT AUTHORITY\SYSTEM’. (28000:18456)

Tue, 10 Jan 2012 13:54:43 +0100 - 2160 - Will retry LDAP refresh in 00:15:00

Tue, 10 Jan 2012 13:54:43 +0100 - 2148 - Disconnecting from database; will reconnect in 10 seconds.

Tue, 10 Jan 2012 13:54:44 +0100 - Secure Server Thread (2164) - SecureServerThread::WaitForSigningKey Error: Database Error:

Microsoft

SQL Native Client

SQL Server

Cannot open database “BFEnterprise” requested by the login. The login failed. (37000:4060)

Microsoft

SQL Native Client

SQL Server

Login failed for user ‘NT AUTHORITY\SYSTEM’. (28000:18456)

Tue, 10 Jan 2012 13:54:44 +0100 - 2156 - Connection failed: Database Error:

Microsoft

SQL Native Client

SQL Server

Cannot open database “BFEnterprise” requested by the login. The login failed. (37000:4060)

Microsoft

SQL Native Client

SQL Server

Login failed for user ‘NT AUTHORITY\SYSTEM’. (28000:18456)

Tue, 10 Jan 2012 13:54:44 +0100 - 2156 - Disconnecting from database; will reconnect in 1 minute.

Tue, 10 Jan 2012 13:54:44 +0100 - 2152 - LicenseUpdater database connection error: Database Error:

Microsoft

SQL Native Client

SQL Server

Cannot open database “BFEnterprise” requested by the login. The login failed. (37000:4060)

Microsoft

SQL Native Client

SQL Server

Login failed for user ‘NT AUTHORITY\SYSTEM’. (28000:18456)

Tue, 10 Jan 2012 13:54:45 +0100 - Main Thread (1364) - Error updating replication server list: Database Error:

Microsoft

SQL Native Client

SQL Server

Cannot open database “BFEnterprise” requested by the login. The login failed. (37000:4060)

Microsoft

SQL Native Client

SQL Server

Login failed for user ‘NT AUTHORITY\SYSTEM’. (28000:18456)

Tue, 10 Jan 2012 13:56:01 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (2130708344)

Tue, 10 Jan 2012 13:58:36 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (-1895825265)

Tue, 10 Jan 2012 13:59:51 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (59588232)

Tue, 10 Jan 2012 14:02:13 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (59588232)

Tue, 10 Jan 2012 14:06:13 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (59618056)

Tue, 10 Jan 2012 14:12:45 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (23343160)

Tue, 10 Jan 2012 14:22:45 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (23350912)

Tue, 10 Jan 2012 14:37:15 +0100 - LicenseUpdater (2152) - LicenseUpdater download failed: Windows reports unknown failure (23350912)

And after that the very last line was repeating apparently each time I tried to enable a site.

After this I just tried to restart only the BES services and yes! this time I can enable any site from the BES console. No more error message in the BESrelay.log.

Maybe the BES services start too fast when the server reboots–before the SQL Server has a chance to start correctly. Replacing Automatic by Automatic (Delayed) in some BES services could simply fix my issue. Let’s try again from the beginning :slight_smile:

(imported comment written by SystemAdmin)

I also have now exactly the same error messages as you at the BES Console and BESRelay.log

(imported comment written by SystemAdmin)

It’s OK now on my test platform.

The Windows service ‘BES Root Server’ Startup type has to be changed to ‘Automatic (Delayed Start)’ so that all SQL Server processes can start before BES tries to connect to it.

After a clean VM reboot, and when the BigFix Management site is available you can enable any site you want without any issue.

Note: The BigFix Management domain took a few hours today before being displayed. I already noticed that it takes some time after the server’s installation but today was much worse. However several errors appeared related to sync.bigfix.com downloads for approx. two hours so maybe they suffered some server failure?

I’ll update this question and close it when my production server with full SQL Server 2008 is reinstalled.

(imported comment written by SystemAdmin)

I confirm, it works by delaying the “BES Root Server” service.

Thanks Pierre-Yves

(imported comment written by SystemAdmin)

My production is OK too now. Case solved, thanks to BigFix’s team who solved the licensing issue.

(imported comment written by dazman)

We had similar symptoms to the above. When we click on the links to enable various sites we were getting the following error “There was an error enabling the site. It appears your server is not able to connect to IBM’s content servers. Please check the internet connection (including proxy settings) and try again.”

We resolved this by:

  • Having a domain Windows account with web access to start the Gather AND the BES Root Server services. Two BES services ! (instead of System)
  • Setting the value of _BESGather_Comm_UseDownloadService = 0

Restarting the TEM server. All aok.

Daz