Azure Storage Emulator error and does not start

Question

This error is really driving me crazy. (Terminal running in administrator mode)

Initialization of azure storage emulator in sql server 2014:

C:\Program Files (x86)\Microsoft SDKs\Windows Azure\Storage Emulator>.\wastorage
emulator init -server MY-PC
Windows Azure Storage Emulator 3.0.0.0 command line tool
The storage emulator was successfully initialized and is ready to use.

Error when starting server:

C:\Program Files (x86)\Microsoft SDKs\Windows Azure\Storage Emulator>.\wastorage
emulator start
Windows Azure Storage Emulator 3.0.0.0 command line tool

Unhandled Exception: System.TimeoutException: Unable to open wait handle.
   at Microsoft.WindowsAzure.Storage.Emulator.Controller.EmulatorProcessControll
er.InternalWaitForStorageEmulator(Int32 timeoutInMilliseconds)
   at Microsoft.WindowsAzure.Storage.Emulator.Controller.EmulatorProcessControll
er.EnsureRunning(Int32 timeoutInMilliseconds)
   at Microsoft.WindowsAzure.Storage.Emulator.StartCommand.RunCommand()
   at Microsoft.WindowsAzure.Storage.Emulator.Program.Main(String[] args)

just updating to latest VS version + SDK solved this problem for me in the end — BigChief, Aug 27 '14 at 22:10

score 167 · Accepted Answer · edited Aug 24 '15 at 20:17

167

Check if you are running BitTorrent/uTorrent or similar software using port 10000.

Check Steve Marx' blog post about the issue. http://blog.smarx.com/posts/windows-azure-storage-emulator-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process

In case that post disappears, the command to check if any other software is using that port is:

C:\Users\smarx>netstat -p tcp -ano | findstr :10000
  TCP    127.0.0.1:10000        0.0.0.0:0              LISTENING       3672

edited Aug 24 '15 at 20:17

DeepSpace101

13,110
9
77
127

answered Jul 29 '14 at 16:13

David Rodriguez

2,412
1
17
15

14

You just saved us lots of time – Andre Pena Aug 20 '14 at 00:08
27

I wonder how the microsoft developers build their apps. Rather than the unclear TimeoutException, can't the application just throw "Port Unavailable" exception ?!!! – Jalal El-Shaer Dec 30 '14 at 07:55
1

It's also worth running without "-p tcp". For me, it was Google Keep. – irwinb Jun 24 '16 at 23:18
Thanks, you made my day. – Elvis Nov 07 '16 at 09:33
1

If you don't like CLI's, hit WinLogo+R %windir%\system32\perfmon.exe /res (or open resource manager from performance tab in task manager), network tab -> tcp connections/listener ports – BigChief Dec 09 '18 at 02:51
1

For those that find this in 2022, for some reason Azurite has found its way onto my computer, guessing a VS update, THIS is what was taking the port! – Dale Francis Jun 14 '22 at 19:14

score 47 · Answer 2 · edited Aug 30 '23 at 15:01

47

Summarizing and adding additional points to other answers to this question.

Open C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe.config file in a notepad or a notepad++ editor. Look at the services section.

<services>
  <service name="Blob" url="http://127.0.0.1:10000/"/>
  <service name="Queue" url="http://127.0.0.1:10001/"/>
  <service name="Table" url="http://127.0.0.1:10002/"/>
</services>

Try to open URL for "Blob" in a web browser. In my case it is

http://127.0.0.1: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.

Try below steps to resolve the issue.

Check if the port 10000 is busy or used by any other process.

To know this you can type the below command in the command prompt

netstat -na | find "10000"

Kill the process.

Now start the Azure Storage Emulator in -inprocess mode

In the Azure Storage Emulator's command prompt type

AzureStorageEmulator.exe start -inprocess

Ctrl+c and then

AzureStorageEmulator.exe start

If this did not resolve the issue try second step.

Run this

netsh http add iplisten 127.0.0.1 and then in the Azure Storage Emulator's command prompt type

AzureStorageEmulator.exe start -inprocess

Ctrl+c and then

AzureStorageEmulator.exe start

edited Aug 30 '23 at 15:01

InvalidBrainException

2,312
8
32
41

answered May 04 '17 at 16:11

Ram Pratap

1,079
11
8

1

Huge help with this - other highly upvoted answers on different questions didn't have the netsh option detailed – Ryanman Apr 21 '19 at 15:11
1

I was facing this issue while trying to debug Azure Function locally and (2) worked for me. Thanks a lot for this! – The Inquisitive Coder Mar 03 '20 at 12:43
Useful info while debugging, the above solution worked for me. Thanks a lot. – kothari Jul 27 '20 at 11:48
2

This one finally worked for me (step 2). What exactly is this doing: `netsh http add iplisten 127.0.0.1` – open-collar Dec 08 '20 at 14:25
#2 worked, but I have no idea why. – Marz Apr 05 '22 at 14:41
Just doing `AzureStorageEmulator.exe start` worked for me – The Muffin Man Jun 14 '22 at 16:32

score 20 · Answer 3 · answered Oct 19 '20 at 04:23

The issue maybe port 10000 is being occupied. Storage emulator runs on port 10000. So you need to kill that process. On windows, open cmd as admin and run following commands.

First find the process occupying port 10000

netstat -ano | findstr :10000

kill the process

taskkill /PID <process id> /F

Now try starting emulator again.

score 17 · Answer 4 · answered Apr 29 '14 at 03:26

17

I have same issue after Azure tools update (2.3 version). After hours of research I found strange solution - set 'Start Windows Azure storage emulator' to 'False' (in properties of Azure project).

answered Apr 29 '14 at 03:26

AChudov

214
1
4

Sounds indeed like a strange solution. Then the storage emulator does not start? – BigChief May 03 '14 at 14:04
1

Inexplicably, this worked for me too. Project ran and WA Storage Emulator has started. How bizarre. – glosrob Jun 28 '14 at 14:18
4

Does it mean, that the Storage Emulator is running, even if you didn't use it before (e.g. after computer reboot)? If yes, than I had probably the same issue. It took me very long time to find it out. Simply the **"System" process (PID 4) was listening on port 10,000**, so it wasn't possible to find, what process was actually causing it. But then I found the Storage Emulator already running (just a process without any UI), so I terminated it and than I was able to start Azure project from Visual Studio, which started Storage Emulator. It seems it's always running after computer reboot. – David Ferenczy Rogožan Sep 18 '15 at 06:25
1

BTW it's not so bizarre. Just Storage Emulator is simply executed (probably) on system boot or somehow automatically at some point of time, so when you try to start another from Visual Studio, it fails. But only Storage Emulator (TCP port 10,000). Compute Emulator (ports 10,001 and 10,002) is not running, so it has to be executed from VS. – David Ferenczy Rogožan Sep 18 '15 at 06:31
1

How do set this? @AChudov – Kitwradr May 16 '21 at 13:49

score 16 · Answer 5 · edited Aug 13 '20 at 02:36

16

In the file C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe.config you need to change port numbers:

edited Aug 13 '20 at 02:36

spottedmahn

14,823
13
108
178

answered Jan 22 '20 at 06:51

bob

157
1
2

Please copy and paste the relevant code into your answer instead of linking to a screenshot of text. – BSMP Jan 22 '20 at 07:40

score 10 · Answer 6 · answered May 02 '14 at 15:39

10

Make sure the user that initialized the emulator is the same as the user that is starting the emulator. Note that if you elevate as a different user to run initialization, then the initialization only applies to that user.

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

answered May 02 '14 at 15:39

Michael Roberson - MSFT

1,621
12
9

1

hmzz maybe this might lead to something can you please help to come up with a solution? : 5/3/2014 4:05:28 PM [Info] Stopping Service: Blob Service Status: Blob http://127.0.0.1:10000/ False The process cannot access the file because it is being used by another process Error: Unable to start the storage emulator. – BigChief May 03 '14 at 14:08
1

@BigChief it probably means that a port is in use. Run the command in the acceptance answer. – irwinb Jun 24 '16 at 23:18

score 10 · Answer 7 · answered Feb 06 '18 at 10:14

10

Run Microsoft Azure Command Prompt as administrator and try to first initialize using AzureStorageEmulator.exe init and then start using AzureStorageEmulator.exe start commands. It worked for my case.

answered Feb 06 '18 at 10:14

Geek

101
1
4

1

Running as Administrator worked for me too. Which is odd, because on another PC, I do not need to use Administrator – Greg Woods Aug 10 '18 at 16:26

score 9 · Answer 8 · answered Sep 29 '17 at 09:58

I had same issue since I had to rejoin my machine to the domain and the user profile got recreated. I noticed that it was starting with option -inprocess from elevated cmd. Then I realized that it has to do with urlac and I solved deleting old ones with following commands:

(from elevated cmd)
netsh http delete urlacl url=http://127.0.0.1:10000/
netsh http delete urlacl url=http://127.0.0.1:10001/
netsh http delete urlacl url=http://127.0.0.1:10002/

After that simply start as usual, the tool will recreate what necessary. Now I can use it without elevation.

score 8 · Answer 9 · answered May 08 '17 at 21:18

8

It is also worth to try to run the command prompt with: "Run As Administrator" and then run the command: C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start

That did the trick for me!

answered May 08 '17 at 21:18

Don Bar

211
3
11

score 5 · Answer 10 · answered Sep 26 '14 at 22:05

5

Another option is to change the ip binding that the emulator uses in the config file located in the storage emulator directory.

Find wastorageemulator.exe.config and change

<services>
      <service name="Blob" url="http://127.0.0.1:10000/"/>
      <service name="Queue" url="http://127.0.0.1:10001/"/>
      <service name="Table" url="http://127.0.0.1:10002/"/>
   </services>

This would be usefull if another application is already using that port and you cannot uninstall.

answered Sep 26 '14 at 22:05

CrazyBernie

174
1
8

But that has a consequence that you can't than use the configuration setting `Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString` set simply to `UseDevelopmentStorage=true` in `ServiceConfiguration.Local.cscfg`, but you have to put there full connection string (which is huge and complicated). And that configuration file is part of a project, so everyone, who's developing it, has to reconfigure his Azure Emulator also. – David Ferenczy Rogožan Sep 18 '15 at 06:37

score 3 · Answer 11 · answered Jan 01 '19 at 16:41

if you are trying to start "Azure storage emulator" through Visual Studio=>Server explorer, make sure that you are starting visual studio as an administrator. I was able to get this issue fixed by running the "Azure storage emulator" on the command prompt, by running the command prompt as an administrator.

score 3 · Answer 12 · answered Jan 30 '21 at 20:42

3

open command prompt as administrator
run command: cd C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator
run command: AzureStorageEmulator start

answered Jan 30 '21 at 20:42

Mahmoud.Ismail

31
4

score 2 · Answer 13 · edited Feb 20 '18 at 17:51

2

There is some info here that might help:

AzureStorageEmulator.exe init –server MyMachine –sqlinstance **.** –forcecreate –inprocess

See this link.

edited Feb 20 '18 at 17:51

abatishchev

98,240
88
296
433

answered May 16 '14 at 04:22

Choco

1,189
1
14
29

score 2 · Answer 14 · answered Jun 05 '18 at 16:25

2

I just hit this, and it turns out that Microsoft Teams was using port 10000. Forcing teams to quit resolved the issue.

answered Jun 05 '18 at 16:25

Paul Batum

8,165
5
40
45

score 2 · Answer 15 · answered Dec 17 '18 at 00:05

For me there was nothing running on the needed ports, the issue was that Visual Studio was not started in Administrator mode so the process couldn't be started.

When I went to the Azure Storage Emulator CLI from "Start" that launches a command shell that is also not in Administrator mode which obviously produces the same result.

Opening a command shell in Admin mode did the job.

score 2 · Answer 16 · answered Feb 25 '19 at 14:31

2

Windows Backup Agent was running on my VM box on port 10000 - moving to 10003 (via the .exe.config file worked)

answered Feb 25 '19 at 14:31

Rory Solley

1,435
1
9
6

Eduard Silantiev · Answer 17 · 2019-10-13T20:42:07.740

First you should initialize the emulator database and configuration be starting AzureStorageEmulator.exe as administrator with a key init: AzureStorageEmulator.exe init

Then, if you still receive an error:

Service Status: Blob http://127.0.0.1:10000/ False The process cannot access the file because it is being used by another process Error: Unable to start the storage emulator.

try to change 127.0.0.1 to localhost for all services in C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe.config

score 2 · Answer 18 · answered Nov 06 '19 at 06:11

It worked for me:

Press the Windows key and search "Azure Storage Emulator"
It shows me an error message "..Cannot create the database "AzureStorageEmulatorDb510"
I opened the SSMS and looked for that database but I found "AzureStorageEmulatorDb59"
I renamed the database to "AzureStorageEmulatorDb510"
Try again run "Azure Storage Emulator"

score 2 · Answer 19 · answered Aug 02 '20 at 21:44

2

The reason for me was Hyper-V. It reserves a lot of ports. You can check reserved ports netsh int ip show excludedportrange protocol=tcp. Easiest solution - change ports in config file.

answered Aug 02 '20 at 21:44

Cute pumpkin

342
3
17

score 2 · Answer 20 · answered May 25 '21 at 16:05

I had the same problem, I tried many ways, nothing was blocking port 10000. I tried updating the emulator config to Localhost instead of 127.0.0.1 here

<services>
  <service name="Blob" url="http://127.0.0.1:10000/"/>
  <service name="Queue" url="http://127.0.0.1:10001/"/>
  <service name="Table" url="http://127.0.0.1:10002/"/>
</services>

but I had the timeout issue again.

Finally, I had to uninstall my IIS. and problem solved. there should be a way to make them work together.

score 1 · Answer 21 · answered Oct 07 '15 at 10:28

I have had this happen recently, and it was because I'd recently installed the HDInsight emulator. It appears this was auto-starting the storage emulator causing an error when VS attempted to start it resulting in an error.

Setting the "Start Microsoft Azure storage emulator" value to False worked in this case also.

score 1 · Answer 22 · answered Jul 04 '16 at 12:38

I encountered the same problem. I found out that, the port 10000 is being used by another process. In my case, utorrent was using it. It could be Bittorrent if that's what you are using. After uninstalling it, it started smoothly with altering my data.

If your torrent downloader means so much to you, you can consider solving your issue from that angle. I hope this works.

score 1 · Answer 23 · answered Dec 25 '16 at 21:22

For users of the newly released documentdb emulator...Microsoft thought it is a good idea that the documentdb emulator uses the same port as the Storage emulator ;) The only way you can access your storage is by shutting down documentdb emulator and restart Visual Studio and voila you can use it again :facepalm:

score 1 · Answer 24 · answered Sep 04 '18 at 10:59

1

I got similar issue with visual studio while trying to run Azure Functions. AzureStorageEmulator.exe init worked for me

answered Sep 04 '18 at 10:59

Preeti Joshi

841
1
13
20

score 1 · Answer 25 · answered Jun 02 '21 at 15:17

I experienced a power outage and after rebooting received the Unhandled Exception: System.TimeoutException message attempting to launch and debug an Azure Functions project from Visual Studio 2019. I tried many (if not all) of the other suggested answers on this thread to no avail. Including but not necessarily limited to ...

Checking for processes using ports 10000-10002, (none were)
Running Visual Studio and/or AzureStorageEmulator as administrator
Deleting / recreating the storage database
Attempted netsh http add iplisten 127.0.0.1 etc. from @Ram Pratap's answer
Changed hostname and port number bindings
Tried AzureStorageEmulator init and AzureStoreEmulator start -inprocess

What finally worked for me was ...

Installing the Storage Emulator using the standalone installer
This then allowed me to fully uninstall just the Storage Emulator using Add & Remove Programs, followed by a restart.
Next I reinstalled the Storage Emulator using the standalone installer, followed by a restart.
Finally I ran AzureStorageEmulator start it worked!

score 1 · Answer 26 · answered Jun 03 '22 at 06:05

Had the same issue, deleting the AzureStorageEmulatorDb510* files in my user folder(C:\Users{UserName}) and running C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe init /forceCreate solved it for me. I was then able to start with AzureStorageEmulator.exe start. Also ran the Cmd.exe in administrator mode.

score 1 · Answer 27 · answered Jun 15 '22 at 09:02

Had the same issue, node.exe is usually the one using port 127.0.0.1:1000 to 10003, which are used for StorageEmulator as well. so easy solution to try is, kill the node process from task manager, Also test by stopping the IIS (if on windows) and test if everything works fine.

score 1 · Answer 28 · answered Jan 04 '23 at 10:34

In my case AzureStorageEmulator.exe was throwing this error because i updated my VS 2022 and it installed azurite with it which was holding the port :10000.

I solved this by ending the task in Task Manager

As pointed out by Dale Francis in one of the comments of top answer

score 1 · Answer 29 · answered Jan 13 '23 at 04:58

1

IDK but none of the solutions work for me. Then accidently I noticed an icon in my taskbar hidden items. It was showing me that my computer emulator is shutdown. Once I start the emulator by following the shown steps it is working fine.

answered Jan 13 '23 at 04:58

yuv

499
1
7
14

Azure Storage Emulator error and does not start

29 Answers29

Linked