Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQ assistant does not work when not logged on with administrator rights

I am using Installing Labview 7.1 and NI-DAQmx 7.2

The DAQ assistant does not work when I am logged on to the PC with normal user rights, but does work when logged on to the machine with administrator rights.
Which part(s) of the registry or system files need to fully accesible by any user to make the DAQ assistant work?
0 Kudos
Message 1 of 9
(4,454 Views)
Hi there,

Please check the following link:

http://digital.ni.com/public.nsf/websearch/5300AA5B93A4CC9C86256E360000E955?OpenDocument

Regards,
Phil R
Applications Engineer
National Instruments
http://www.ni.com/support
0 Kudos
Message 2 of 9
(4,450 Views)
Can you update the link, please?
I have the same problem, How can I work with Labview and GPIB on a WIN2000-PC without administrator rights, witch directories must be open and others...???
0 Kudos
Message 3 of 9
(4,450 Views)
Hi, I found the same problem today. Would you please update that webpage again please???

Thanks.
0 Kudos
Message 4 of 9
(4,442 Views)
Hey all,

I do not have access to that link. This a known issue with the DAQ Assistant when you are not logged on as an administrator.

The DAQ assistant uses Measurement and Automation Explorer, and thus its use is based on the MAX directory. This workaround has been known to work in some instances:


Log onto the computer as an administrator
Browse to the C:\Program Files\National Instruments\MAX directory
Right-click the MAX folder and select Properties, Click the Security tab, and click the Add button
Type in the user name and click OK
Give the user Read & Execute, List Folder Contents, and Read permission
Click Apply and then OK

Good luck,
AnujD.
Message 5 of 9
(4,429 Views)

Hi all --

 

Same problem, only this fix doesn't seem to work on the newest version of MAX.  Have a clean install... LabVIEW 8.20 -- MAX 4.1.0.3001 -- Have given all registry keys and subkeys under HKEY_LOCALMACHINE\SOFTWARE\NATIONAL INSTRUMENTS  full control to everyone.  Ditto with anything in \windows or \program files directories per KnowledgeBase 2D6CK3QS (which solved it under previous versions for me).  Also looked at the above...

 

Also tried giving full access on VXIPNP_Alliance, PXISA, etc keys... .daq and .ini files in \windows... still no dice.

 

Everything for local administrators looks to work just ducky... so seems likely to be a permissions problem from files or regkeys again.

On a related note, do these programs log access errors at all asside from anything WinXP standard, for troubleshooting?

Any help?

 

Thanks in advance everyone!  Have an outstanding day! Smiley Tongue

 

Jason

0 Kudos
Message 6 of 9
(3,892 Views)
Actually, just one point of clarification... (Should have read a bit more closely)... I'm still trying just to get MAX to open up and scan devices...  I double click, but nothing happens when I'm non-administrator.  Works fine for administrator.
0 Kudos
Message 7 of 9
(3,889 Views)
Hi Jason,

I want to clarify you have done these steps.

The file is located at  C:\Documents and Settings\All Users\Application Data\National Instruments\MAX\Data for Windows XP/2000

you are looking for the file
config3.mxs

Make sure you are logged in as the Administrator. Go to the config.mxs or config3.mxs file described in the first paragraph. Right-click on that file and select Properties. Select the Security tab to view the permissions for the selected group. Select the appropriate user group and place a check mark in the boxes to Allow Modify and Write privileges for the user group and click OK. Now log out and log back in as a member of the user group. You will now be able to see all of the devices in MAX.

I am looking for other possible issues with Administrative privileges and MAX, but I just want to verify you have taken those steps.

Have a great day,

Michael D
Applications Engineering
National Instruments
0 Kudos
Message 8 of 9
(3,873 Views)

Michael --

Thanks for your reply and efforts -- It's _much_ appreciated...

I've got a resolution... Basically seems there are two additional files that seem now with the latest LV and max to need elevated privs to run as non-admin... Details on them below:

c:\windows\system32\mfc71.dll
mfc71.dll is the module that contains the Microsoft Foundation Classes (MFC) functions used by applications created in Microsoft Visual Studio

and

C:\windows\system32\msvcr71.dll
Description: msvcr71.dll is a module containing standard C library functions such as printf, memcpy, and cos. It is a part of the Microsoft C Runtime Library.

These showed as dependencies of nidevmon.exe.  Now things seem to work... At least MAX is opening and all test panels seem just ducky ...


Thanks again -- and have a spledid evening!

Jason

0 Kudos
Message 9 of 9
(3,863 Views)