Where does TestStand keep its sequence log messages?

[DLMC]

The particulars

Windows 11 Enterprise

Labview 2022

TestStand 2021

This is question that I have found no answer to, most likely because my Google-foo is not up to the task.

While debugging a TestStand issue where a VI would not run in TestStand but ran fine in just LabVIEW I found a file called SeqEdit_BrokenVILog.<timestamp>.txt that told me why.  Sadly, I did not note where I found that file, have not been able to find it again and no one in TestStand user land has talked about it.

Where does TestStand keep run-time logs or error logs, or debug logs, or whatever they are called?  That file was essential to me finding out what was going on - I'd love to continue using that mechanism... But where is it?

be well,

DLC

[aeastet]

This is what I found:

1. Result Report Files

By default, TestStand stores execution results (including log messages) in report files:

• Location:
  C:\TestStand Reports\ (default, configurable)

• File Types:

  • .txt

  • .html

  • .xml

  • .atml

• Content:
  These include step results, custom messages, errors, and logging from Log Message, Message Popup, or Report Text steps.

• How it's Controlled:
  In TestStand Sequence Editor:

  • Configure → Result Processing...

  • Select or customize report generation.

---

✅ 2. NI TestStand Database Logging (Optional)

If database logging is enabled, messages can be logged into a relational database like SQL Server or Oracle.

• Configure via:
  Configure → Database Options...

• Database Schema:
  You can customize which step results or log messages are saved (e.g., UUT_RESULT, STEP_RESULT, etc.).

---

✅ 3. Runtime Message Log (Internal Debugging)

Temporary or runtime messages may also be viewable via:

• Execution View pane (in Sequence Editor or Runtime UI)

• Report Text step (messages show in the report)

• Breakpoints and Watch Expressions for debugging

These are typically not saved unless explicitly written to a report or file.

---

✅ 4. Custom Logging via LabVIEW/.NET/ActiveX Steps

If you're using custom steps to write logs (e.g., to a file or Windows Event Viewer), then the location depends on your implementation (e.g., writing to C:\Logs\customlog.txt or similar).

---

🛠️ How to Add a Log Message to a Report

You can explicitly log something by:

• Using the "Log Message" step under the User step types.

• Setting a step’s "Record Result" or "Include in Report" flags.

• Using RunState.SequenceContext.ReportLoggingOptions or Result.ReportText.

---

If you're unsure where your logs are being stored, check the current report and database configuration under:

• Configure → Result Processing...

• Configure → Database Options...

[DLMC]

---

@aeastet wrote:

This is what I found:

1. Result Report Files

By default, TestStand stores execution results (including log messages) in report files:

• Location:
  C:\TestStand Reports\ (default, configurable)

• File Types:

  • .txt

  • .html

  • .xml

  • .atml

• Content:
  These include step results, custom messages, errors, and logging from Log Message, Message Popup, or Report Text steps.

• How it's Controlled:
  In TestStand Sequence Editor:

  • Configure → Result Processing...

  • Select or customize report generation.

---

✅ 2. NI TestStand Database Logging (Optional)

If database logging is enabled, messages can be logged into a relational database like SQL Server or Oracle.

• Configure via:
  Configure → Database Options...

• Database Schema:
  You can customize which step results or log messages are saved (e.g., UUT_RESULT, STEP_RESULT, etc.).

---

✅ 3. Runtime Message Log (Internal Debugging)

Temporary or runtime messages may also be viewable via:

• Execution View pane (in Sequence Editor or Runtime UI)

• Report Text step (messages show in the report)

• Breakpoints and Watch Expressions for debugging

These are typically not saved unless explicitly written to a report or file.

---

✅ 4. Custom Logging via LabVIEW/.NET/ActiveX Steps

If you're using custom steps to write logs (e.g., to a file or Windows Event Viewer), then the location depends on your implementation (e.g., writing to C:\Logs\customlog.txt or similar)ssage to a Report

Thanks for your efforts on that, but these are all errors given by the test when that which is being tested fails or has information to save or show, except for #3 which is ephemeral error information.  Type 3 is kind of what I am looking for, but even this information is terse and did not go into the detail I saw in that sequence "broken vi" txt file with a date stamp on it, which seems like it was intended to hang around.  I will keep searching for where I can find these gems of information that were so useful - I plan on continuing to break the test I am working on. 🙂 

Darn!  I wish I had documented where I found that file!

be well,

DLC

[Oli_Wachno]

Can't tell you exactly, but the places to look for stuff like that is usually 

%TestStand%\CFG (or%TestStand64)

or

C:\Users\your.user\Local\National Instruments\TestStandVersionOfChoice

[ShockHouse]

It's in your temp directory. Either use %temp% or C:\Users\<username>\AppData\Local\Temp to get there.

[DLMC]

Oli, Shockhouse,

I knew those locations, neither have that file.  I wish I had written down where I found it because now it just seems like I was hallucinating. Oh well.  Maybe it will crop up some time again, I'll write it down...

be well,

DLC

[ShockHouse · Accepted solution]

It is 100% the temp directory. And it's not a TestStand Log file, it's specific to LabVIEW in this case. [EXE Name]_BrokenVILog. Since you are using the Seq editor, its SeqEdit_BrokenVILog. 

Here's slides from a powerpoint I've given on this. The only time it would be somewhere other than the %temp% directory, is if in your LabVIEW Settings you changed it to you a custom temp location. (Tools -> Options -> Paths -> Temporary Directory)

[DLMC]

ShockHouse,

I did not express myself well.  I confirmed, using your suggestions that was the temp directory - that .txt file is now not there, or so I thought  

And then, I mistyped in my search bar and missed the filesI was looking for. 

This absolutely found and answered my questions.

be well,

DLC