Failed to Synchronize error

(imported topic written by jlamb23)

I recently deployed the Bigfix client to four new servers. The machines showed up in the console, but all of the data said "not reported’. I checked the log file on the servers and viewed this error.

At 13:33:27 -0500 -

Starting client version 6.0.3.4

At 13:33:29 -0500 -

RegisterOnce: Attempting to register with ‘http://xxx.xxx.xxx.xxx:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=6.0.3.4&Body=1164227227&SequenceNumber=10&MinRelayVersion=6.0.0.0

Registered

At 13:33:32 -0500 - actionsite (http://xxx.xxx.xxx.xxx:52311/cgi-bin/bfgather.exe/actionsite)

FAILED to Synchronize - BigFix could not verify the authenticity of the site content.

Anyone know what this means?

(imported comment written by BenKus)

Hey jlamb,

Yes. This means that the BES Client cannot verify the digital signature for the actionsite (which is how the BES Client gets its actions, policies, settings, etc.)

The reason for this could be:

  1. The masthead of the BES Client does not match the masthead of the BES Server.

  2. The signing key files you are using as a BES Console operator have been revoked.

  3. The files in the actionsite have been corrupted in some form.

  4. Any other issue that might cause files on the BES Server to get corrupted on disk, in transit to the BES Client, or any other mismatch of signature information between the client/server.

To fix this, try:

  • Verify you have the right masthead in the BES Client installer folder, run BES Remove for the BES Clients, and reinstall.
  • Try re-propagating the master actionsite (send any action out with your master operator account).

If this still doesn’t work, please open a support ticket.

Also… You should upgrade your BES Clients from 6.0.3.4 as soon as you can. There are many known issues in that version and the newer BES Client builds have lots of fixes:

http://support.bigfix.com/bes/changes/fullchangelist-6.0.txt

Ben