03-30-2012 04:40 PM
My Labview ProDev hangs on startup every time. I get a blank panel (Not Responding) and see that much communication goes back and forth over my network port. This goes on for 3 minutes or more, then it finishes and LabVIEW runs fine.
If I disable my network port, Labview starts and runs normally.
The web server is not enabled. This is a fresh install with defaults.
Solved! Go to Solution.
03-30-2012 07:26 PM
I've heard of this problem related to disconnected printers.
Look at http://lavag.org/topic/9700-labview-8-6-slow-startup-time/
04-04-2012 01:25 PM
Make that 6 minutes. Wow. This is unacceptable. Checking all the printers.
04-04-2012 01:43 PM
No extra printers. Still we get 6 minutes. Network light is lit throughout, but the task manager says no activity.
04-04-2012 01:59 PM
Fire it up and try "netstat" in cmdline. See where all the connections are open to. Might narrow down where the problem is.... printer, network share, database, ni.com...
04-04-2012 02:40 PM - edited 04-04-2012 02:52 PM
Are you setup with a license server? (Not pointing fingers, just trying to get more information).
These times definitely seem to point to nework connection timeouts.
What is the meaning of "network light is lit" (no traffic? losta traffic?)
During the wait, open a console window and type "netstat -n". Any unusual connections?
Get wireshark and capture all traffic from before opening LabVIEW until it opens.
(EDIT: I see snowmule already suggested netstat. I composed my message but then got sidetracked and did not post until much later)
04-04-2012 03:30 PM
The license is for Prof. Dev. Sys., and it's activated. I've just always installed and used the local NI License Manager. That program says I'm activated.
Running netstat - I've been able to account for every connection. No ni.com addresses.
04-04-2012 03:35 PM
Try two more tests:
Is there anything in the system log?
04-04-2012 03:54 PM
This company uses an external monitored & managed firewall, and the virus protection is remote and operated by IT as well. Novell logons, etc.
They give us test guys pretty much what we ask for. If I knew a port or protocol that needed to be unblocked they'd probably do it for me. But since I have no idea what's going on I don't know what to ask for.
Disabling web server, vi sharing..no change.
04-04-2012 05:59 PM
Apparantly the issue is related to the Novell connections.
At this location a Novell script maps 6 remote servers. If LabVIEW attempts to resolve those mapped drives in some way on startup it's bound to take a while. I tried logging in without processing the Novell logon [a local-only login] and the delay was eliminated.
I can certainly login without those servers attached and add them later, after LabVIEW starts.