Why do I receive a "500 Servlet Exception" after upgrading from version 3.0 or 3.1 to version 4.x?

0 Likes

Problem:

Why do I receive a "500 Servlet Exception" after upgrading from version 3.0 or 3.1 to version 4.x?

Resolution:

ANSWER
----------------------------------
After upgrading SilkCentral Issue Manager from version 3.0 or 3.1 to version 4.x you may receive the following error when attempting to create a new issue, or view an existing issue:


This error occurs because the label for the "custom" tab did not exist in Versions 3.0 and 3.1, which had a hard-coded value for this tab. Versions 3.2, 3.3 and 4.x store this label in the Custom_Gui table.

It is therefore strongly recommended to upgrade to version 3.3 before upgrading to version 4.x to avoid this exception.

If you have already upgraded from versions 3.0 or 3.1 to 4.x and you receive this error it is possible to modify the database directly by getting the Database Administrator to run the following query in SQL Server Enterprise Manager:

INSERT INTO IM_CustomGui (ProjectID_fk,
GUIObjectID,
GUICaption,
GUIType,
ValueListID_fk,
InsertRole,
UpdateRole,
CaseMapping,
GUIFlags,
UserCreated,
DateCreated,
UserLastMod,
DateLastMod)
VALUES (17,119,"Custom",4,NULL,0,0,0,0,"segue",GETDATE(),"segue",GETDATE())


The first value (17) is the ProjectID, so this will fix the problem for a project with an ID of 17. If other projects show this exception too you have to execute this query again but change the ProjectID accordingly.

See also: What should I consider when upgrading from Issue Manager 3.x to 4.x?

Old KB# 23679
Comment List
Anonymous
Related Discussions
Recommended