TestStand XML Report Generation Issue on Deployment Computer

[sam1262]

Hello,

I'm having an issue on one of my deployment computers where the XML files generated by a TestStand sequence don't contain valid XML & XML styling. I have a development computer where the sequence was built on using TestStand 2013 and LabVIEW 2013. I also set some of the report generation settings on this computer. 

I've copied over all the necessary files to run the TestStand sequence, as well as all the TestStand /Cfg files from the development computer to the deployment computer (which are both running Windows 7), however the XML report generated does not contain the appropriate styling. I'm able to run the sequence fine. Opening the XML file in an XML validator tool also shows that the XML code itself has missing tags, brackets, etc. 

Has anyone experienced a similar issue, or have any idea what could be causing this? Any help is appreciated.

Thanks,

Sam

[oscarfonseca]

Hello Sam,

I don't recall seeing this behavior before. I presume it has something to do with the computer's files/configuration indeed, and I can see how you have replaced all the presumably involved files.

Can you post an example of the expected/correct file, vs the invalid one that you're getting? Maybe someone in the community can relate to what you're seeing.

All the best,

[sam1262]

Hi Oscar,

While looking further into this problem I came across a list of known TestStand issues. If you look particularly at the following ones, I think they might be related to the issue I'm having:

In some of my testing I also concluded that the XML report became corrupt only when sequence calls from a main sequence file were present. I disabled on-the-fly report generation and this solved the issue altogether- as the errors above may suggest.

Now, I'm trying to figure out a workaround where I can generate an XML report, with on-the-fly reporting, with sequence file calls, and also get a valid report in the end. I haven't been able to find anything on this yet. 

Best,

Sam

[oscarfonseca · Accepted solution]

Hello Sam,

Thanks for providing that extra information and tests. I think this case sounds more like CARs (Corrective Action Requests): 479179, and 530669. They were fixed in TestStand 2014 and 2014 SP1, according to the articles posted.

The documented workarounds are:

• Switch to a different report file format, such as ATML.
• Disable On-The-Fly reporting.

All the best,