NOTICE: Our Community is moving. Get more information.
Why do I receive a "...C++ Runtime Error..." when accessing traces to Quality Center?
When accessing the Traceability Tab for a requirement, a C++
Runtime Error is displayed, and the CaliberRM client shuts
down. The requirement(s) in question, have traces to QC that
are attempting to be retrieved right before the error occurs.
If the QC Server is shut down, so that it is completely
unavailable to the CaliberRM Client, the trace is not retrieved and
is listed as "unavailable trace" however the CaliberRM
Client does not crash.
Upon viewing the structure of the corresponding requirement in
the QC web client, there seemed to be a recursion of the
requirement tree nested within itself. Though the requirement
seemed to display ok, modifying a field and attempting to save the
changes also resulted in a crash of the QC client.
This issue was seen during integration testing, and could have
resulted from several configuration changes, possibly being made
during pending operations or even changes made directly in the QC
If the problem is isolated, you may delete the upper branch of
the requirement tree in QC corresponding to the problem. A
subsequent publish from QC can be performed to recreate the
requirement and re-sync the trace.
If this scenario occurs wherein deleting the requirement branch
and starting over is not a viable option due to the number of
requirements or intricate workflow/traceability, the QC admin
should be brought in to troubleshoot on the QC side for any
database, or QC consistency checks to be performed.