NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand crashes after starting Execution Profiler, Update NI calls, Import/Export Properties

Hallo everbody,

 

We have recently had a problem with TestStand. When starting some tools, TestStand editor crashes immediately. In the WIndows eventviewer this is shown as a consequence of the .NET runtime environment  crash with exitcode 80131506. The module cdr.dll, version: 4.8.4645.0 is indicated as the cause of the error. Error code is 0xc0000005

Does anyone know this problem?

Thanks and greetings
Marc

0 Kudos
Message 1 of 7
(419 Views)

Marc, 

What specific version and bitness of Windows OS and TestStand are you using?

Is this crashing behavior occurring on a single system or does it also occur on other similar versioned OS and TestStand systems?

Scott Richardson
https://testeract.com
0 Kudos
Message 2 of 7
(385 Views)
Spoiler
Hi Scott,

We use Windows 10 in the 64-bit version. The problem exists on all our IT-managed computers, which are all configured in the same way (virus scanner, firewall, etc.). We also use the same TestStand version (2021 SP1) on all these computers.



Regards
Marc

0 Kudos
Message 3 of 7
(362 Views)

Marc, FWIW, I believe that the error is an access violation. Since you have multiple system seeing this, I am curious, have these systems worked fine and started failing at some specific timeframe? Did they all start failing at the same time? Can you associate that transition to failing to some change on these systems, such as updating NI software, OS updates, virus protection, etc.?

Scott Richardson
https://testeract.com
0 Kudos
Message 4 of 7
(342 Views)

Hi Scott,

To be honest, I also suspect the virus protection to be the cause (Trellix Endpoint Security). Unfortunately, I don't have the rights to deactivate it even temporarily and am currently reliant on the help of our IT department to narrow down the cause of the error.
If there is anything new, I can report it here.

 

Thanks for your efforts
Marc

0 Kudos
Message 5 of 7
(335 Views)

Hi Scott,

The cause was actually Trellix Virus Protection. Our IT department changed something in the policy, which fixed the problem.

 

Regards
Marc

0 Kudos
Message 6 of 7
(305 Views)

Great, thanks for letting the forums know how your resolved this.

Scott Richardson
https://testeract.com
0 Kudos
Message 7 of 7
(295 Views)