We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

Troubleshooting Deployment Diagrams 

When you work in Distributed System Designers, certain actions affect the deployment diagram and other items in the solution. This topic describes conditions that result from performing these actions and steps that you can take to resolve these conditions.

In Deployment Designer, orphaned shapes on the deployment diagram have a red dashed outline and the name of the shape appears in red. Orphaned shapes can occur when the logical datacenter diagram is modified or removed from the solution while the deployment diagram is closed.

If logical servers were removed from the logical datacenter diagram, those shapes appear orphaned when the deployment diagram is reopened.

To remove these orphaned shapes, synchronize the deployment diagram with the logical datacenter diagram. For more information, see How to: Synchronize Deployment Diagrams with Logical Datacenter Diagrams.

If the logical datacenter diagram was removed from the solution, all shapes on the deployment diagram appear orphaned.

To resolve this condition, add the missing logical datacenter diagram back to the solution.

When you bind a Web application that has multiple provider endpoints to an IIS Web server that has multiple Web site endpoints, Deployment Designer lets you bind the provider endpoints to different Web sites. However, this binding is an error. All provider endpoints on a single Web application must be bound to the same Web site endpoints.

The deployment report does not specify which application pool each application is bound to.