Ok, I googled first and most of the solutions involved resetting the db backing azure table storage which I didn’t want to do right away… though that would have solved my issue, as you will figure out later. That lead me to think about looking into logs. In the exception I was receiving in Visual Studio, I was seeing a request ID in the form of a guid. Spoiler alert: the problem was that the SQL data file (.mdf) backing the emulator was full… yeah, I know, I’m that lucky ) Enabling Logs I’ve had these kinds of issues in the past with a mismatch between the azure storage dlls and the emulator version but in this case, nothing had changed from “it worked fine last time I did this” to “why is this broken now?” Recently, I encountered an issue where doing GET requests against Table Storage in the Azure storage emulator was working but POST and PUT requests were failing with a generic 500 coming back from the emulator. Azure In this blog post, we will explain how to get more insight into weird azure storage emulator problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |