Error Messages

NI Requirements Gateway 2018 Help

Edition Date: March 2018

Part Number: 371714F-01

»View Product Info
Download Help (Windows Only)

Rule violations that result in incomplete or inaccurate project analysis appear as error messages on the Rule Check pane. The following table lists possible error messages, explains each error, and suggests how to resolve each error.

Error Message Explanation Resolution
Covered document not found The .rqtf file that corresponds to the project is corrupted and contains a covered document that you specified but that the project does not define. Resave the project and use the Project pane of the Configuration dialog box to specify the covered document.
Covering document not found The .rqtf file that corresponds to the project is corrupted and contains a covering document that you specified but that the project does not define. Resave the project and use the Project pane of the Configuration dialog box to specify the covering document.
Analysis error Requirements Gateway locates an error in the intermediate file. This error can occur if the XML file uses an invalid format or Requirements Gateway cannot access the intermediate file. Close and restart Requirements Gateway.
Bad requirement level The definition of the requirement element for a type contains improper syntax in the regular expression used for capturing and nesting requirements. The capture requirements do not follow the hierarchy the type specifies. Correct the source document to match the captured hierarchy or correct the expression syntax for the requirement element of the type to capture and nest requirements.
Closing expression found without opening expression A type element definition contains a closing expression without the expected opening expression. This error affects requirement, macro-requirement, or section expressions. This error can occur when the source file structure or the intermediate file contains inconsistencies in the expression syntax or when the type element definition contains an incomplete definition of the section hierarchy. Modify the source document or intermediate file to insert the missing opening expression or delete a duplicate closing expression. If you are editing expressions in a type, determine whether the expressions used properly analyze the project document source file content.
COM error Communication with an external application fails. This error can occur when the application declares an obsolete COM library, another application uses the same COM interface at the same time, or if the application is not installed or incorrectly installed. Reinstall the external application or investigate and resolve the COM error.
Conversion problem Requirements Gateway cannot analyze the document. This error can occur when the document has an unknown or obsolete format, such as Microsoft Word 95. Update the document to use a supported format or use a different type that supports the file format.
Converter not found The project contains a type that is based on a conversion tool that is not available. For example, this error can occur if you developed a proprietary conversion tool for use in a previous version of Requirements Gateway and you then upgraded to the current version of Requirements Gateway. Update the conversion tool for compatibility with the current version of Requirements Gateway.
Cover link source not found Requirements Gateway cannot find a reference defined in a source document. This error can occur when you define two groups of parentheses in the regular expression for the reference element of a type. The first group of parentheses specifies the target, and the second group of parentheses specifies the source that Requirements Gateway cannot find. Verify that the source exists and that the regular expression defined for the reference element of the type is correct.
Cyclic graph creation not allowed Requirements Gateway cannot analyze the parent-child relationship in a source document. This error can occur when you define a parent element and a child element in the type but you use the child element in hierarchical levels higher than the parent element in a source file. An example of cyclic graph creation is a Heading 2 section that contains a Heading 1 section. Correct the source document to match the captured hierarchy, or correct the expression syntax for elements of the type to nest elements.
Document not found Requirements Gateway cannot find the target document defined for a link element of a type. Verify that the source document exists and verify that the regular expression defined for the link element of the type is correct.
Document not readable A document you defined in the project is not available. This error can occur when you do not have the privileges required to access a remote file, the file has been renamed or moved, or the type of analysis applied to the document does not match the file type. Verify your access privileges, rename, move, or create the missing file, or apply the appropriate type to the document.
Embedded document not found Requirements Gateway cannot find a document that a folder in the project includes. This error can happen when the .rqtf file that corresponds to the project is corrupted. If you modified the .rqtf file that corresponds to the project in applications other than Requirements Gateway, revert the changes you made.
Entity tag found in macro-requirement Requirements Gateway captures an entity between the opening and closing tags of a macro-requirement definition. Requirements Gateway does not permit entities within macro-requirements. Delete the entity.
File access error A file in the project is not available. This error can occur when you do not have the privileges required to access a remote file, the file has been renamed or moved, or the type of analysis applied to the file does not match the file type. Verify your access privileges, rename, move, or create the missing file, or apply the appropriate type to the file.
Impossible to delete Requirements Gateway captures an element, but the element does not exist. This error can occur when you customize a type to delete requirements marked as obsolete. Remove the expression to delete an element in the type definition.
Invalid parent type Requirements Gateway cannot analyze a parent for an element defined for the type. Verify that the regular expression definition for the parent element of the type.
Inverse reference without requirement Requirements Gateway captures a reference in an inverse coverage relationship but cannot capture the requirement that contains the reference. Define a requirement to contain the reference.
Link source not found Requirements Gateway cannot find the source of a link element in a project document. Verify that the source document exists and verify the regular expression definition for the link element of the type.
Link to undefined requirement Requirements Gateway cannot find the target requirement of a reference anywhere in the project. This error can occur when a defined requirement no longer exists, the requirement name contains a syntax error, or a covering element references a requirement that you have filtered from the analysis. Define the requirement in one covering document, correct the syntax error, or remove the filter.
Macro-requirement defined several times A macro-requirement is defined more than once in the same document using the same name. Rename the macro-requirement.
Mirror requirement with different attribute value A requirement in mirror documents contains label, text, or attribute values different from the same requirement in the main document. Modify the label, text, or attribute values of the requirement in the main or mirror document.
Mirror requirement without main requirement You defined the mirror link type between an upstream document and a downstream document in the project, but Requirements Gateway cannot find the same requirement in the upstream document for a requirement in the downstream document. Remove the requirement from the downstream document.
Missing mirror requirement You defined the mirror link type between an upstream document and a downstream document in the project, but Requirements Gateway cannot find the same requirement in the downstream document for a requirement in the upstream document. Add the requirement to the downstream document.
Multiple use of same GUID Requirements Gateway captures multiple elements with the same GUID. This error can occur when you add or import the same document with unique GUID to the project for more than once . Verify that you are not adding or importing a document which already exists in the project.
Non-covering entity Requirements Gateway captures an entity that does not have a higher-level requirement. This error can occur when commented code exists within a code document. Delete the non-covering entity.
Opening expression found without closing expression A type element definition contains an opening expression without the expected closing expression. This error affects requirement, macro-requirement, or section expressions. This error can occur when the source file structure or the intermediate file contains inconsistencies in the expression syntax or when the type element definition contains an incomplete definition of the section hierarchy. Modify the source document or intermediate file to insert the missing closing expression or delete a duplicate opening expression. If you are editing expressions in a type, determine whether the expressions used are written to properly process the source file.
Parent not found Requirements Gateway cannot find a parent for a section element defined for the type. Verify that the parent exists in the source document and verify the regular expression definition for the parent section element of a type.
Requirement defined several times A requirement or derived requirement is defined several times in the same document. A requirement cannot have the same definition as a derived requirement. Rename the requirement.
Requirements defined in several documents, and the documents are covered by a shared document One document covers two documents and each covered document contains a requirement, derived requirement, or macro-requirement whose ID is identical to an ID contained in the other covered document. Specify different requirements in each covered document.
Section with same identifier Two sections that occupy the same hierarchical level have the same ID. This error can occur when two headings use the same ID number. Specify different IDs for each section.
Self covering requirement A reference refers to itself. Create a separate requirement for the reference to cover or delete the self-covering reference.
Too many results found. A capture expression may be wrong One regular expression captures more than 50,000 results. This error warns against excessive memory consumption, which can potentially cause a system crash. If you intend to capture more than 50,000 results with one expression, and if you are a user with administrator privileges, edit the nirg.ini file located in the <Requirements Gateway>\bin.w32 directory to define a variable, maxFoundResults=<your number>, in the [General] section. Create the [General] section if it does not exist.
Traceability Graph Violation An element references a requirement in a document that does not cover the document that contains the reference. Double-click a Traceability Graph Violation error on the Rule Check pane to select the affected source document in the Graphical view and refer to the Messages pane for more information about the error. Create a reference between the two documents for direct traceability. You can also delete or modify the reference.
Unauthorized attribute value Requirements Gateway captures an attribute with a value not included in the defined list of values for the attribute element of the type. Add the value of the captured attribute to the defined list of values on the Attributes tab of the Types pane of the Configuration dialog box or modify the value of the attribute in the document to use a value specified in the defined list of values.
Uncovered requirement The project contains a requirement, derived requirement, or macro-requirement that no covering document references. Requirements Gateway does not apply this rule for requirements of low-level documents or for a document that covers itself. Add a reference in the covering document for the requirement, derived requirement, or macro-requirement.
Undefined covering requirement/entity A covering element no longer exists or contains a syntax error. Rename or define the covering element.
Unknown document type The project contains a document that does not match any of the available types. This error can occur when the .types file is lost or moved or when one user defines a local type and a second user opens the project using a different Requirements Gateway configuration that does not include the type. Requirements Gateway automatically replaces the unknown type with the default Text type. Add the unknown type to the project as a custom type so that you can use the correct type.
Unknown element type The source document contains an element that does not match any of the available element types. Modify the definition of the source document type to capture the element.
Unknown parent type The source document contains a parent element, but the parent element does not match any of the element types that allows nesting child elements. Modify the definition of the element type to allow nesting child elements.

WAS THIS ARTICLE HELPFUL?

Not Helpful