Skip to main content
R
rzheng1-Visitor
1-Visitor
October 22, 2015
Solved

Error MKS124066: Type "ALM_Requirement Document" does not exist. what reason?

  • October 22, 2015
  • 1 reply
  • 4559 views

It had happened when I imported a reqiurement document (Integrity v10.6).

Thanks!

    Best answer by VolkerEckardt

    Hi Roy,

    can you check whats the correct name for your Requirement Document type inside your Integrity Admin? Perhaps without Prefix?

    Then, check the file gateway-tool-config.xml located in your client (or gateway server directory) if this name (with prefix ALM_) is there. Then, adapt the names to match to what you have in your Integrity Admin.

    Does this help?


    Volker

    1 reply

    V
    VolkerEckardt17-PeridotAnswer
    17-Peridot
    October 22, 2015

    Hi Roy,

    can you check whats the correct name for your Requirement Document type inside your Integrity Admin? Perhaps without Prefix?

    Then, check the file gateway-tool-config.xml located in your client (or gateway server directory) if this name (with prefix ALM_) is there. Then, adapt the names to match to what you have in your Integrity Admin.

    Does this help?


    Volker

    R
    rzheng1-VisitorAuthor
    1-Visitor
    October 23, 2015

    Hello, Volker

    Thanks! I checked  my Requirement Document type inside your Integrity Admin as following:

    RequirementTypeAdmin.JPG

    Is it without Prefix?  How do I modify it?

    and I searched "ALM_Requirement" in gateway-tool-configuration.xml file,  but no found anything.

    Thanks!

    V
    VolkerEckardt17-Peridot
    17-Peridot
    October 23, 2015

    Roy,

    Ok, hm, can you please tell me which Import configuration you choose?

    And, is it right that you import a word document  (docx)?

    Volker

    Terms & ConditionsAccessibility statement