04-24-2017 09:03 AM - edited 04-24-2017 09:04 AM
04-24-2017 10:27 AM - edited 04-24-2017 10:28 AM
This is not an error.
It is simply a warning that Windows has a firewall (it didn't always) and that some features may have problems getting thru.
It's NOT telling you that something is wrong.
I would just proceed. If some parts fail, you will get an error then (I think example finder is one). When that happens, you have an opportunity to open a hole in the firewall.
But I would leave the firewall intact until you actually have a problem.
Blog for (mostly LabVIEW) programmers: Tips And Tricks
08-21-2025 04:45 PM
Okay, so I paid a ton of money for software not to get answers that 'truly' don't answer the paying user's concern. The code exmp69 IS actually causing the problem, at least by blocking Windows Services from letting us "Start" Ni Device Loader. From within Win Services, the Firewall has been Disabled and so has Defender, but the Win system is still blocking the Start of the Ni Device Loader and thus MAX can't see the 9174 chassis, let alone see the card slots.
To many times throughout the Ni web site, I keep finding short non complete answers to very important questions. Yes, my software is old, but paid over 10k for it, to only use a few times and always be challenged by Windows.
IS there a config file that NI has for us to reset every Windows line item within the Service list, and anywhere else on the system to get the allowable configuration for use?
THx... a bunch of old rocket scientist in a garage loosing it... LOLOLOL Thx
08-21-2025 04:47 PM
08-22-2025 09:09 AM
@OldGuy007 wrote:
The code exmp69 IS actually causing the problem,
I am pretty sure you mean code expm69 instead.
You did not tell us your OS, but LabVIEW 2011 is ancient and not certified for any modern windows OS.