Using Tivoli Endpoint Manager 8.2.1310 components (Console, Server, Clients) and using Console, when selecting a computer in the list, an error occurs as follows:
Unexepected Error
The Tivoli Endpoint Manager Console has encountered an error and is unable to complete your request.
If you choose to ignore this error, the application may be in an inconsistent state. If you choose to quit, you will lose any unsaved changes.
The diagnostic message is:
Requirement Failure at BESFixlet.cpp:78 ( IsAnalysisTemplate() )
I presume that this is related to a custom analysis or fixlet, but I have not been able to identify the problematic item. If it is related to custom content, is there a process for locating the Analysis or Fixlet that is causing this error?
I am currently facing exactly the same issue with TEM 8.2.1372 (Server and Console). It affects only when selecting a Windows server in the list. I am also not able to identify the Analysis.
The root cause in my case seems to the GTS RBA (Runbook Automation) site. If I exclude this site, the Windows Computers are again visible and the error message does not appear. GTS RBA does not affect non Windows systems here even if enabled. Having GTS RBA disabled for Windows machines is only a work around and I am still searching for a real solution.
There are around 50 analysis in the new GTS RBA Site (Site Version: 14) that did not get activated automatically. Activating them Globally addressed the issue for us.
unfortunately, all analyses for the GTS RBA site (101 in my case, version 14) are activated, and it wasn’t me doing that. So that’s not the solution for me
I narrowed it at that time but was never able to absolute the cause before the end of the project. I did notice a DISA STIGs fixlet once appeared produce error as it contained a character such as single or double-quiote in one of it’s description fields, and when relevant, it generated the message when attempting to view the system. For general troubleshooting of this issue, In hindsight, I would disable each custom fixlet, or isolate one computer to a view for which the fixlets and analysis can be incrementally activated, as trial and error. If a custom fixlet with the issue is found, check it’s language content, and that it is appropriately fixlet content vs analysis. It may also be due to erroneous tattooed properties on the systems. This may be why new group containing a computer with no activated site / TEM data may be the right method to isolate it. Sorry for my delay in the response.
