Wikis - Page

How can I resolve the Custom Reports Runtime Error: "Invalid license key: XXX - Please contact your System Administrator"?

0 Likes

Problem:

How can I resolve the Custom Reports Runtime Error: "Invalid license key: XXX - Please contact your System Administrator"?

Resolution:

ANSWER
----------------------------------
The reports on the Custom Reports Tab in SilkCentral Test Manager (SCTM) 7.0 are produced by an integrated report engine. This report engine, developed by InetSoft, uses a license key that expired in December 2004. When this key expires the Custom Reports, created by InetSoft Report Designer, cannot be run. The issue can be resolved by exchanging the expired temporary key for the permanent license key as detailed below.

Locate the machine where the SCTM 7.0 server is installed and use the SCTM Service Manager to stop the Segue Frontend Server:

START | PROGRAMS | SILKCENTRAL | SILKCENTRAL SERVICE MANAGER

Should a message be returned saying Service Manager is already running please look in the System Tray:

Double-click the SILKCENTRAL SERVICE MANAGER Icon | SEGUE FRONTEND SERVER Tab | STOP BUTTON | Click OK

Locate the SccResinFrontendServerConf.xml file:

C:\Program Files\Segue\SilkCentral Test Manager 7.0\conf\frontendserver


Make a backup of this file before editing it, with a non-formatting text editor such as Windows Notepad.

Find the XML element:

 


The value of the license.key attribute will be a long alphanumeric entry with embedded dashes. Replace the value of the license.key attribute with the new license key S000-61B-ERX-000094001-F37E9317CF96. It should like:

 


Save the file before restarting the Segue Frontend Server.

Click SILKCENTRAL SERVICE MANAGER Icon | SEGUE FRONTEND SERVER Tab | START BUTTON | Click OK

To confirm the issue has been resolved, login to SCTM and ensure the Custom Reports are returning data.

The SCTM 7.0 package on the Segue download area has been updated to contain the new permanent license key, so any downloads after 02 December 2004 will not encounter this issue.

Old KB# 24881
Comment List
Related
Recommended