Troubleshooting

This page covers troubleshooting steps for ModelCenter MBSE.

Run or Export Execution Plan button grayed out/not available

If the Run button or Export Execution Plan button is grayed out, this indicates that the selected Execution Plan is incomplete or has errors that prevent ModelCenter MBSE from running the plan.

Steps to Resolve:

  1. Inspect the Execution Plan:
    1. Is an Execution Plan tab loaded as the visible tab?
    2. Is there at least one selected, valid Analysis?
    3. Is the Execution Plan missing linked/required information for the selected Analyses?

    4. Is there a red Error symbol in the Execution Plan?

  2. Resolve the individual issues, either in ModelCenter MBSE or in an external application as necessary.
  3. Run or export the Execution Plan.

Save baseline values button grayed out/not available

If the Save baseline values button is grayed out, this indicates that an Execution Results tab is not selected or has errors that prevent ModelCenter MBSE from running the plan.

Steps to Resolve:

  1. Inspect the Execution Results tab:
    1. Is an Execution Results tab loaded as the visible tab?

    2. Is there an error message at the top of the Execution Results tab? And/or is there a red Error symbol in the Execution Results tab?

  2. Resolve the individual issues, either in ModelCenter MBSE or in an external application as necessary.
  3. Run or export the Execution Plan.

Error Building ModelCenter Workflow

There are several possibilities for the "Error Building ModelCenter workflow" error:

  1. Error building ModelCenter workflow. ... component could not be connected to source. ... component [name] does not match a known component.
  2. Error building ModelCenter workflow. Error: Can't parse number. Reason: Number overflow

Error building ModelCenter workflow.

Analysis: [ID]: 
    * component could not be connected to source. Cannot describe:
        exampleValidators/lessThan Reason: ERROR: PHXClassNotFoundException: component [name] does not match a known component

This error indicates that there was a problem when ModelCenter attempted to build the workflow. Note that the Execution Plan tab on the left is marked with the yellow Warning symbol , which indicates that a problem was noted on the Execution Plan before it was run.

Steps to Resolve:

  1. Edit the Analysis outside of ModelCenter MBSE to resolve the error.
  2. Check that the Analysis in ModelCenter MBSE is correct.
  3. Re-run the Execution Plan.

Error building ModelCenter workflow.

Error: Can't parse number Reason: Number overflow

This error indicates that the entered value was larger than a 32-bit number, and therefore was too large for ModelCenter to handle.

Steps to Resolve:

  1. Edit the Execution Plan tab to use a smaller number for this variable.
  2. Re-run the Execution Plan.

Alternately:

  1. Edit the Systems Model outside of ModelCenter MBSE to scale the system appropriately, so that the variable is not over the limit.
  2. Re-run the Execution Plan.

Cannot interact with the Execution Plan window

Solution: the Analysis Editor dialog is most likely open.

Steps to Resolve:

  1. Look for the Analysis Editor dialog:
    1. Is it minimized?
    2. Is it on another monitor?
    3. Is it covered by another application?
  2. Close the Analysis Editor dialog.

Cannot Edit Values in the Execution Results Tab

The values in an Execution Results tab cannot be changed. Instead, the initial values in the Execution Plan should be changed and the Execution re-run with the new values.

Steps to Resolve:

  1. Click the Execution Plan tab that generated the Execution Results tab.
  2. Edit the values in the Execution Plan tab.
  3. Re-run the Execution Plan with the new values.

Failed to save design instance

Solution: save a Design Instance from a block structure element, not from a variable or any other type of structure element (e.g., package) in the model.

Steps to Resolve:

  1. Click on a block in the execution results tab.
  2. Save the design instance.

Errors connecting to ModelCenter Remote Execution

Error: Cannot connect to ModelCenter Remote Execution

This error indicates that the Server Address for the ModelCenter Remote Execution is not correct.

Steps to resolve:

  1. Correct the MCRE server address listed in the Server Address field.
  2. Click the Click to retry link in the error message, or click the Connect button next to the Server Address field.

Error: Cannot connect to: [MCRE server address and port]

Reason: No connection could be made because the target machine actively refused it.

This error indicates that the ModelCenter Remote Execution may not be running at the Server Address.

Steps to resolve:

  1. Check that ModelCenter Remote Execution is running at the indicated Server Address.
  2. Check that the MCRE server address is correct.
  3. Click the Click to retry link in the error message, or click the Connect button next to the Server Address field.

Cannot connect to: [MCRE server address and port]

Reason: The requested name is valid, but no data of the requested type was found.

Solution: Make sure you have specified a valid host name and that the ModelCenter Remote Execution is running on that machine. This error indicates that the Server Address may be invalid or the MCRE server may not be running at the Server Address.

Steps to resolve:

  1. Check that ModelCenter Remote Execution is running at the indicated Server Address.
  2. Check that the MCRE server address is correct.
  3. Click the Click to retry link in the error message, or click the Connect button next to the Server Address field.

Cannot get hierarchy. ERROR: ModelCenterException

ERROR: ModelCenterException: Cannot describe: [location]. 
ERROR: PHXClassNotFoundException: component [address] does not match a known component.

This error indicates that a component in the Analysis could not be found at the indicated location.

Steps to resolve:

  1. Edit the Analysis outside of ModelCenter MBSE to ensure the component is in the correct location.
  2. Reload the Analysis in Analysis Editor.

Cannot start session. ERROR: PHXClassNotFoundException

ERROR: PHXClassNotFoundException: component [name] does not match a known component

This error indicates that a component in the Analysis could not be found at the indicated location.

Steps to resolve:

  1. Edit the Analysis outside of ModelCenter MBSE to ensure the component is in the correct location.
  2. Reload the Analysis in Analysis Editor.

Variable type is not supported

This error indicates that a variable type in the selected Analysis is not supported in ModelCenter MBSE.

Steps to resolve:

  1. Edit and save the Analysis outside of ModelCenter MBSE to correct the variable type.
  2. Reload the Analysis in Analysis Editor.

OK and/or Apply button is grayed out

There are several reasons why the OK and Apply buttons may be grayed out. Hover over a button to see the error:

  1. Not all Analysis variables have been mapped.
  2. The proposed Analysis name is invalid.
  3. The tool configuration for this Analysis is not valid.
  4. No error tooltip displays (Apply button)

1. Not all Analysis variables have been mapped.

All variables in the Analysis Variables section must be mapped to a Systems Model Structure, a Requirement, a constant, or an operator.

Steps to resolve:

  1. How to create Links
  2. How to add a Constant Value or Operator
Note: There is an another explanation for this same message: if the Margin variable from a Requirement is linked to an Analysis Variable, the Is Satisfied variable must be linked as well. If the Is Satisfied variable is not linked, then this message will also display.

Steps to resolve:

  1. Link the Is Satisfied variable to the appropriate Analysis Variable.

Alternately:

  1. Unlink the Margin variable.
  2. Ensure all Analysis Variables are linked appropriately.

2. The proposed Analysis name is invalid.

Analysis names must be unique within the Analyses List for the systems model.

Steps to resolve:

  1. Give the Analysis a unique name.
  2. Click the Apply button to save the Analysis Name, or click the OK button to both save the Analysis Name and close the dialog.

3. The tool configuration for this Analysis is not valid.

This message may be seen in an Analysis that is being edited. It indicates that there is an error in finding the Analysis' location.

Steps to resolve:

  1. Close the Analysis Editor.
  2. Check that the Analysis is located in the expected location on the selected ModelCenter Remote Execution.
  3. Re-open the Analysis to edit.

4. No error tooltip displays (Apply button)

This indicates that you are editing an Analysis and no changes have been made yet. Updating only the Analysis Name field does not trigger the Apply button.

Steps to resolve:

  1. Click the OK button to save the Analysis Name and exit the dialog.

Alternatively:

  1. Click on one of the Analysis Variables to highlight it.
  2. Click the Apply button to save the Analysis Name.

Name is not a valid Analysis name/Analysis Name field is red

Note: If the Analysis Name field is highlighted in red to indicate an error, then the OK and Apply buttons will also be grayed out and unavailable; see the The proposed Analysis name is invalid section.

Name was empty or contained only whitespace.

An Analysis name must contain at least one character (besides whitespace/Space).

Steps to resolve:

  1. Give the Analysis a name that is not empty or only whitespace.
  2. Click the Apply button to save the Analysis Name, or click the OK button to both save the Analysis Name and close the dialog.

Name either contains invalid characters or the name already exists.

Analysis names must be unique within the Analyses List for the systems model.

Steps to resolve:

  1. Give the Analysis a unique name.
  2. Click the Apply button to save the Analysis Name, or click the OK button to both save the Analysis Name and close the dialog.