Windows Azure Storage Emulator cannot be started

By Daniel Du

When running the Blob example of Windows Azure today, we found that the Blob storage simulator cannot be started. The pop-up error message is as follows:

"Process cannot access the file because it is being used by another process"

From the above, we can see that the Blob simulator uses the port number 10000. According to the error message, most of them are caused by port conflict. But which program occupies port 10000? You can use the port scanning tool for search, but windows also comes with the command NETSTAT with similar features, so you do not need to download the scanning tool. Run the following command:

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

From the output, we can see that process 6256 is listening to port 10000. What is the process of process 6256? How can we find this process and kill it? The following command is useful again:

C: \ Users \ duda> tasklist/fi "pid eq 6256"

Image Name PID Session Name Session # Mem Usage
========================================================== ======================================
Emagent.exe 6256 Services 0 40,956 K

 

It can be seen that the process name is "emagent.exe", which is a process of an Oracle management tool. I don't need oracle now, so I can kill it in the task manager. After killing, my Azure storage simulator can be started again.