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.