When you upgrade an older version of SpiraTest, SpiraPlan or SpiraTeam (hereafter referred to as Spira) from an older version to the latest version, the installer has to upgrade the application and database at the same time. This article provides some solutions to cases where the installer throws an error or fails to upgrade the database for some reason.
After upgrading to Spira v4.2, if you get either of the following error messages:
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.
Sometimes when running the SpiraTeam v4.1 installer to upgrade from an older version of SpiraTeam (same also applies to SpiraTest and SpiraPlan) you will get the error message:You must install the Microsoft .NET Framework 4.0.30319 even though .NET 4.0, 4.5 or 4.5.1 is installed.
This article is now obsolete.Current framework requirements listed here.
Sometimes after your instance of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk is upgraded (or you upgrade an on-premise edition), the screen doesn't display correctly.
Rapise is evolving product and we release new versions of it from time to time. If you plan to upgrade your copy of Rapise follow these simple steps.
When you upgrade from v5.4 to v6.0, unlike previous versions of the upgrader, we don't delete the entire database and recreate it. The upgrader makes the changes to live database in-situ. However if you have missing foreign key constraints in the v5.4 database it can lead to bad data that breaks the installer.
During the upgrade of an older version of Spira v6.x to the latest version of Spira v6.x the installer logs the following:
Cannot insert the value NULL into column 'TASK_WORKFLOW_ID', table 'SpiraTest.dbo.TST_TASK_TYPE'; column does not allow nulls. UPDATE fails. The statement has been terminated. [System.Data.SqlClient.SqlException]
Sometimes it is necessary to move a SpiraTeam, SpiraTest, SpiraPlan, or KronoDesk installation to another server, without wanting to lose all of your data. This KB will guide you through the steps of transferring the install over, and optionally upgrading the application. This guide will walk you through the recommended steps when needing to move both the application and database to new servers.
Sometimes when running the Spira v6.0 installer to upgrade from v5.4.0.4 to v6.0 you get the following error:
Table or indexed view 'TST_ATTACHMENT' does not have a full-text index or user does not have permission to perform this action.
This article describes the cause and provides the solution
When you upgrade from v5.4 to v6.0 upon opening a test case detail page you receive the error: "The 'TestCaseWorkflowId' property on 'TestCaseType' could not be set to a 'null' value". This article explains the cause and provides the solution
After upgrading from v3.2 to v4.0 you may receive this error message when you access the Reports home page on certain projects:
PageLayout:: OnError:Cannot deserialize the blob of personalization data associated with the current page.Parameter name: data [System.ArgumentException]The serialized data is invalid. [System.ArgumentException]Value cannot be null.Parameter name: enumType [System.ArgumentNullException]
This article describes the solution to fix this issue.