Upgrade BigFix 9.0.876 to

I am upgrade BigFix 9.0.876 to it is install successful but some problem is coming after opening the IBM Endpoint manager console.
Error Message–
Logon Faild: Faild to connect to server: HTTP Erroe 35 : SSL connect Error: error : 14077102:SSL
routines:SSL23_GET_SERVER_HELLO:unsupported protocol.

Please tell me how to solve this problem.

You need to update your console to the same version. There is a folder on your BigFix server with the latest version.

1 Like

I don’t understand, please tell me brief.

Now you have the IEM server at level 9.2, but the console is still at level 9.0. To access the server you need to upgrade the console too.
To upgrade the console you need to copy the folder that you have on your IEM server under C:\Program Files (x86)\BigFix Enterprise\BES Installers\Console on your console machine and run the installer.

1 Like

This is the Error Message for after upgrading the , and tell me how to fix this problem.

Then I have uninstall BigFix-BES-Console- and install BigFix-BES-Console-9.0.876.0, After installing the lower version of console the IBM Endpoint Manager Console is running is fine.

I can’t understand the problem please let me know how to resolve the problem.

Tell me the full procedure of upgrade of Updated Windows Server/Console Components - Manual Upgrade Required - IBM Endpoint Manager version

That’s odd. It LOOKS like only your Console was Upgraded not the server itself.

A manual upgrade is usually required when the BES Server service is running with credentials other than LOCAL SYSTEM. You can see this in the Services list. This may have been configured for a variety of reasons.

  • DSA is configured. The BES server needs credentials to perform the required Database replication.
  • Remote Database. The database is installed on a separate server, and the BES server service needs credentials to access it.

I would agree, it looks like your primary DB did not actually upgrade. You would not be able to connect with an old console if this were not the case. Do you have a DSA server in your infrastructure? Might be possible that there was an issue with updating the primary and it never completed and then your DSA kicked in. And if you do have a DSA, from my understanding, that needs to be upgraded first. But we do not have our DSA set up yet so I’ve not experienced this.

I believe your looking for this article