Verify that the instance name is correct and that SQL Server The server was not found or was not accessible. A network-related or instance-specific error occurred while establishing a connection to SQL Server. Probing SQL Instance: 'localhost\SQLExpress'.Ĭaught exception while probing for SQL endpoint. SqlError: : The target principal name is incorrect. Windows Azure Storage Emulator 5.7.0.0 command line toolĪutodetect requested. ANY help or thoughts would be appreciated!Ĭ:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start
#Run azure storage emulator as admin full#
Here are the full outputs of the emulator start/init calls.
Instance pipe name: np:\\.\pipe\LOCALDB#B161531A\tsql\queryĬ:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator> here are the current info details of the db:Ĭ:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>sqllocaldb iĬ:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>sqllocaldb i "MSSQLLocalDB" I have gone through the steps of deleting mssqllocaldb and the azurestorageemulator mdf and similar files, which went as expected, no issues. still, I tried init, with similar issues: The summed up error was that init should be run, though I think the issue was more one of accessing the local db in the first place. Probing SQL Instance: '(localdb)\MSSQLLocalDB'.Ĭaught exception while probing for SQL endpoint. So I go to do that (from first paragraph, running storage emulator as admin), and I basically get an error probing (localdb)/MSSQLLocalDB (full error log will be at bottom): I shut down for the night, but comingīack to it the next day, now I'm back to my original problem state.) Studio and all components, and after doing that and a restart, I opened the VS template project and ran debug, and it just worked, the emulator command window opened and ran and was showing all expected output, etc.
#Run azure storage emulator as admin update#
Then there was an interesting point where, I decided to update visual I went through everything I could find including deleting/restarting the localdb instance. (As an aside, when I originally started this yesterday, I was on 5.4.x.x of the emulator. I've done this with VSStudio running as admin and normal, same result. Please run azurestorageemulator.exe start as admin. I have VS 2017 enterprise, I created a template Azure function, and when I go to debug, it lets me know the typical (paraphrased) 'couldn't start Azure Storage Emulator, I am trying to create an Azure Function, and running into issues at the very start.