NOTICE: Our Community is moving. Get more information.
Why are Eclipse-based CaliberRM clients unable to view Requirements?
Eclipse-based CaliberRM clients throw errors or fail to display
anything when attempting to view CaliberRM Requirements. The
Eclipse log (a file named ".log" in the Eclipse
workspace) shows an error stack like one of the following:
Due to the common underlying code, this issue can be observed in
the CaliberRM for Eclipse client, the CaliberRM view available in
Caliber DefineIT, and the CaliberRM plugin for Eclipse-based
releases of Together.
There is a defect in the CaliberRM 2006 Client Hotfix 39c (file
version 9.0.934). In this build, editing any single-selection list
attribute (whether a User Defined Attribute or a system attribute
like "Requirement Status") may cause an invalid index
value to be applied to one of the attribute"s available
options. These invalid index values in turn cause critical faults
in any SDK application that attempts to retrieve a Requirement
containing that attribute.
The solution is to use an unaffected build of CaliberRM Client,
such as the original client build (version 9.0.847), Hotfix 28c
(version 9.0.910), or Hotfix 43c (9.0.945), to and open the
affected attribute for editing, then close the edit window without
making any changes. The Client will refresh the underlying index
values and thus resolving the errors, even though the data is left
The problem attribute should be one assigned to the types of
Requirements throwing the error in the CaliberRM for Eclipse,
DefineIT, or Together client. This should help localize the
issue to one or a few possible attributes.
If all Requirements are affected, then the problem most likely lies
with one of the system attributes and not with a UDA.
If you are not certain which attribute is the cause and cannot
narrow down to a few suspects, the best course of action is simple
to sort your list of UDAs by type and open and close each
single-selection list UDA in turn, then address the two system
attributes. Even on a large database this procedure should
only take a few minutes at most; it is potentially faster than
attempting to deduce which attributes could be the cause.