-
Notifications
You must be signed in to change notification settings - Fork 840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CosmosDB Emulator wont start #470
Comments
Please be sure that you've downloaded and installed the latest version of the Emulator from here. If you send an e-mail to askcosmosdb@microsoft.com I'll work with you directly. Thanks. |
@David-Noble-at-work Thanks David, I have uninstalled and installed that download link version 1.21.0.0 and I am still having the same issue. I have sent off an email with the details of my issue from the following issue case. |
When I tried to upgrade the emulator to the latest version, I ran into a similar issue where nothing worked following the uninstall/reinstall. What finally fixed the issue for me was:
|
Not sure where to post this issue. I have another ticket opened at MicrosoftDocs/azure-docs#6788
I cant seem to start the Cosmos DB Emulator. I have windows 10 and it appears to install fine, but when I click to start it up I see the tray icon appear and then it disappears before I can click on it. The localhost landing page "https://localhost:8081/_explorer/index.html" does not appear and I cannot navigate to it either
I have tried to restart my machine. Uninstall the application. Turn off the IIS web server I use for debugging but nothing appears to work.
I have ran the command "lodctr /R" and got a successful message back from running it, it still wont start.
I tried to look for the crash dumps at c:\Users\user_name\AppData\Local\CrashDump but I see no crashDump files
I have tried to launch the Emulator as an administrator but it still wont start.
I tried to Collect trace files with the following steps
but I dont get any trace files either. Im not sure what is wrong at this point in time
The text was updated successfully, but these errors were encountered: