Unable to capture the registration ip of client

yorkly1 · May 4, 2022, 5:43pm

Good day All, I created an analysis to run the following query statements as shown below.

addresses of adapters whose (exists gateway lists of it) of network

registration subnet address of client

registration address of client

===========

Out of 10,000+ clients, there are about 125 clients are reporting and results from the various operating systems. It works well for majority of the clients running similar operating systems. It is hard to determine which specific OS is causing the issue. I believe that something to do with the besclient process is unable to query the above statements for unknown reason.

See screenshot attached. Any suggestions on diagnose this issue? Thanks. Please advise.

trn · May 5, 2022, 7:12am

If you hover over an <error> indication in the console a pop-up will give you a hint as to what is wrong.

Also, not all inspectors work on every OS - the reference for network adapter (https://developer.bigfix.com/relevance/reference/network-adapter.html) shows that gateway list is supported on Windows, but does not mention any other OS

yorkly1 · May 5, 2022, 1:51pm

I do have similar OS servers that works well. See below.

It does not seem to relate to BES Client version either. See below

How can I fix it?

trn · May 5, 2022, 3:24pm

‘The operator “gateway lists” is not defined’ is because gateway lists is only supported in Windows

The singular expression error is because your relevance expects exactly one result and will error if it gets zero or multiple results. Recode to

registration subnet addresses of client

registration addresses of client

yorkly1 · May 5, 2022, 6:44pm

Thanks Trevor. About “singular expression error”, most of these servers in question do have 1 single or multiple IPs listed. See screenshots from the not working servers.

And a working sample server also have multiple IPs as well. See below.

It does not seem to be related to single or multiple IPs causing that error.

ctan · March 17, 2023, 8:17pm

I believe this is caused when there are more results for that field than BF can handle.

The magic number is 16. More than 16 records causes BF to return no values.

atlauren · October 8, 2026, 1:30am

2026, reporting in.

I see this behavior of registration address of client reporting an error on multiple OSes, and no correlation between number of addresses on the client. I see it on machines with only one address, multiple addresses, on or off VPN... I've yet to suss out a correlation.

Q: operating system
A: Win11 10.0.26100.9457 (24H2)
T: 8.000 ms

Q: version of client
A: 11.0.5.204
T: 8.000 ms

Q: exists client whose (exists registration address of it)
A: False
T: 8.000 ms

Q: registration address of client
E: No inspector context.
T: 7.000 ms

Q: (exists addresses of it, (exists gateway of it) as string| "None", loopback of it) of adapters of networks
A: True, True, False
A: False, False, False
T: 32.000 ms

Why does registration address of client sometimes fail? In an analysis that happens to report it, I see the failure on about 20% of reporting machines.

JasonWalker · October 8, 2026, 2:27pm

E: No inspector context.

That's a property that is not known to the Fixlet Debugger itself, you have to send this query to the active running client using the debugger option 'Evaluate Using -> Local Client' or the equivalent options in BigFix Query app.

The Fixlet Debugger by default runs outside of the active client, so it's not subject to CPU throttling and it can run on systems that don't even have an installed client. A side-effect of that is that some things (like the current registration, selected server, subscribed sites, etc.) are not available and you have to switch the debugger to 'Local Client' context so it sends the query to the running client instead.