Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This might be another process using the port that Azure dev storage is using.</p> <p>To figure out which app is that, run <code>netstat</code> first:</p> <pre><code>netstat -p tcp -ano | findstr :10000 </code></pre> <p>You will get a process id (PID) in the last column:</p> <pre><code> TCP 0.0.0.0:10000 0.0.0.0:0 LISTENING 2204 </code></pre> <p>It means that process listening to this port is ID 2204. Then run <code>taklist</code>:</p> <pre><code>tasklist /fi "pid eq 2204" </code></pre> <p>So you will see something like this:</p> <pre><code>Image Name PID Session Name Session# Mem Usage ========================= ======== ================ =========== ============ SMSvcHost.exe 2204 Services 0 29 300 K </code></pre> <p>So now you know that <code>SMSvcHost.exe</code> is listening on that port.</p> <p>If you can't stop the process using the port, there's a way to remap the ports used by DevFabric. The solution is taken from <a href="http://mohamadhalabi.com/2011/06/03/azure-storage-emulator-process-cannot-access-the-file-because-it-is-being-used-by-another-process/" rel="nofollow noreferrer">this blog post</a>:</p> <blockquote> <p>You could do that by navigating to C:\Program Files\Windows Azure SDK\v1.4\bin\devstore (replace 1.4 with your SDK version) and opening <strong>DSService.exe.config</strong>. From there you could change the configuration and make your services listen to other ports.</p> </blockquote> <p>For me in <strong>v1.6</strong> the path was <code>C:\Program Files\Windows Azure Emulator\emulator\devstore\DSService.exe.config</code></p> <p>For <strong>SDK v2.5 / Storage v3.4</strong> the path is <code>%ProgramFiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\WAStorageEmulator.exe.config</code></p> <p>For <strong>Emulator v4+</strong> the path is <code>%ProgramFiles(x86)%\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe.config</code></p> <p>But be careful, because you will not be able to use <code>UseDevelopmentStorage=true</code> in your connection string anymore (e.g. connect with Azure Storage Explorer). </p> <ul> <li><code>DsInit</code> doesn't help</li> <li>Specifying the connection string this way <a href="https://stackoverflow.com/a/7037036/182371">https://stackoverflow.com/a/7037036/182371</a> doesn't help either.</li> </ul> <p>In order to connect, use a custom connection string that is targeting the new endpoint ports you defined. You'll still want to connect using the <a href="http://msdn.microsoft.com/en-us/library/azure/hh403989.aspx" rel="nofollow noreferrer">standard, well-known storage emulator account name and key</a>. An example connection string can be <a href="https://stackoverflow.com/questions/24365307/azure-emulator-port-conflict-app-tries-to-connect-to-wrong-port/24365699#24365699">found here</a>.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload