Lee,
Yes…we’ve just checked that directory and that compliance_by_fixlets_1_2.js file is there. We’ve had that report in place for a few months along with the Fixlet by Computer Group report. They’ve both been great for us! The only recent changes we’ve made is updating to v9.5.4.
@DTMitchell, I just tested on my 9.5.4.38 server and it works correctly.
Does the other Fixlet by Computer Group report work?
Can you please turn on JavaScript console output for your browser (depending on what you use) and look at any messages that might be useful?
I sit next to and work with Daniel, Fixlet by Computer Group works just fine. I will look at the JavaScript console output and let you know what we find.
I’m actually not getting any messages in the console. We are using Firefox.
@DTMitchell, @rgarrett, and everyone else who might be using this report.
Looks like 9.5.4.38 (Patch 4) will break these reports.
We have included a security feature in Web Reports.
This change impacts the browser’s behavior when the server sends the “X-Content-Type-Options: nosniff” header on its responses. This is a good thing, however, Web Reports has omitted telling the Browsers in the response header for the JavaScript/CSS in our custom reports.
So the effect is that JavaScript and CSS will no longer will executed by the browsers.
For reference:
Unless and until Web Reports is being fixed, the simple workaround is to serve the report from another Web server.
I have loaded the script unto my personal server (not ideal) to get around this for now.
Just download these reports and Import into Web Reports as XML.
Fixlet Compliance by Content v1.3.bes (2.8 KB)
Fixlet Compliance by Computer Group v1.8.bes (2.7 KB)
Lee,
Thank you. Unfortunately though, after downloading these updated reports, both Robert and I have tested and are still getting just a loading screen. Is there anything, settings wise, that we would need to change??
We’ll continue to play around with…
hello @leewei, I wonder if you can help me, I downloaded and Applied the Fixlet Compliance by Content (v1.1)* and it works very well, thank you so much!!, now what we are a bit confuse (please take into account that we are transitioning from TPM into Bigfix, hence our expertise is limited) is the column that reads “applicable”…
in our scenario we:
computer -> computer name is “the name of one server only”
Content "the name of our baseline"
computers group: All computers (1) which makes sense as we only doing one server.
Click on generate report
the report generates
One of the fixlets “M17-SEP…XXXX” in the applicable column appears “4”
we were expecting the applicability of that patch to read 1 (just for the computer chosen) or 0 (if the patch is not applicable to the given computer)
questions:
A. Why applicable = 4 and not 1
If the applicability of the patch on that column makes reference to ALL servers in the state, how can I change it so that it only shows for that server and no more
I do understand that I could just simply remove the column to avoid confusion, but it will be cool to be able to show the applicability only for those servers chosen.
thanks.
@juliocesarperez17, when we select a baseline as content, the report effectively takes in all the Fixlets as part of the baseline. So the Applicable is in reference to the underlying Fixlets.
I am getting the same issue with the report. I am not sure if anyone can help me get this report running but when I run it in IE11 it kinda works but formatting is all messed up and when I try in Firefox it just stays at the loading screen. The zip was extracted to C:\Program Files (x86)\BigFix Enterprise\BES Server\BESReportsServer\wwwroot\ext-3.2.0.
Any help would be great.
There is a problem with a specific version of the BigFix Server.
What version do you have?
I am currently running 9.5.4.38. It will load in IE11 but with out formatting. Looks like a CSS issue to me but it will not load at all in Chrome or Firefox.
Here is the post that references the problem with 9.5.4 and the fix specific to that version that I had posted.
Thank you so much that worked like a charm. You did a great job putting this report together.
Still facing that issue as well, what exactly was the fix to get the report to work in Firefox?
When i try to import the following templates Fixlet Compliance by Computer Group v2.0.beswrpt or Fixlet Compliance by Content v2.0.beswrpt, i get the following error
Error in template function ReportChrome::Body: Database Error: [IBM][CLI Driver] CLI0109E String data right truncation. SQLSTATE=22001 (22001: 18446744073709451617)
What could be the issue?
When I import "Fixlet Compliance by Computer Group v2.0, it looks like the version of Flash Player now on our computers will not allow us to show the graphs/charts or anything visual properly. Will there be a new version coming out soon that will work with more recent versions of Flash Player or is there a new version out there that I am not aware of. We were using Bigfix version 9.5.2 and just upgraded to 9.5.9. In either versions, the graphs would not show up. Any suggestions would be most helpful.
Thanks,
Paul
Hi Leewei. Thank you for the reports. They worked great until last month (Sept 2023). We upgraded our BigFix system from 10.0.9 to 11.0, and they stopped working (giving a “loading…” screen. All the ext files are still there under “ext-3.2.0”. Using the browser debug, we got this:
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:75 Uncaught EvalError: Refused to evaluate a string as JavaScript because ‘unsafe-eval’ is not an allowed source of script in the following Content Security Policy directive: “script-src ‘self’ ‘unsafe-inline’”.
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:75:7443
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:75:18401
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:75
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:75
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65 Uncaught TypeError: Cannot read properties of undefined (reading ‘prototype’)
at Object.extend (webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65:1413)
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:95:31
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:95
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:440 Uncaught TypeError: Ext.WindowGroup is not a constructor
at Ext.ux.window.MessageWindowGroup (webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:440:15)
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:454:48
Ext.ux.window.MessageWindowGroup @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:440
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:454
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65 Uncaught TypeError: Cannot read properties of undefined (reading ‘prototype’)
at Object.override (webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65:1738)
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:1399:5
override @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:1399
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65 Uncaught TypeError: Cannot read properties of undefined (reading ‘prototype’)
at Object.extend (webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65:1413)
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:1825:30
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:1825
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65 Uncaught TypeError: Cannot read properties of undefined (reading ‘prototype’)
at Object.extend (webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65:1413)
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:2823:33
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:65
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:2823
webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:3536 Uncaught TypeError: Ext.onReady is not a function
at webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:3536:5
(anonymous) @ webreports?ShortenedParams=b05b90b2b9a6f2d7a2abbca13cc12ed7c4b15fa8:3536
Can you please help? TIA