Articles Tagged 'upgrade'

Articles
Upgrade from v5.4 to v6.0 Blocked by Foreign Key Constraints

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.

How to move a Spira or KronoDesk installation to another Server

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.

Upgrade from v5.4 to v6.0 blocked by missing FullText Index Error

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

What to do When a SpiraTest/Plan/Team Upgrade Fails?

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.

The 'TestCaseWorkflowId' property on 'TestCaseType' could not be set to a 'null' value

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

How to upgrade Rapise to a newer version

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.

Upgrading SpiraTeam v4.1 from older version fails due to .NET 4.0 check failing

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.

Getting 'X' is not a member of type 'Inflectra.SpiraTest.DataModel.IncidentView' after 4.2 upgrade

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.

Unable to create a new project after upgrading to v4.0
If you have upgraded from Spira v3.2 to v4.0 you may receive a Foreign Key violation error message when you try and create a new project. We have identified the cause and will be adding a fix to patch 003. This article describes an immediate workaround.
WebPart Error on Reports Page After Upgrading from v3.2 -> v4.0

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.

The application doesn't display correctly after upgrading versions

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.