c# - Creating Table in Azure Storage Emulator produces HTTP 500 Error -
i've been attempting create table through machine's azure storage emulator. can recreate problem simple program uses windowsazure.storage nuget version 6.2.0 :
using microsoft.windowsazure.storage; namespace storageemulatortest { internal class program { private static void main(string[] args) { var cloudstorageaccount = cloudstorageaccount.parse("usedevelopmentstorage=true"); var cloudtableclient = cloudstorageaccount.createcloudtableclient(); cloudtableclient.gettablereference("johnnytest").createifnotexists(); } } }
after 25 seconds, throw exception of type microsoft.windowsazure.storage.storageexception, message: the remote server returned error: (500) internal server error.
i have attempted:
- ensuring windowsazure.storage nuget package latest version (6.2.0).
- re-installing azure sdk vs2015 2.8.1 (and ensuring it's latest version)
- stopping, clearing, initing azure storage emulator through azure storage emulator command line tool (seemed work fine, no errors)
- reading web response's stream through exception's ".innerexception.response.getresponsestream()". fails exception states "stream not readable".
- restarting machine (desperation kicked in)
my bag of tricks running low. has encountered issue?
i solved it. had wipe out existing local storage emulation instance. using "azurestorageemulator.exe clear" or "azurestorageemulator.exe init" insufficient. uninstalling azure sdk insufficient.
i started stopping storage emulation:
azurestorageemulator.exe stop azurestorageemulator.exe clear azurestorageemulator.exe init /forcecreate
that last command errored , indicated not create database.
then deleted (actually, renamed them) these remaining files comprised database behind azure storage emulator:
- c:\users\[me]\azurestorageemulatordb42_log.ldf
- c:\users\[me]\azurestorageemulatordb42_log.mdf
finally, started emulator up
azurestorageemulator.exe init /forcecreate azurestorageemulator.exe start
success!
i'm unsure got me situation, best guess caused recent upgrade of azure sdk.
Comments
Post a Comment