Hello Paul -
I am curious, you mention that you checked the file permissions in the TestStand directory, does this mean you were checking the DCOM settings on your machine? Or just that you were making sure the user had read/access permissions to the folders in question?
Something you may want to check if you haven't yet, is the SuperUser's default security settings. You can do this by running decomcnfg.exe on your machine. In the new window, check inside the security tab to see what level access your logged-in user is granted. By default, SuperUsers on Win2000 systems should have no problems with security, but it is always good to check if something has been altered.
The second thing you might check is the file permissions on the Sequence Editor itself. On NT
bases systems if you are using a NTFS partition for your OS, you can specify different access levels to different users. To check this, use the decomcnfg program again and select 'sequence file' from the list of applications. Select 'properties' look at the security tab for the file to see if Administrator is the only group authorized to open the Sequence Editor.
A third potential trouble spot to investigate is the TestStand engine, verify that it is registered and running, or simply reregister it via a command such as regsvr32 and a full path to your "teapi.dll" which is located in the bin directory in the TestStand install path.
Because errors such as these can be tricky to find the precise source of, any additional information you have about the machine and how TestStand was installed on it would be of use in working with you further. If checking the additional security settings yields no useful information, I would recommend you send an email directly with your system inform
ation and an engineer will work with you to try and address this behavior.
-Regards
Elaine R.
National Instruments
http://www.ni.com/ask
