Then I realized that it has to do with urlac and I solved deleting old ones with following commands: (from elevated cmd)Īfter that simply start as usual, the tool will recreate what necessary.Īnother option is to change the ip binding that the emulator uses in the config file located in the storage emulator directory. I noticed that it was starting with option -inprocess from elevated cmd. I had same issue since I had to rejoin my machine to the domain and the user profile got recreated. It is also worth to try to run the command prompt with: "Run As Administrator"Ĭ:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start Run Microsoft Azure Command Prompt as administrator and try to first initialize using AzureStorageEmulator.exe init and then start using AzureStorageEmulator.exe start commands. If that doesn't help, you can try to launch the emulator with the -inprocess flag to get a more detailed error message: WAStorageEmulator start -inprocess Note that if you elevate as a different user to run initialization, then the initialization only applies to that user. Make sure the user that initialized the emulator is the same as the user that is starting the emulator. If this did not resolve the issue try second step.Ģ) Run this netsh http add iplisten 127.0.0.1Īnd then in the Azure Storage Emulator's command prompt type AzureStorageEmulator.exe start -inprocessĬtrl+c and then AzureStorageEmulator.exe start In the Azure Storage Emulator's command prompt typeĪzureStorageEmulator.exe start -inprocess Now start the Azure Storage Emulator in -inprocess mode To know this you can type the below command in the command prompt netstat -na | find "10000" If you are unable to open the URL or if there is a error, this is the reason why you are not unable to start Azure Storage Emulator.ġ) Check if the port 10000 is busy or used by any other process. Try to open URL for "Blob" in a web browser. Open C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe file in a notepad or a notepad++ editor.
Summarizing and adding additional points to other answers to this question.
AZURE STORAGE EMULATOR LOCALDB WINDOWS
After hours of research I found strange solution - set 'Start Windows Azure storage emulator' to 'False' (in properties of Azure project).
AZURE STORAGE EMULATOR LOCALDB UPDATE
I have same issue after Azure tools update (2.3 version).