TestStand Report is empty after generation

[svenbo89]

Hello everybody,

my actual problem is the following:

We use TestStand 2014 in our production test systems for several months now.

Sometimes it happens, that some reports contain no data after generation on the harddrive.

The file consist 0kb data, even with a text editor it is absolutely empty.

On our test machines we don't use the OTF Reporting.

If this problem occurs, the next file can be absolutely fine. It happens absolutely random and maybe 1-2 times per 100 tests. 

Further we only use the built in Report generation of teststand, that means no additional callback during execution.

Does someone has any idea what can cause this problem?

Thank you very much.

[Nico011]

Hi svenbo,

It kinda sounds like something is preventing TestStand from accessing the file or its location. Are you saving the reports to a shared location? Or perhaps the files are being accessed during operation?

Nic

[svenbo89]

Unfortunately no.

As it happened the first time, the report was saved on a local usb memory stick.

Because i thought, that this memory stick is broken, i changed the path to the HDD.

But this didn't help.

[Norbert_B]

---

@svenbo89 wrote:
[...]i changed the path to the HDD.

But this didn't help.

---

Which base directory?

There are directories where Windows demands specific user rights.

Also you might want to check if there are services like disk indexing are running at the time you have issues with the report....

[svenbo89]

Yes, i know that windows needs specific user rights in some directories. 

On some machines we use usb drives for the whole test program including sequence file, on others we use the Desktop path.

Because i suspected malfuntions, i had also replaced some usb drives with new (better) ones, since cheap devices sometimes break.

Unfortunately the problem occured again.

I will try to switch the indexing services off. 

Thank you

[Norbert_B]

Does the computer 'run idle' during test?

If so, i can imagine that USB configuration (BIOS/Windows) puts USB to sleep which could induce issues like this.....