Azure local memory emulator problem 400 bad request

I could not find this on the site. This may be trivial, but the error message is pretty misleading.

When you try something with azure sdk and local emulators (memory and computation emulators) during debugging, you may get the following error when initializing these emulators:

The process cannot access the file because it is being used by another process.

In addition, if you want to check something from the code and want to access the blob memory emulator, you can get 400 Bad request as a result.

+2
source share
1 answer

You can customize this. Open the file "DSServiceLDB.exe.config" under "C: \ Program Files \ Microsoft SDKs \ Windows Azure \ Emulator \ devstore".

Inside the file, change the values ​​in this 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> 
0
source

All Articles