The Docker image names which are displayed by default in Performance Center Administration (under Orchestration) are misspelled

In the Docker Images tab in Orchestration, the predefined image names below are misspelled, and the images do not actually exist until they have been pulled from Docker hub into the local orchestrator.
1. performancetesting/load_generator_linux:12.60
2. performancetesting/load_generator_win:12.60

To fix this issue
1. Delete the default images, and then create new images as follows:

For a Dockerized Linux 12.60 Load Generator image:
1. Image Name: performancetesting/load_generator_linux
2. Image Type: UNIX (not Linux as in predefined image)
3. Purpose: Load Generator
4. Image Tag: 12.60

For a Dockerized Windows 12.60 Load Generator image:
1. Image Name: performancetesting/load_generator_windows
2. Image Type: Windows
3. Purpose: Load Generator
4. Image Tag: 12.60

2. Pull the images from your Orchestrator node (Swarm/Kubernetes). For example:

Docker pull performance testing/load_generator_windows:12.60

Error:”Failed to stop test. Reason: ‘There was no endpoint listening at net.pipe://localhost/CntrlService/Service…” when running a test in Performance Center

When trying to run a performance test in which a topology is defined, the test stops abnormally shortly after it has started. The following error message is displayed in the event log of the run:

"Failed to stop test. Reason: ‘There was no endpoint listening at net.pipe://localhost/CntrlService/Service that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."

The topology uses SiteScope version 11.20.

To fix this issue delete all monitors and hosts that were configured in SiteScope and recreate them.

Unable to add a Host in Performance Center

When adding a host on PC 9.x it shows the credentials popup, the event viewer shows the below error

Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10016

Date: 8/29/2011

Time: 1:26:03 PM


Computer: KCH1D068


The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7E89FF0B-F649-4F9A-A9C3-F05DFAAA3DA1} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at

This is because the DCOM server has no permissions to start

To fix this issue modify the DCOM permissions:

Start -> Run -> dcomcnfg

Expand Component Services, expand Computers , expand My Computer , expand DCOM Config

Right click on SMS Agent Host , click Properties

Select the Security tab, click Edit in the Launch and Activation Permissions section

Select System , ensure Local Launch is Allowed

Click OK, Click OK

additional details here