When I’m trying to evaluate ANY client relevance using local client on my fixlet debugger, I’m getting the following error.
q: (not exists default value of key "Software\Policies\Mozilla\Firefox\PopupBlocking" of (current user keys (logged on users) of registry)) or (default value of key "Software\Policies\Mozilla\Firefox\PopupBlocking" of (current user keys (logged on users) of registry) as string != "1")
E: An error occurred while communicating with the client.
My machine is already reporting and I’m using a VPN and running the console on my local machine instead of logging on a server and running the console. I have checked BESClient service as well, it is working fine.
I’ve seen that when the debugger fails to communicate with the BES Client service to run in client mode. Maybe your local client is busy processing content, or is locked up processing a complex evaluation so is unable to release the API to the debugger? A restart of the client often fixes it.
Has your company blocked evaluating as client?
Try a really simple query like
Q: now
It’s possible to disable “evaluate as client” by disabling the Client Compliance API. I know of one customer who did this, it involved deleting a couple of folders from the BESClient directory or removing the registry entries for the query & response folders of the client.
If that’s the case you should talk to your deployment administrators about re-enabling your Client Compliance API if you need this functionality.
I tried this query as well and just like other queries, it is loading for 5 minutes, causing my Fixlet debugger to get stuck in not responding and then showing the same error.
I don’t think my company has blocked evaluating as client because my colleague is able to run queries using local client without any issues.