This documentation is archived and is not being maintained.

Troubleshooting System Diagrams 

When working in System Designer, certain actions affect the system diagram as well as other distributed system diagrams. This topic describes certain conditions that result from performing these actions, their impact on associated items, and steps you can take to resolve these conditions. The following list describes alert states that can arise from these actions as well as other areas in which you might need to troubleshoot issues:

The following table describes alert states that appear on a system diagram.

Alert state Possible cause

Red dashed outline

One of the following:

  • The underlying definition of system member was renamed while the system diagram was closed.

  • The underlying definition of a system member is missing or deleted.

The following section contains more information about the alert states that might appear.

Error Alert States on System Diagrams

Error alert states might appear on a system diagram under the following conditions:

  • The underlying definition of a system member was renamed while the system diagram was closed.

    Members of a system are linked to their underlying definitions by name. Therefore, renaming definitions breaks the links to their uses on closed system diagrams because they are not updated. When these system diagrams are reopened, the member whose definition was renamed while the diagram was closed displays a red dashed outline. In addition, a squiggly line appears below the definition name, which could not be found, on the member shape to help you resolve the broken link.

    NoteTip

    To resolve this condition, you can delete the member from the system diagram, or you can revert the definition to its previous name. You can also revert the definition name temporarily so that you can rename it while the system diagram is open. For more information, see How to: View Application and System Definitions from System Diagrams and How to: Rename Applications on Application Diagrams.

  • The underlying definition of a system member is deleted or missing.

    System members display a red dashed outline when their underlying definitions have been deleted or are missing. In addition, a squiggly line appears below the definition name on the member shape. Missing application definitions can also include missing application definition (.sdm) files, such as for external Web services, databases, and generic applications. Missing system definitions are missing system diagram (.sd) files.

    The following table describes scenarios in which this condition can also occur.

    Scenario Resolution

    Deleting the underlying definition of an application or system.

    Delete its use from system diagrams that reference that definition. For more information, see How to: Delete Applications and Systems from System Diagrams.

    The definition of an application or system is missing.

    Add the missing definition to the solution. For example, if the missing definition is an unimplemented application, add an application of the same type to the application diagram. If the missing definition is a system, add the system diagram back to the solution. For more information, see How to: Define Applications on Application Diagrams and How to: Add System Diagrams to Solutions.

    Removing or unloading a project associated with an application definition from the solution.

    Add the project back to the solution or reload the project. For more information, see How to: Reverse-Engineer Projects in Existing Solutions and How to: Unload and Reload Projects.

    Adding a system diagram from another solution.

    Add projects associated with missing application definitions to the current solution. For more information, see How to: Reverse-Engineer Projects in Existing Solutions. If application definitions are unimplemented, add a new application of the same type to the application diagram. You can also implement the applications in the other solution and then add their projects to the current solution. For more information, see How to: Implement Applications on Application Diagrams.

    Copying a member of a system between system diagrams in different solutions or instances of Visual Studio.

    For a missing application definition, copy the definition to the application diagram in the current solution. If the application definition is implemented, add the project for that application. For more information, see How to: Reverse-Engineer Projects in Existing Solutions. For a missing system (member) definition, add the system diagram defining that system to the current solution. For more information, see How to: Add System Diagrams to Solutions.

Opening, closing, or removing a system diagram from a solution has the following impact on other diagrams in the solution:

  • Opening a system diagram opens the application diagram and any other system diagrams that are referenced by the opened system diagram.

  • Closing a system diagram requires saving and closing any system and deployment diagrams that reference that system diagram.

    NoteTip

    To close a system diagram without saving it, first close any related system or deployment diagrams.

  • Before removing a system diagram from the solution, you must close all other open diagrams in the solution.

Adding a new system diagram and performing actions on that diagram, such as adding a use of an application definition, while code is running causes Visual Studio to stop responding.

NoteTip

To avoid this condition, stop code execution before performing actions on the diagram.

Show: