Dynamic Signal Acquisition

cancel
Showing results for 
Search instead for 
Did you mean: 

Why are Automation Explorer Test Panels only accessible to a sysadmin?

When running as the local system administrator on a WinXP Pro machine, I have no problems running the test panels in automation explorer and all my VIs load correctly when running Labview. However, on the same system when logged in as a regular user, the test panels are grayed out and when loading Labview apps I get numerous LabVIEW load error code 21 dialog boxes followed by a dialog listing all the Missing SubVIs. When using an older version of NI-DAQ (~6.5 if I recall correctly), the problem goes away. Below is the technical support form print out from the system in question.

Thanks,
BPD




National Instruments Technical Support Form (Version 3.1.0.3021)
Generated: Monday, April 04, 2005 4:56 PM Eastern Daylight Time

User Information:
Registered Owner:
Registered Organization:
Address:
City:
State:
Country:
Postal Code:
Phone:
Fax:
Email:

System Information:
Operating System(OS): Microsoft Windows XP
OS Version: 5.01.2600
OS Info: Service Pack 1
Processor: Intel(R) Pentium(R) 4 CPU 1700MHz / x86 Family 15 Model 0 Stepping 10 / GenuineIntel / 1699 MHz
Number of Processors: 1
Physical Memory: 1,572,336 KB RAM
Drive C:\ 98,685,508 of 117,210,208 KB free

NI Software Information:
CVI Run-Time 7.0.0.395
NI-DAQ 7.2.0f1
NI-DAQmx 7.2.0f0
NI-DSA 1.2
NI-488.2 Software 1.70
LabVIEW 7.1
Advanced Analysis 7.1.0
Analog Modulation 2.0.3.36
Application Builder 7.1.0
Database Connectivity Toolset 1.0.132
Digital Modulation 2.0.0.36
Express VI Development Toolkit 1.0
Internet Toolkit 6.0.0
PID Control Toolset 6.0
Report Generation Toolkit For Microsoft Office 1.1.0
Signal Processing Toolset 7.0.1
Sound and Vibration Toolset 2.0.0
Spectral Measurements 2.0.3.36
VIAnalyzer Toolkit 1.0
LabVIEW Run-Time 6.0
Measurement & Automation Explorer 3.1.0.3021
Measurement Studio 6.0
For Visual Basic
ActiveX User Interface 7.0.0.344
ActiveX 3D Graph 7.0.0.344
ActiveX DataSocket 4.2.2.1
NI-USI 1.0.2
NI-PAL Software 1.8.0.0
NI Spy 2.1.0.12
NI-VISA 3.1
visa32.dll 3.1.0.24
NiViSv32.dll 3.1.0.24
NiVisaServer.exe 3.1.0.35
NIvisaic.exe 3.1.0.35
viic_ext.dll 3.1.0.35
NiViAsrl.dll 3.1.0.24
NiViEnet.dll 3.1.0.35
NiViEnetAsrl.dll 3.1.0.35
NiVi488.dll 3.1.0.35
NiViGpvx.dll 3.1.0.35
NiGpvx32.dll 3.1.0.35
NiViPxi.dll 3.1.0.35
NiViRpc.dll 3.1.0.35
NiViUsb.dll 3.1.0.35
NiViVxi.dll 3.1.0.35
LabVIEW Run-Time 6.1
LabVIEW Run-Time 7.0
LabVIEW Run-Time 7.1
0 Kudos
Message 1 of 3
(6,896 Views)
I would advise upgrading to NI-DAQ 7.4. This release solves the permission issues as long as you use DAQmx. You can find it at http://search.ni.com/nisearch/nisearchservlet?nistype=default&filter=+%2BProductLine%3A41+%2BDownloadType%3A%22NI-DAQ%22+%2BVersion%3A%227.4%22+%2Bcontentformat%3Asoftwarelib&ddown=2

Good luck
0 Kudos
Message 2 of 3
(6,875 Views)
Thanks for the feedback. Unfortunately, I'm trying to solve the problem for systems with PCI-4551 and PCI-4552 boards which aren't supported by DAQmx. I am, however, also working with PCI-4772 boards on the same network, so maybe I'll try things out there while (Hopefully!) the full range of boards will get supported under DAQmx.

BPD
0 Kudos
Message 3 of 3
(6,868 Views)