Are there any pre-reqs for running the QnA Fixlet debugger?
I’ve upgraded to v8 and whenever I try and start “D:\Program Files\BigFix Enterprise\BES Console\QnA\FixletDebugger.exe” I get an error from the C++ runtime library (see attached screenshot - if attachments are working now).
The server that I’m trying to run this on is running Server 2003 XP2 and is also the main BES servers too (if that makes any difference).
The versions of C++ on this server are:-
Microsoft Visual C++ 2005 &
Microsoft Visual C++ 2008 - x86 9.0.30729.17
Any idea’s?
Edit ##############
it appears that attachments are still a problem
The error message basically says:-
Runtime Error!
Program: D:\Program…
This application has requested the Runtime to terminate it in an unusual way .
Please contact the applications support team for more information.
jspanitz - thanks for the pointer, unfortunately, no help.
Noah, I did retry with a fresh download with no luck. It is working on my XP machine but not on either of my two Win2008 BigFix Server m/c’s. I’m almost certain that v7.2 worked OK.
I’m think that it’s down to my login access permissions. I asked a collegue who has full admin rights to try to run it and it worked for them.
I’ve been asked to re-pose this question given the frequency that I have to request admin privileges to the windows machines…
As per my last post, the Relevance Debugger seems to require at least one execution as an admin (as opposed to my usual power-user) - the question is why? What does it need to do / set on the first execution that it doesn’t need to do again? Can whatever it is doing be done during the installation?
I realize this thread is old, but I just went through this exact same issue. Two different versions (v7.x v 8.x) of the QnA / Fixlet Debuggers would crash with a “Microsoft Visual C++ Debug Library Runtime” error AND they would only crash when evaluating a relevance statement on the Graphical Breakdown tab AND only if the relevance evaluated all of the subkeys of the key stated below. However, I was definitely running the debugger using an account with admin rights.
Using SysInternals’s / Microsoft’s ProcMon utility, I found it would always crash after reading particular registry keys in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. I went ahead and uninstalled the software associated with those keys, which removed the keys entirely, and the relevance statement completed successfully without incident.
In retrospect, I probably should’ve looked at the security settings on those keys, or otherwise figured out what made those keys different.
I’m posting this info because this is obviously still a problem with the latest version of the Fixlet Debugger (I’m guessing it needs better error handling) and in case anyone else has similar issues, to let them know how and what to look for.
The BigFix Agents (and thus the relevance engine) expects to have full access to the local computer… If you run it as a non-privileged user, you will likely get incorrect results…
We should fix any crash bugs we have, but even if we do, you should run it as admin…
