Self-referential test step linking in SpiraTest can cause .NET exceptions

KB54: Created By inflectra.david | Thursday, February 1, 2024 | 7425 Views | Last Updated: 2/1/2024

Home Page > Knowledge Base > 1. Spira Platform > SpiraTeam

Home Page > Knowledge Base > 1. Spira Platform > SpiraTest

If you ever receive the following error message:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: nlssorting.dll, version: 4.0.30319.1, time stamp: 0x4ba21c2f
Exception code: 0xc00000fd
Fault offset: 0x0000000000001ef9
Faulting process id: 0x1208
Faulting application start time: 0x01ce67177b5b877f
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
Report Id: 5ef990e5-d30e-11e2-863b-005056b1010f

This article is obsolete.
Currently used versions of .NET do not cause the same exceptions since the new framework implemented resolves that legacy bug.

This can often indicate that you have a situation where you have a test case link to a test case that links back to the parent test case (i.e. an infinite loop).

So if you ever receive this message, check for the following situation:

Test Case 1
- TC1 - Links to Test Case 2
  - TC2 - Links to Test Case 3
    - TC3 - Links back to Test Case 1

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

Self-referential test step linking in SpiraTest can cause .NET exceptions

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

Search Results