Can't write to TestExec.ini

Question

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

Answer 1

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.
Problem
The NI DataFinder is indexing files on my machine (installs with DIAdem or LabVIEW DataFinder Toolkit or DataFinder Server Edition), and I sometimes receive errors -5001 and -17205 when generating XML or ATML reports from TestStand example sequences. I am able to generate HTML and ASCII reports without any errors – what is causing these errors?
Solution
An explanation of the cause of these errors is provided below. This issue (as described below) is fixed in the NI DataFinder 2011 when TestStand 2010 SP1 or newer is installed.
The NI DataFinder periodically indexes files in certain default directories, one of which is the National Instruments Public directory. When the DataFinder attempts to index a file, it grabs exclusive read access to the file such that no other process can read or write to the file.
When generating an XML or ATML report, TestStand obtains and releases write access to the file on multiple occasions when creating the file, writing to the file, adding/removing root tags, etc., and TestStand does not expect other applications to lock the file. By default, TestStand will attempt to generate a report file in the same directory as the sequence file being run.
You may encounter the above mentioned errors if all of the following apply:
You install a DataPlugin for TestStand XML or ATML report files
You generate an XML or ATML report for a TestStand sequence, such as a TestStand  example sequence file
DataFinder is configured to index the directory where TestStand generates the report, such as the <TestStand Examples> directory.
To work around this issue, you can manually exclude a directory where TestStand generates reports from NI DataFinder’s list of Search Areas (directories to index).
The Version Selector application installed by TestStand 2010 SP1 automatically configures DataFinder 2011 to exclude files in the <TestStand Public> directory for all version of TestStand installed on a machine. Thus you will not encounter the above mentioned error when running TestStand example sequences if TestStand 2010 SP1 or newer is installed and DataFinder 2011 is indexing files on your machine.
I hope this helps.
Josh L.
Applications Engineer
National Instruments