Skip to main content
insightsoftware Docs insightsoftware Docs
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Troubleshooting Modeling Workbench

In this section, you can find more information about solving problems that might occur during Modeling Workbench operation.

Import warnings

You may encounter one of the following warnings if you import new content. Warnings that are self-explanatory are not described here.

  • The specified extension type doesn’t exist

    The module specifies an extension type that does not exist (anymore). The value has been set to None. An appropriate existing extension type can be selected in the Workbench.

  • The specified license label doesn’t exist

    The module specifies a license label that does not exist (anymore). The value has been excluded from the list of license labels. An appropriate existing license label can be added in the Workbench.

  • Key ‘…’ in [ModuleInfo] section not recognized, line will be skipped

    The key mentioned in the warning is not recognized as a valid module property. The entire line is skipped. When the key contains a typo, add the value to the appropriate module property in the Workbench. When the key is not (yet) supported, please notify your EA contact person and add the entire line to the comment property for future reference.

  • [ModuleInfo] section won’t be parsed as it is found, but not at the top of the file

    The imported file contains a [ModuleInfo] section, but it is not located at the top of the file. This is required for the import. Therefore, a new [ModuleInfo] section is added as header during import and the existing [ModuleInfo] section is ignored. Verify in the Workbench whether all module properties are imported correctly.

  • No restructure module with name ‘…’ exists in model ‘…’, configuration extension will be skipped

    The specified restructure module does not exist in the specified model. The configuration extension is not imported. Make sure that the module is imported or added to the model and re-import the configuration extension.

  • Module ‘…’ is not a recognized configuration extension module type, configuration extension will be skipped

    The specified module is not recognized as a valid configuration extension module type. The configuration extension is not imported. The system does not support the configuration extension module type (yet). Please notify your EA contact person.

  • Multiple segments with name ‘…’ found in module ‘…’; segments will be joined

    The specified segment occurs multiple times in the specified module. The segments have been grouped together. Use the content editor to remove the duplicate segment headers from the module.

Published:

Troubleshooting Modeling Workbench

In this section, you can find more information about solving problems that might occur during Modeling Workbench operation.

Import warnings

You may encounter one of the following warnings if you import new content. Warnings that are self-explanatory are not described here.

  • The specified extension type doesn’t exist

    The module specifies an extension type that does not exist (anymore). The value has been set to None. An appropriate existing extension type can be selected in the Workbench.

  • The specified license label doesn’t exist

    The module specifies a license label that does not exist (anymore). The value has been excluded from the list of license labels. An appropriate existing license label can be added in the Workbench.

  • Key ‘…’ in [ModuleInfo] section not recognized, line will be skipped

    The key mentioned in the warning is not recognized as a valid module property. The entire line is skipped. When the key contains a typo, add the value to the appropriate module property in the Workbench. When the key is not (yet) supported, please notify your EA contact person and add the entire line to the comment property for future reference.

  • [ModuleInfo] section won’t be parsed as it is found, but not at the top of the file

    The imported file contains a [ModuleInfo] section, but it is not located at the top of the file. This is required for the import. Therefore, a new [ModuleInfo] section is added as header during import and the existing [ModuleInfo] section is ignored. Verify in the Workbench whether all module properties are imported correctly.

  • No restructure module with name ‘…’ exists in model ‘…’, configuration extension will be skipped

    The specified restructure module does not exist in the specified model. The configuration extension is not imported. Make sure that the module is imported or added to the model and re-import the configuration extension.

  • Module ‘…’ is not a recognized configuration extension module type, configuration extension will be skipped

    The specified module is not recognized as a valid configuration extension module type. The configuration extension is not imported. The system does not support the configuration extension module type (yet). Please notify your EA contact person.

  • Multiple segments with name ‘…’ found in module ‘…’; segments will be joined

    The specified segment occurs multiple times in the specified module. The segments have been grouped together. Use the content editor to remove the duplicate segment headers from the module.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk