API error loading fixlet

system · February 7, 2014, 5:43pm

(imported topic written by EduardoBarbosa)

Hi,

I’m not 100% sure if this is the correct place on the forum since this problem is with the API+patching management.

We recently upgraded TEM server to 9.0.835 and the API to 9.0.649 (that seems to be the most recent version available here:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/BigFix%20Platform%20API
)

All actions that we deploy using the same code we have for 2+ years works fine with the exception of fixlets that are patches or updates.

The part of the code when I make the fixlet loading:

fixlet.Load(siteID, fixletID, username, password);

                if (fixlet.DiagnosticMessage.Length != 0)



                    throw new Exception(fixlet.DiagnosticMessage);

It throws an exception with the following message: “HTTP Error 35: SSL connect error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number”.

Strange thing is that making the same deployment using the TEM management console works just fine for the same api.

Can anyone give me a hint on what’s going on ?

Thanks in Advance

Eduardo Barbosa

AlanM · March 5, 2014, 8:52pm

(imported comment written by AlanM)

BES Support site has fixlet 1696 for upgrading the Windows Platform API to 9.0.835 so that fixlet should have become relevant after upgrade. Did it not?

system · March 5, 2014, 8:57pm

(imported comment written by EduardoBarbosa)

Hi Alan,

I just received that information from IBM support team after opened a ticket about this issue.

The fixlet is not relevant (maybe because the API is on a development box and not on server) and the usual link I mention above does not have this version.

To get this API version I need to install a previous API version on server to get it ?

Regards

Eduardo Barbosa

AlanM · March 5, 2014, 9:36pm

(imported comment written by AlanM)

The fixlet doesn’t only look on the server for the information so as long as there is a client on the machine the API is running on it should work.

The fixlet works by checking the install of a previous API version yes, so if there isn’t one properly installed that could be an issue. Also if you are running an evaluation license the fixlet won’t become relevant.

You could download the item (the link is in the fixlet actionscript) and apply it manually if you like as well.

system · March 5, 2014, 9:50pm

(imported comment written by EduardoBarbosa)

The problem is that 1696 fixlet is not visible at all and the last API visible is the 8.2.1312 and the Applicable computer is another endpoint.

So I cannot see the url to download the latest version at all.

This is not an evaluation version server.

Can the upgrade to version 9 trigger licensing issues that is making this fixlet not visible ?

How can I troubleshoot this issue ?

Thanks

Eduardo Barbosa

AlanM · March 5, 2014, 10:00pm

(imported comment written by AlanM)

If you are in the BES Support site, you can click in the console at the top “Show Non-Relevant Content” and then you should be able to see the fixlet

The download path is: http://software.bigfix.com/download/bes/90/BigFix-BES-ServerAPI-9.0.835.0.exe

The client running on the machine also has to notice your server has updated by re-registering which can take up to 6 hours after upgrade (by default)

system · March 6, 2014, 1:18am

(imported comment written by EduardoBarbosa)

That has helped a lot and was able to update the API.

But now a different error has occur on the same line when loading the fixlet:

“HTTP Error 28: Timeout was reached: Connection timed out after 10000 milliseconds”

You can see it on the attached screenshot.

Thanks

Eduardo Barbosa

AlanM · March 6, 2014, 1:47am

(imported comment written by AlanM)

You’ll need to give more information to support now as they will need to ask for logs etc.

system · March 20, 2014, 3:15am

(imported comment written by Bhushan Chirmade)

Hi Eduardo,

Did you find solution to your issue? We are also facing the same issue after upgrading to TEM 9.0.787 version. I tried lot of other ways to trust the certificate but of no use. IBM is also struggling to find out what is going on. Please let me know if you find solution to this issue.

Regards,

Bhushan

system · March 20, 2014, 6:37pm

(imported comment written by EduardoBarbosa)

Hi Bhushan,

After updating to the 9.0.835 API (url do download above on this thread) has solved the initial error.

Still working with IBM support on the HTTP 28 Timeout Error.

Regards

Eduardo Barbosa

system · March 20, 2014, 7:33pm

(imported comment written by EduardoBarbosa)

Hi Bhushan,

After updating to the 9.0.835 API (url do download above on this thread) has solved the initial error.

Still working with IBM support on the HTTP 28 Timeout Error.

Regards

Eduardo Barbosa

system · March 20, 2014, 4:42am

(imported comment written by DaveLangridge)

Thje API page has bneen updated with the later versins of the API that you require. Pelase download the one at the same versionlevel as your TEM and retry.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/BigFix%20Platform%20API

You will also find that the BESfileimporter1.2 will not work either as the TEM database version is now too high for it. I ahve opened a bug to have this updated as well

bug 62370

Thanks

Dave Langridge BEM

IBM L2