Windows Azure SDK Compute Emulator Listen Port Unavailable
Updated: September 21, 2011
Applies to: Windows Azure SDK 1.5 and Windows Azure SDK for .NET
Symptom: You can encounter this error when you use Microsoft Visual Studio or the CSRun Command-Line Tool to run an application in the Compute Emulator.
When you use Microsoft Visual Studio to run an application, you receive the following error message:
One or more ports used by the Compute Emulator are currently used by other processes. To resolve this, please see MSDN documentation at http://msdn.microsoft.com/en-us/library/hh472164.aspx
When you use the CSRunCommand-Line Tool to run an application, the Compute Emulator attempts to start, but quickly fails. The following message is displayed in the notification area:
When this error occurs, the following message is entered into c:\users\<username>\AppData\Local\dftmp\DevFCLogs:
Exception occurred when trying to open service host. {0}, {1}`There is already a listener on IP endpoint 127.0.0.1: 15095. Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint.
Cause: Another service is using a porton which one of the Compute Emulator services is listening.
Resolution:
-
Determine if any of the following ports are being used by a non-Windows service: 15095, 15096, 15097, 15098, 15099, or 15100.
-
Navigate to the installation directory of the Compute Emulator. By default the Compute Emulator is installed at C:\Program Files\Windows Azure Emulator\emulator\devfabric.
-
In the DevFc.exe.config file, locate the add port entry that contains the conflicting port value and modify the value to use a non-conflicting port. The DevFc.exe.config file entries that can be affected are:
-
<add key="ManagementServicePort" value="15095" />
-
<add key="RepositoryServicePort" value="15096" />
-
<add key="AgentCallbackPort" value="15097" />
-
<add key="AgentPort" value="15098" />
-
<add key="PxeResponderPort" value="15100" />
-
<add key="ManagementServicePort" value="15095" />
-
In the DfService.exe.config file, locate the dfservice element and modify the ManagementServicePort or RepositoryServicePort attribute to use a non-conflicting port.
-
<dfservice ManagementServicePort="15095" RepositoryServicePort="15096" />
-
<dfservice ManagementServicePort="15095" RepositoryServicePort="15096" />
-
Press F5 to restart the application or run the CSRun Command-Line Tool.
Symptom:
When you use Microsoft Visual Studio to run an application, you receive the following error message:
Unable to connect to dfService.
When you use the CSRun Command-Line Tool to run an application, the Compute Emulator attempts to start, but quickly fails. The following message is displayed in the notification area:
When this error occurs, the following message is entered into c:\users\<username>\AppData\Local\dftmp\DevFCLogs:
Exception occurred when trying to open service host. {0}, {1}`There is already a listener on IP endpoint 127.0.0.1:12001. Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint.
Cause: Another service is using a port that on which one of the Compute Emulator services is listening.
Resolution: To correct the issue:
-
Identify any non-Windows Azure service that is listening on the following ports: 12000, 12001, 12002, 808, 16001, or 15100.
Tip For example, VMWare Workstation Server listens on port 12001. -
Stop the identified service.
-
Press F5 to restart the application.
See Also