tag:help.appveyor.com,2012-11-13:/discussions/problems/452-error-executing-tests-that-use-the-azure-storage-emulatorAppVeyor: Discussion 2018-10-19T08:16:36Ztag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T15:40:38Z2014-06-19T15:40:38ZError executing tests that use the azure storage emulator<div><p>Hi James,</p>
<p>SDK 2.3 is already installed on build worker.</p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T15:45:21Z2014-06-19T15:45:21ZError executing tests that use the azure storage emulator<div><p>Is it here <code>C:\Program Files (x86)\Microsoft SDKs\Windows
Azure\Storage Emulator\WAStorageEmulator.exe</code></p>
<p>The logs indicate it is the 3.0.0.0 version.</p>
<p>If it's install elsewhere that could be the cause of the
<code>Error: Port conflict with existing application.</code></p>
<p>I'l commit a change that doesn't try to start the emulator and
see how it goes.</p></div>James Skimmingtag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T16:29:34Z2014-06-19T16:29:34ZError executing tests that use the azure storage emulator<div><p>I tried not starting the emulator, but the tests failed because
the emulator was not started.</p>
<p>I've just tried a custom install script <code>"C:\Program Files
(x86)\Microsoft SDKs\Windows Azure\Storage
Emulator\WAStorageEmulator.exe" start</code> but it still started
the 3.0.0.0 version not the 3.2.</p>
<p>If SDK 2.3 is installed where is it?</p>
<p>Ultimately adding the azure emulator as a service to starr like
SQLExpress and IIS would be useful.</p></div>James Skimmingtag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T16:31:45Z2014-06-19T16:31:45ZError executing tests that use the azure storage emulator<div><p>Let me take a look.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T17:39:02Z2014-06-19T17:39:02ZError executing tests that use the azure storage emulator<div><p>You were right, it's 3.0 emulator is currently installed. Most
probably only build tools 2.3 were installed. We will install 2.3
emulator - I'll let you know when it's available.</p>
<p>I was able to start 3.0 though from "before build" script:
<a href=
"https://ci.appveyor.com/project/appvyr/appveyor-bot-test/build/1.0.2#L66">
https://ci.appveyor.com/project/appvyr/appveyor-bot-test/build/1.0....</a></p>
<p>I think the reason you see "port conflict" might be racing
condition where emulator is not released after previous
fixture.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T17:45:40Z2014-06-19T17:45:40ZError executing tests that use the azure storage emulator<div><p>I think the port conflict was a false negative, I need the 2.3
emulator as I'm using the latest Storage NuGet package which
doesn't work with older emulators.</p></div>James Skimmingtag:help.appveyor.com,2012-11-13:Comment/334688332014-06-19T18:47:10Z2014-06-19T18:47:10ZError executing tests that use the azure storage emulator<div><p>OK, I see.</p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/334688332014-06-20T13:42:48Z2014-06-20T13:42:48ZError executing tests that use the azure storage emulator<div><p>I've managed to work out the correct product ID to use
WebPICMD:</p>
<pre>
<code>WebPICMD /Install /Products:VWDOrVs2013AzurePack.2.3 /AcceptEula</code>
</pre>
<p>Unfortunately it fails to install with the following
message:</p>
<pre>
<code>Install completed (Failure): 'Windows Azure Storage Emulator - 3.1'</code>
</pre>
<p>I also tried just installing the emulator directly (see below
for why I installed 3.1 not 3.2)</p>
<pre>
<code>WebPICMD /Install /Products:WindowsAzureStorageEmulator.3.1 /AcceptEula</code>
</pre>
<p>It also fails but I do get told there's a log file <code>Log
Location: %temp%\WindowsAzureStorageEmulator.txt</code>
unfortunately I can't access that log, I tried adding it as an
artefact, but because the build fails no artefacts are
collected.</p>
<h1><a href="#why-i-installed-3-1-not-3-2" class="anchor" name=
"why-i-installed-3-1-not-3-2" id=
"why-i-installed-3-1-not-3-2"></a>Why I installed 3.1 not 3.2</h1>
<p>For some reason WebPICMD is installing the 3.1 emulator not 3.2
(I tried <code>WebPICMD /Install
/Products:WindowsAzureStorageEmulator.3.2 /AcceptEula</code> but it
says it doesn't exit).</p>
<p>I wonder (granted this is speculation), is it refusing to
install the 3.2 Emulator because VS2013 Update 2 is not installed?
What version of VS2013 is installed?</p></div>James Skimmingtag:help.appveyor.com,2012-11-13:Comment/334688332014-06-23T03:37:18Z2014-06-23T03:37:18ZError executing tests that use the azure storage emulator<div><p>James,</p>
<p>We've deployed the latest Azure storage emulator. It shows 3.2
now. Please give it another try and let me know how it goes.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/334688332014-06-23T07:53:38Z2014-06-23T07:53:38ZError executing tests that use the azure storage emulator<div><p>Feodor</p>
<p>It works great thank you, my tests are now passing, the before
build command has the following output:</p>
<pre>
<code>"C:\Program Files (x86)\Microsoft SDKs\Windows Azure\Storage Emulator\WAStorageEmulator.exe" start
Windows Azure Storage Emulator 3.2.0.0 command line tool
The storage emulator was successfully started.</code>
</pre>
<p>Thanks again.</p></div>James Skimming