title: Azure storage emulator unable to initialize
body: <p>I've upgraded Azure Storage Emulator from 2.3 to 2.4. <em>WAStorageEmulator.exe</em> has been renamed to <em>AzureStorageEmulator.exe</em> but that's not the issue.</p>
  
  <p>When I run</p>
  
  <pre><code>AzureStorageEmulator init -forcecreate
  </code></pre>
  
  <p>I simply get an error that Google returns with <strong>zero</strong> results:</p>
  
  <blockquote>
    <p>Error: User-specified instance not found. Please correct this and re-run initial
    ization.</p>
  </blockquote>
  
  <h2>Edit</h2>
  
  <p>I had to do a start and stop and then I was able to init. Because I had previous version of emulator installed I already have <em>WAStorageEmulatorDb34</em> on my local SQL server instance. After I run <em>init</em> command I can see that <strong>no new database is being created</strong> (like <em>WAStorageEmulatorDb42</em>).</p>
  
  <p>So I thought that the newest version may be using older DB. I then ran a query in MSSMS to check for existing blob containers and I can still see both containers I created on the older emulator containing blobs I added.</p>
  
  <p>When I then accessed Development Azure Storage in Visual Studio it showed no containers whatsoever. So the new version apparently doesn't use old DB. <strong>But which one?</strong> And <strong>where is it</strong>?</p>
  
  <p>Ok so I thought I'd run init one more time but with additional parameters to put DB on my SQL server instance:</p>
  
  <pre><code>AzureStorageEmulator init -server localhost -sqlinstance MSSQLSERVER -forcecreate
  </code></pre>
  
  <p>And then I get the aforementioned error. Again...</p>
  
  <p>I'm running CMD as admin with elevated permissions.</p>