08-24-2010 09:20 AM
I had made some changes to a 1st level subsequence (one that is called by the main sequence) and ran some test and all was fine. Then I opened another 1st level subsequence to make similar changes. It opened but I got a message stating that TS couldn't write to TestExec.ini. That was because it was not checked out from ClearCase. Why did TS want to update this file at this time?
Inquiring minds want to know.......
Thanks,
jvh
08-25-2010 01:03 AM
Hi jvh,
I cant remember exactly what's in TestExec.ini but I would guess it stores such data as previous loaded sequence files and sequences. If there wasn't a copy of the file in the default directory I am surprised TestStand didn't generate a new file. So maybe the folder was write protected or that application / user didn't have premission to write in that folder.
08-30-2010 10:14 AM
Hi jvh,
TestExec.ini is a configuration file for your TestStand environment. If anything is modified, configuration wise, it will need to be updated. I attempted to reproduce your situation by making my TestExec.ini read only and simply modifying a sequence file. I was unable to get the same error. Do you know if any configuration options were also changed and what you were changing in the sequence?
Thanks
06-27-2011 12:57 AM
Hi All,
This is already old topic and i have also found few similar topics, but no answer to question.
I'm now facing similar problem with read only configuration file (TestExes.ini) and i wonder whether someone have solution to this problem.
1) Is it possible to disable warnings caused by read only config files?
2) Are there some other way to get around this problem?
Br. Lauri Lahti
06-27-2011 02:38 AM
Sorry.. I got file name wrong.
Here is screenshot of error message i got.
06-27-2011 06:18 PM
Hi Larui,
When does this error occur? I've found a KB on error code -17205 that might help you out. It's listed below.
I hope this helps.
Josh L.
06-28-2011 09:34 AM
@Lauri Lahti wrote:
Sorry.. I got file name wrong.
Here is screenshot of error message i got.
Are you checking this file into source control? Is it marked as read-only?
-Doug
06-28-2011 09:49 AM
It also could be a permissions issue where you don't have permissions to write to the Program Files directory.
06-28-2011 10:09 AM
@AllenP wrote:
It also could be a permissions issue where you don't have permissions to write to the Program Files directory.
Good point. Also, if you are using Windows Vista you should be using TestStand 4.1 or higher and if you are using Windows 7 you should use TestStand 4.2.1 or higher.
-Doug
06-28-2011 08:05 PM - edited 06-28-2011 08:09 PM
After studying this problem more it seems to be problem with permission.
This error was generated by deployment engine after installing it to Windows 7. Quick fix was to run it as administrator.
Generally speaking it's not good solution to require administrator rights so better solutions are needed.
So what we learn is that installing configuration files which needs write access under program files isn't good choise.
What would be better place for configuration files?
I don't want to use teststand default path in order to prevent mixing with other deployment's configuration files.
I just wonder why teststand need to write to UserInterface.xml?
Br. Lauri
Edit: There have been earlier discussion about UserInterface.xml
http://forums.ni.com/t5/NI-TestStand/UserInterface-xml-directory/m-p/716077