Strange behavior of Windows Azure Compute Emulator (SDK 2.3)

Question

Today, after an update of the Azure SDK from 2.2 to 2.3, I noticed that only one of the two instances of my web role is started in
the Azure Compute Emulator, the output of the Start-AzureEmulator is this:
VERBOSE: Starting Emulator...
VERBOSE: Role is running at http://127.0.0.1:81/
Role is running at tcp://127.0.0.1:3389/
Role is running at tcp://127.0.0.1:3389/
VERBOSE: Started
and only one instance is started in the Azure Compute Emulator.
But in the past was something similar to this one:
VERBOSE: Starting Emulator...
VERBOSE: Role is running at http://127.0.0.1:81/
http://127.0.0.1:82/
Role is running at tcp://127.0.0.1:3389/
Role is running at tcp://127.0.0.1:338/
VERBOSE: Started
and two instances were started.
I already found this thread:
http://stackoverflow.com/questions/13946634/strange-behavior-of-windows-azure-compute-emulator-sdk-1-8-with-multiple-role
but it was not useful in my case (Microsoft.WindowsAzure.Common.WorkArounds.BindToAllIpsWorkAroundEnabled is False).
Thanks in advance for any help.
OS: Windows 8.1
Azure SDK: 2.3
Azure Compute Emulator: 2.3.0.0

Answer 1

Hi,
As far as I know, powershell didn't have a parameter to start azure emulator with full express, please try to use Command-line to test, refer to
http://msdn.microsoft.com/en-us/library/gg433130.aspx for more details, if this didn't give you help, please feel free to let me know.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.