I tried to launch Cosmos DB Emulator, but I get these 3 errors:
DocumentDb Master has stopped working
DocumentDb.GatewayService.exe has stopped working
DocumentDb Server has stopped working
You can download emulator from Microsoft Download Center.Extract setup and run emulator exe.
Once you completed the setup, type Azure Cosmos DB Emulator in Start menu. Run it as administrator
If you are stuck at any point read Here
I think it was the problem about GatewayServiceStartup process.
To solve this, we can try to run the elevated command:
C:\windows\SysWOW64> lodctr /r
This problem is most often caused by incompatibility with local SQL server.
The familiar issue as yours: documentdb emulator gatewayservice crashing on startup
In addition, we can refer to the troubleshooting Chapter from this article for more information.
Hope it is helpful to you.
I had similar problem and gave up. Accidentally I found the solution after (AzureStorageEmulator 5.1 doesn't to start):
seems, I found the reason - the net access for local machine was closed somehow:( I have ran the command
netsh http add iplisten 127.0.0.1
Related
I am unable to get cosmos emulator started. I keep getting a “This site can’t be reached. Localhost refused to connect” message when it tries to navigate to https://localhost:8081/_explorer/index.html. Several seconds later, I get the below error message:
I'm using the latest version (2.4.5.0). I uninstalled Cosmos Emulator, deleted the %LOCALAPPDATA%\CosmosDBEmulator folder, and reinstalled. Still same issue.
Then, I tried running LODCTR /R in the command prompt twice, but that didn’t do anything for me. I’m out of ideas. This was working for me several months ago, so something happened recently that caused it to stop working. What could be causing this issue? Anything else I can try?
You can follow the steps mentioned here to troubleshoot your issue
If you installed a new version of the emulator and are experiencing errors, ensure you reset your data. You can reset your data by right-clicking the Azure Cosmos Emulator icon on the system tray, and then clicking Reset Data…. If that does not fix the errors, you can uninstall the emulator and any older versions of the emulator if found, remove "C:\Program files\Azure Cosmos DB Emulator" directory and reinstall the emulator
Just installed CosmosDB emulator 1.19 and ran into issues upon startup. GatewayServiceStartup stops working upon launch. Does anyone have any idea?
You could debug the GatewayServiceStartup process and check the log.
If you experience crashes in CosmosDB.StartupEntryPoint.exe, run the
following command from an admin command prompt: lodctr /R
You could find the above statement in the Troubleshooting Chapter from this document.
In addition , please refer to the thread:
documentdb emulator gatewayservice crashing on startup.
Hope it helps you.
I'm running Windows 10 - 1703 build 15063.296 - using Edge with Azure Cosmos DB Emulator, the UI tabs on the quick start page don't work? is anyone having the same issue? BTW, the Azure portal works fine.
using Edge with Azure Cosmos DB Emulator, the UI tabs on the quick start page don't work?
If you mean that you could not choose other platforms except .NET in Quickstart page, you could try to uninstall and reinstall the Azure Cosmos DB Emulator, the issue seems fixed now.
I think the issue is that data explorer files got corrupted/non-functional.
After making sure you have the latest version of the emulator installed, follow these steps:
Exit the emulator
Delete all files under C:\Program Files\Azure Cosmos DB Emulator\Packages\DataExplorer\ (not the folder itself - just the files)
Open emulator
I hope this works for you! :)
Since I restarted my computer yesterday I cant start any of my azure cloud projects due to this error :-
System.ServiceModel.AddressAlreadyInUseException: Cannot listen on
pipe name 'net.pipe://localhost/dfService/' because another pipe
endpoint is already listening on that name. --->
System.IO.PipeException: Cannot listen on pipe name
'net.pipe://localhost/dfService/' because another pipe endpoint is
already listening on that name.
I've checked the project ports and there all no standard ports that shouldn't and haven't conflicted with anything.
In a last ditch attempt I formatted my machine as I didnt have much on anyway and even with a clean install of VS2013, Azure SDK 2.6 and Windows 8.1 Im still getting the same error.
Has anybody has similiar problems or could suggest a direction for me to go in?
Thanks in advance.
It helped me to shutdown both Computing and Storage Emulator, close Azure Simulation Monitor (csmonitor.exe systray application) and manually start the Azure Emulator as an administrator. Also if it started the Emulator Express and you need Full Emulator (I expect so, since this error didn't appear with the Express for me), just stop it and start the Full Emulator using systray icon.
Just don't let Visual Studio to start it automatically. I don't know what was the real reason of that error, but this solved it for me.
Upgraded my windows azure project to 2.1 and i cannot get the local emulator to work any longer.
I get this error when I run on express mode
"the compute emulator is not running in express emulation mode. Please restart the emulator in correct mode."
I tried restarting but it just would not work.
I also tried using the full mode but get this one
-'cannot listen on pipe name 'net.pipe //localhost/dfService/ because another pipe endpoint is already listening on that name'
- I get a dfagent and windows azure development fabric logging agent not working on this setup as well.
Please help.
Thank you