TestStand 3.1 ASCII Text Report is not working with Win 2008

[HenryG]

After test sequence is executed and Test Report (ASCII text file) supposed to be displayed, TestStand will stopped responding. I’m getting following Windows 2008 error:

Description:

  A problem caused this program to stop interacting with Windows.

Problem signature:

  Problem Event Name: AppHangB1

  Application Name:         TestExec.exe

  Application Version:     3.1.0.9095

  Application Timestamp:              41071a59

  Hang Signature:              c5d2

  Hang Type:       256

  OS Version:      6.1.7601.2.1.0.272.7

  Locale ID:           1033

  Additional Hang Signature 1:     c5d231e38214d7e121af4cda8e7a9b0c

  Additional Hang Signature 2:     b6e8

  Additional Hang Signature 3:     b6e8690201cd304d4eb9ae4d11cb46f9

  Additional Hang Signature 4:     c5d2

  Additional Hang Signature 5:     c5d231e38214d7e121af4cda8e7a9b0c

  Additional Hang Signature 6:     b6e8

  Additional Hang Signature 7:     b6e8690201cd304d4eb9ae4d11cb46f9

The XML and HTML reports are working fine.

Any idea how to fix it?

Thank you,

Henry

[Anjelica-W]

Can you provide more details on your application including an overview of what your sequence does?

Does this crash occur for any other sequences including example sequences?

Have you been able to generate a ASCII Text Report in the past?

You mentioned that the HTML and XML reports are generated correctly. Does it crash everytime you run the sequence using the ASCII report format?

[HenryG]

Hi Anjelica,

1. My test sequence is running diagnostics on PCB using DLL interface.
2. The crash will occur for any test sequence including example sequences.
3. I am able to generate the ASCII Text Report on Win 2003. This is happening only on Win 2008 .
4. Yes, the HTML and XML reports are generated correctly.

Thank you,

Henry

[Anjelica-W]

Hi Henry,

I am currently setting up a test machine to try and replicate this behavior. I will update you with my findings.

[Anjelica-W]

Hi Henry,

I was not able to reporduce the issue on my Windows 2008 test machine with TestStand 3.1. I would recommend running a force reinstall to ensure that any missing or corrupt files are replaced.

[dug9000]

It's also possible your dll calls are corrupting memory leading to crashes in unrelated code due to memory getting overwritten. Can you reproduce the problem with a simple sequence, or only with your main sequence? If only with your main sequence, make sure the prototypes to your dll calls are specified exactly correctly to avoid issues with memory corruption.

-Doug

[HenryG]

Hi Doug,

This is not a case, the crash will occur for any test sequence including NI example sequences.

Thank you,

Henry

[HenryG]

Hi Anjelica,

The force reinstall did not fix the problem. Please see my attachment.

Thank you,

Henry

[dug9000]

Ok, then maybe trying a clean install or a fresh install on a different machine might work. Keep in mind that TestStand 3.1 does not officially support Windows 2008. That doesn't mean it won't work, but it does make it more likely that some things might not work correctly. See the following document for more details:

http://www.ni.com/teststand/product_lifecycle/

-Doug

[dug9000]

Also, have you customized TestStand or the process models in anyway? If so you might want to try reverting those customizations or installing on a clean machine and not installing your customizations.

-Doug