LabVIEW very slow to open after system update

[Dec!an]

Hi,

After a recent system update & reboot, LabVIEW is now very slow to load.

If I have the patience to wait, the vi appears after ~30 minutes.

The PC is on a whitelisted lab network which includes *.ni.com network access.

If I change the network settings to DHCP and connect to our standard campus network, the vi will open in a normal amount of time.

I can then switch back to the lab network.

Any idea how I can debug this issue?
It may be that it is querying some license server, but I do not know what or where.

We had this issue in the past and used the above method of temporarily connecting to campus network, but with remote working now it is not so easy to do this.

Thanks,
Declan.

[billko]

If I recall correctly, this was sometimes caused by the LabVIEW News ticker on the bottom being enabled.  It would try to phone home, and it would keep on trying until it timed out minutes later.  I don't recall the timeout being so drastically long, though.  Is there any way to install a second NIC, so you can have both connections at the same time?

[Dec!an]

Thanks Bill.

Unfortunately, we are already using 2 NICs one of which connects to our lab network and the other which is used for a LAN to which our test equipment is connected.
The lab network is behind a firewall and each PC has a separate LAN.

There are no issues enabling specific known sites if I only knew what the "phone home" requirements are.

Declan.

[FireFist-Redhawk]

If the problem is what Bill mentioned, there's a token you can put in your LabVIEW.ini to disable the feed. Don't know if it will still try to phone home with the feed disabled but worth a shot...

GSW_RSSCheckEnabled=False

[Dec!an]

Thanks Andrew but unfortunately that didn't do the trick. 😞

I added updated the LabVIEW.ini file as directed and still observed same delay in starting.

We needed to resolve this, so we reverted to our old hack of temporarily connecting to campus network & then launching LabVIEW.

Still perplexed about this as I'd like to get to the bottom of it.

Declan. 

[FireFist-Redhawk]

What kind of license do you have? Go to NI License Manager and click on Network Licenses. If you are using a network license, the server hosting that license will be shown and you could whitelist it as well.

[FireFist-Redhawk]

Also, I don't know too terribly much about Wireshark as I've never had to use it, but I feel like you could use that to do some troubleshooting as well. Look at the network traffic when using the working connection and then using the nonworking connection and compare.