Articles Tagged 'error'

Customers running Spira v5.0 or v5.1 may experience an issue where the system will let you create test case folders that point to one of their children as parent. This causes an infinite loop which will break the system. This article provides a solution to fix the issue (though we recommend upgrading to v5.4 to prevent it happening in the future).

This article is obsolete.
The infinite loop issue was fixed in later versions of Spira.

After upgrading to Spira v4.2, if you get either of the following error messages:

• 'Width' is not a member of type 'Inflectra.SpiraTest.DataModel.IncidentView'
• 'DisplayMode' is not a member of type 'Inflectra.SpiraTest.DataModel.IncidentView'

Please follow the instructions in the article to solve the issue that happens when you try and use a saved filter that gives this issue.

This article is obsolete.
It is referring to the old bug fixed in later versions and applies only to that particular case when upgrading to Spira v4.2.

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.

If you have recently upgraded to Spira v5.x from an earlier version and get an error message saving artifacts that mentions 'XPKTST_ARTIFACT_CUSTOM_PROPERTY' then you may have some old artifact custom property records that are blocking the new item saving

If you are trying to run a test case or test set and you receive the following error:

Messages:
   Database constraint violation occurred [APPLICATION.Business.EntityConstraintViolationException]
   An error occurred while updating the entries. See the inner exception for details. [System.Data.UpdateException]
   Violation of PRIMARY KEY constraint 'XPKTST_ARTIFACT_CUSTOM_PROPERTY'. Cannot insert duplicate key in object 'dbo.TST_ARTIFACT_CUSTOM_PROPERTY'.
The statement has been terminated. [System.Data.SqlClient.SqlException]

Then this article provides the solution for you.

Automatic screenshots on every test step may occupy too much space. Learn how to make  a screenshot on failure only.

You can use the Spira Project Backup & Migration Tool to move projects between one instance of SpiraTest and another pretty easily. However there is a known issue that can sometimes occur if you have deleted custom properties.

Sometimes when you try and run certain reports you may get an strange error message "The passed in report ID or report format ID does not exist". This message is unfortunately a red herring, and there is a different reason for this error.

This article describes how to resolve the following error message that can occur on new installations of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk when ASP.NET is not correctly configured. This message typically only occurs on Windows Vista, Windows7 or Windows 2008 Server.

HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.

After upgrading from v3.2 to v4.0 you may receive this error message when you access the Reports home page on certain projects: