02-23-2006 01:10 PM
02-24-2006 05:32 PM
Hello,
That error usually occurs when you do not have administrator privileges. Since you do, I have a few questions for you to try to track down the problem. Are you running Resman from MAX or are you running it from the Resman.exe file (ie. from the Start menu)? What hardware do you have (what type of controller, etc)? Is it a VXIpc or a computer? Also, did you change versions of any drivers or MAX between now and when it was working properly? Sometimes the MAX configuration can't load because of driver version mismatches. One thing you can try is go into Program Files>>National Instruments>>MAX and move the "Data" folder to somewhere else on your harddrive. Then, try to open MAX again and run Resman. If you have configurations for your hardware in MAX already, be sure to just move the folder and not delete it. If this fixes the problem, you may need to redo your MAX configurations, if possible, once you are able to successfully open MAX and run Resman without errors. Although you get these errors now, can you still use any of your hardware or will it not work at all? Please answer these and I will look into the issue further.
Chris R.
Applications Engineer
National Instruments
03-03-2006 11:54 AM
Hi Chris,
I run RESMAN from the .exe. I have a PCI-MXI-2/VXI-MXI-2 with all switches/jumpers in the default position. I didn't change the versions of the drivers until I had the problems. Since then I have removed and reinstalled NI-VXI 3.2 from the CD that came with the MXI cards and NI-VXI 3.3.1 downloaded from the web. I get the same results from both versions. I currently have 3.3.1 loaded and I moved the DATA folder as you suggested but no luck. Also, now when I run MAX, I get a message the 'config.mxs' is corrupted. I take the suggested action of renaming the file but I still get the error. I am unable to run my hardware in the VXI chassis. Any suggestions on where to go from here?
Thanks!!!
03-07-2006 07:09 AM
03-08-2006 02:37 PM
Chris and Ebele,
Thanks for your help. I had looked before at the link that Ebele suggested but it didn't help. But at Ebele's suggestion, I looked at again and it made me realize what the problem was. We recently had made some changes in user accounts and things really got changed on my test machine. I was able to get the user rights back that I needed to get everything to run.
Thanks again!