LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NiAsstnt.exe hanging on "Initializing..." when starting DAQ Assistant for domain users only

Hello, when our users try to use LabVIEW and have authenticated via our domain they get stuck on "Initializing..." when they try to use the DAQ Assistant. If they authenticate locally they don't experience this problem. The process seems to be doing something in the background as the CPU usage of the process changes and occasionally there is a blimp in network activity from the parent process LabVIEW.exe, although this could be LabVIEW communicating to the license server. The problem is quite odd and I'm hoping to get troubleshooting advice. Thank you in advance for any help!

0 Kudos
Message 1 of 6
(2,715 Views)

If only you had attached the VI that exhibits this behavior, as well as a description of the Operating System (I'm guessing Windows 10 x64, but who knows?)...  We'd know what version of LabVIEW, we'd know how you configured the Dreaded DAQ Assistant, we'd know (perhaps) what you wanted the DDA to do, and other things.  But it's a waste of your time for me to just "guess" ...  [Note that attaching a static picture is almost worthless in this case].

 

Bob Schor

0 Kudos
Message 2 of 6
(2,683 Views)

My apologies for not including that data. I had been staring at it for over 4 hours yesterday. I must also apologize that I've never seen LabVIEW until yesterday. Anyway; yes! I can provide that data!

 

Our labs are running Windows 10 x64

Our domain is a Samba4 NT4 style domain 

Attached is the VI file provided to me from our team

The version of LabVIEW I'm testing with is version 18.0.1 SP1

NiAsstnt is version 18.5.0f0 as well as NI-DAQmx, NI-488.2, NI-RIO and NI-VISA

Ni IVI Compliance Package is version 18.0

 

The reproduction steps that I've been given is to double click on the labview-test.vi

Once loaded goto Windows > Show Block Diagram
In Block Diagram double blick on DAQ Assistant

 

For us, and I've reproduced this myself, if I login as a local Windows user the next window I see is Create New and I'm at a wizard

If however I login as a domain user I get "Initializing..." and it hangs there indefinitely

 

One other thing I've noticed while I've been investigating this is that the loading of plugins by LabVIEW.exe take slightly longer as a domain user but this may be a red herring.

 

Our team has also tested this with LabVIEW 19 on a fresh install of Windows 10 x64 and the same behaviour is observed.

 

If there is any other data I can obtain please let me know.

 

Thank you again for taking the time read my reply!

0 Kudos
Message 3 of 6
(2,625 Views)

I used Process Monitor by Sysinternals to try to debug LabVIEW. I haven't yet been able to figure out what call it's doing that is causing the hanging on "Initializing..." however; it is clear that LabVIEW is entering into an endless loop. I've attached the zipped process log. Any help would be very much appreciated. Thank you for taking the time to read my post.

0 Kudos
Message 4 of 6
(2,608 Views)

Your first step should be connecting to the device in NI-MAX. If you can't interact with the device in NI-MAX then you won't be able to interact with the device in LabVIEW.

0 Kudos
Message 5 of 6
(2,602 Views)

I apologize for the long delay in testing this. Here is the result from trying your suggestion.

 

As a domain user I'm able to load NI-MAX and I can see the device present on Communication Port 1 (COM1).

The behaviour is the same as a non domain user.

 

We also created a test environment and even without the device connected to it the NiAsstnt.exe process hangs on "Initializing..." if the user is logged in through the domain controller but if the user is logged in locally there is no problem.

0 Kudos
Message 6 of 6
(2,569 Views)