Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

What can cause the error "Importing Requirements Failed: (n) requirement(s) created (n) Error(s)...." when importing CaliberRM requirements?

What can cause the error "Importing Requirements Failed: (n) requirement(s) created (n) Error(s)...." when importing CaliberRM requirements?

Problem:

What can cause the error "Importing Requirements Failed: (n) requirement(s) created (n) Error(s)...." when importing CaliberRM requirements?

Resolution:

ANSWER
----------------------------------
The reason for this error is to inform the user that the requirements import has failed for some of the Caliber RM requirements. The message informs you that:
XX (number) of requirements were successfully created but that XX (number) of errors occurred during the import to Test Manager. If you get the error you should consult the SynchLog log file. This file is located in the SilkCentral Test Manager log directory at "C:\Program Files\Segue\SilkCentral Test Manager 8.0\log".

One of the main reasons the import may fail is that on import to Test Manager there is a limit of 60 characters for requirement names, therefore if you have a requirement that is greater than 60 characters you will see the following in the log:

Importing "" > Duration: 0.36 seconds > ERROR (Errors: 1, Warnings: 0) > Creating new SilkCentral Test Manager requirement "40.5.4.6 Health Outcome Measurement Contractor Responsibilities" > ERROR: Fatal, reason: >com.segue.tm.common.requirements.rmsync.StoreRequirementFatalException: couldn"t store requirement entity changes > StackTrace::

This will be followed by a large java stack trace and finally the error code:

[PERF-EXEC9]String or binary data would be truncated.

So if you search the log for the word truncated and you see the error then you will know that one or more of your requirements need to be renamed. Keep searching the log until all affected requirements are identified. Once you know all affected requirements open the requirement template in Caliber RM and rename all the requirements. If you are experiencing any additional problems, or if you get a different error please contact Support and enclose a copy of your SynchLog.Log file and the requirements you are trying to import.

Old KB# 24780

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:49
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.