Articles Tagged 'install'

One of the benefits of using Inflectra software is that you get unlimited upgrades for the first year and as long as you maintain an active service plan. This articles describes the process for upgrading your installation of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk to the latest version. It also answers many common questions about the process.

If you install Rapise on non-vanilla system, e.g. old workstation with a lot of other software, especially with anti-virus and development tools, it may end-up in a state when some components are not registered  successfully and some files are blocked.  In this article we describe symptoms and ways to cure.

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.

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.

This is a common need, since you may have installed SpiraTest, SpiraPlan,  SpiraTeam, or KronoDesk  on a workstation to evaluate its capabilities and now need to install it on a production server for real use, but you don't want to lose all your existing data.

Our web-based products: SpiraTest, SpiraPlan, SpiraTeam and KronoDesk make use of the Microsoft IIS web-server and Microsoft SQL Server database platforms.
This KB article explains some of the more common error messages that can occur after installing one of our products and the steps to remedy them.
Article was initially written specifically for versions v3.0 - v4.2 of Spira and versions v1.x of KronoDesk, but some of the issues applicable to the recent versions as well.

In rare cases Rapise installation fails. There may be different reasons for this including AV software, security configuration or corrupted Windows system. To help Rapise team to find out the root cause you may zip and share Rapise installation logs.

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.

After upgrading to v6.8, you may get a system error with the text in it that states that the task can not be completed. This can affect creating users, copying Products, creating new Products, among other activities.

When you are installing SpiraTest, SpiraTeam, SpiraPlan or KronoDesk on a database server with a large 'model' database sometimes the install will fail because the initial Spira/KronoDesk database is not large enough to contain your model database. This article provides the solution

In the unlikely case of unsuccessful deinstallation of Rapise (e.g. if computer power switched off during deinstallation,  or Windows Installer process terminated) there is a way to manually fix the system and complete interrupted deinstallation process.. Automatic uninstall may no longer properly work and leave files in Program Files folder.

Sometimes when you first install and open Rapise, the Start Page does not display correctly. This article explains the cause and solution to fix the issue.

If you don't have some of the standard Window fonts installed (e.g. Courier New), when you try and launch Rapise, it will fail to open correctly. This article provides information on the problem and solution.

Sometimes when you try and install Rapise, you will see the error message "The Pipe is Being Closed", this article provides some solutions for this message.

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.

If you run one of our installation packages (.msi) and receive the following message:

A DLL required for this install to complete could not be run

Sometimes when you install Rapise on a computer that had a previous version of Rapise installed, when you try to record and/or playback a test you get the following error message:

C:\Program Files (x86)\Inflectra\Rapise\Engine\Player.js WScript.CreateObject: Could not connect object.

This article describes the steps to correct the error.