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.

If you're running Spira v4.0 patch 002 or lower, you can either apply patch 003 when it becomes available or as an immediate solution:

1) Open up SQL Server Management Studio on the database server

2) Choose the "New Query" option

3) Change the database to SpiraTest / SpiraPlan / SpiraTeam and then run the following SQL command:

SET IDENTITY_INSERT TST_WORKFLOW_FIELD_STATE ON;
GO
INSERT INTO TST_WORKFLOW_FIELD_STATE
(
WORKFLOW_FIELD_STATE_ID, NAME, IS_ACTIVE
)
VALUES
(
3, 'Hidden', 1
)
GO
SET IDENTITY_INSERT TST_WORKFLOW_FIELD_STATE OFF;
GO

 

Article Info
  • Last Updated: 11/11/2013
  • Article ID: KB33
  • Views: 1699