Open aarondandy opened 6 years ago
LoulG
commented
6 years ago Same here.
Windows 10 1709 (16299.309) CosmosDb 1.20.108.4
As a side note, I have another machine (Surface Book) in the same configuration (Windows, CosmosDb and Hyper-V) on which the emulator is working as desired.
aarondandy
commented
6 years ago @LoulG Oh man, of all the things I put in my issue I forgot to list my windows version which is the same as yours, I'll add that. Can you please also post the version of windows you have on your working machine so we can see if that may be related? Can other people with this issue also list their windows versions? You can do so by running winver .
LoulG
commented
6 years ago All my two machines have exactly the same configuration/versions. The only difference between the two, is that the working machine is not domain joined.
aarondandy
commented
6 years ago My broken machine is not domain joined so I guess neither aspect is related.
aarondandy
commented
6 years ago I am able to run the emulator from https://hub.docker.com/r/microsoft/azure-cosmosdb-emulator/ but the web UI seems to not work. I get a ton of JS errors and the web UI is unable to show me databases or collections. At least the C# client seems to work. It would be a much nicer experience if the msi would work on my machine too.
LoulG
commented
6 years ago @aarondandy Did you have it work ? I didn't find a solution yet... Do you have any corporate local firewall or proxy that could block some connections ?
aarondandy
commented
6 years ago Nope, I'm still unable to get the installed emulator working. It used to work, but after a few OS updates or installation no longer works.
David-Noble-at-work
commented
6 years ago @aarondandy Hi there, It looks like you may have hit a known issue: an incompatibility that we've got with certain network filters. This is indicated by the error messages you site:
FAILED HRESULT -2147014851, Function RntbdChannelPump::HandleAcceptDone, File RntbdChannelPump.cpp, Line 116, DocumentServiceId
FAILED HRESULT -2147014851, Function TcpListener::EndAccept, File TcpListener.cpp, Line 118, DocumentServiceId
FAILED HRESULT -2147014851, Function TcpListener::TcpAcceptContext::End, File f:\_bld\16221\3506\sources\product\backend\native\transport\tcp\TcpListener.TcpAcceptContext.h, Line 55, DocumentServiceId
FAILED HRESULT -2147014851, Function TcpListener::TcpAcceptContext::OnComplete, File TcpListener.TcpAcceptContext.cpp, Line 95, DocumentServiceIdThe error (HRESULT -2147014851 ⇒ 0x8007273D ⇒ WSAEOPNOTSUPP) is related to our use of the Registered I/O Networking extensions (RIO). These error messages originate in our AcceptLoop.
It's on our roadmap to remove our dependency on RIO. For now the only solution may be for the custom to remove the offending network filter, if that is indeed the case you've come across.
Please tell me:
Best, David Noble
aarondandy
commented
6 years ago My current list:
LoulG
commented
6 years ago On a Surface Book 2, Windows 10 1709 (16299.309), CosmosDb emulator works fine. Here are the network filters:
On monday, I will post the list from the machine on which the emulator is not working
LoulG
commented
6 years ago Here is the list of the network filters for the machine on which the emulator does not work (same windows version as the one on which it works: Windows 10 1709 (16299.309)
As this list is the same onto the 2 machines, maybe it's worth listing the characteritics of each network filter? @David-Noble-at-work
David-Noble-at-work
commented
6 years ago I'm not seeing any suspicious entries in the list of filters you've provided. Do you have any third-party VPN software installed (e.g., PulseSecure)?
Are you up for a Skype call? If so, please send e-mail to askcosmosdb@microsoft.com and I will pick it up.
Thanks.
aarondandy
commented
6 years ago I do have multiple VPNs, we can go over them if you would like in a call.
LoulG
commented
6 years ago Any feedback ? @David-Noble-at-work do you need another skype call to cross verify ?
aarondandy
commented
6 years ago @LoulG nothing looked related when investigating my machine. They got some telemetry out of it though.
garfbradaz
commented
6 years ago This is happening to me since upgrading to Windows 1803.
aarondandy
commented
6 years ago I just got a new xps 5970 and paved it with a fresh 1803 install, same issue. Things I have installed that may be relevant:
evandixon
commented
6 years ago I too have trouble running it on my 2-3 year old home computer (has a VPN, and probably a bunch of other stuff installed over the years). Interestingly, it runs fine on my 3-month-old work computer (does not have a VPN AFAIK).
aarondandy
commented
6 years ago Hey @David-Noble-at-work, are there any new releases of the emulator on the horizon that I could try?
arkiaconsulting
commented
6 years ago @aarondandy If it can help, I had it working by uninstalling a software named "Pulse Client". You may find it running in the task manager, and it should be listed in the programs and features screen.
aarondandy
commented
6 years ago @arkiaconsulting Thanks for the tip. I don't have that VPN software specifically but it does seem as though the issue could be related to networking. I suspect I will need to use a new version of the emulator with fixes applied for this issue.
hamdyghanem
commented
6 years ago I recommend you to use the sample provided in the quick start quickstart/DocumentDB-Quickstart-DotNet.zip
Also you can play in the ConnectionPolicy settings sample:
var cp= new ConnectionPolicy
{
ConnectionMode = ConnectionMode.Gateway,
EnableEndpointDiscovery = false,
ConnectionProtocol = Protocol.Https
};
juunas11
commented
6 years ago Actually I fixed my problems by using Gateway mode + HTTPS with the emulator:
client = new DocumentClient(endpointUri, _config.AuthKey, new ConnectionPolicy
{
ConnectionMode = ConnectionMode.Gateway,
ConnectionProtocol = Protocol.Https
});I have not tried connecting to the emulated service with those options from code yet but I would like to point out that the CosmosDB emulator tools themselves don't work as they can't connect which can be very inconvenient when doing Debugger Driving Development :trollface:
aarondandy
commented
6 years ago Is the commonality between people that have this working and people that don't Hyper-V or maybe even any hypervisor at all?
ghost
commented
6 years ago Hello to everyone, I am facing exactly the same problem with Azure Cosmos DB Emulator version 2.1.2. The result, is that when I was trying to go to the Explorer tab, I was getting some "Service is currently unavailable" errors.
I tried almost everything to let it works (Disabled: Firewalls, Defenders, some Network Filters, ipv6, and so on, Reset data...), but nothing worked.
I discovered that there are some kind of problems with the DocumentDB's Master and Server Packages.
Following are some methods called when a client trying to connect to TCP ports: 10251 (Master) or 10253 (Server):
...
WSAIoctl(SIO_KEEPALIVE_VALS) -> Return STATUS_SUCCESS
WSAIoctl(SIO_TCP_SET_ACK_FREQUENCY) -> Return SOCKET_ERROR on Windows 8.0 OS
...
mswsock.dll::RIOCreateRequestQueue(...) -> Return RIO_INVALID_RQ on my Windows 8.1 OS
...The fatal error on my Windows 8.0 OS, that comes from second call to WSAIoCtl (HRESULT -2147014851 ⇒ WSAEOPNOTSUPP ⇒ SOCKET_ERROR ⇒ STATUS_NOT_SUPPORTED) is related to ioctl SIO_TCP_SET_ACK_FREQUENCY, that was introduced on Microsoft Windows starting only from 8.1 version, and so, it seems to be correct that this error happen on prior OSes. I want to say that this is the only Windows API that let Document DB doesn't be compatible with Windows 8.
The fatal error on my Windows 8.1 OS, that comes from call to mswsock.dll::RIOCreateRequestQueue (HRESULT -2147014851 ⇒ WSAEOPNOTSUPP ⇒ RIO_INVALID_RQ ⇒ STATUS_INVALID_DEVICE_REQUEST) is related to the fact that I had some not compatible VPN software with Registered I/O Networking extensions (RIO) installed on my machine. In particular, to let DocumentDB works, I simply renamed the file C:\Windows\system32\Drivers\NEOFLTR_XXX_XXXXX.SYS (Juniper Networks TDI Filter Driver), that is part of PulseSecure software (that someone other in this thread has referenced as the problem). P.s.: that driver was not listed in Windows Network Filters, so do not rely only on Windows Network Filters list.
So, the steps that I suggest to solve those kind of problems are (in order): 1) Check if there are installed software that are blocking TCP ports: 10251, 10253, 10255 (MongoDB) 2) Check if you have VPN software installed, and try to temporarily disable it 3) Try to "Reset data"
I hope it helps Microsoft Azure Cosmos DB Developers to solve or manage above problems automatically.
@David-Noble-at-work, @aarondandy, @LoulG, @garfbradaz @evandixon
mdsharpe
commented
4 years ago I am experiencing “Service is currently unavailable” errors with the Azure Cosmos DB Emulator (version 2.9.2.0). This only happened since I moved my workstation from my office to my home and started using VPN to connect to my work network.
I was able to resolve temporarily by uninstalling and deleting all local data related to the emulator, but it has started happening again the following day.
Camios
commented
4 years ago Service unavailable can be from having too many containers in the emulator.
codematrix
commented
4 years ago I just did a Data Reset it started working again.
DaleyKD
commented
4 years ago This emulator is frustrating the beeeeejeeebus out of me. I can't get it to work longer than a few days before having to reset it or fix the SSL or whatever.
alveflo
commented
4 years ago Any news on this one? I'm facing the same issues...
GrumpyRainbow
commented
3 years ago Ran into this same issue, but followed @codematrix's comment, recreated local data seeds and all was well. I wonder if we just had too many records in the db and it eventually stopped working. I'll be paying attention to that moving forward to see if that's the case.
ben-graffle
commented
2 years ago Any update on this? This happens every time I use the cosmos emulator docker container
christiansparre
commented
2 years ago An update would be nice. I'm running into this daily where certain databases or containers just stops working. Other databases work just fine. Deleting the database/container does not fix the problem. After creating database/container with the same names it keeps failing.
vmachacek
commented
1 year ago yeah, this is very annoying, why is it so hard to fix?
Description
After installing Azure Cosmos DB Emulator 1.20.108.4 I am unable to use it after it starts.
Steps to reproduce
Expected & Actual
I expect that the Azure Cosmos DB Emulator Explorer will be able to interact with the Azure Cosmos DB Emulator. I am unable to interact with or use the Cosmo DB Emulator outside of accessing https://localhost:8081/_explorer/index.html .
Other Notes & Things Tried
Windows Version: 1709 or 10.0.16299.309
I sent you my traces.
I have re-installed Hyper-V
I have re-installed the Azure Cosmos DB Emulator multiple times. And then some more.
I have removed all of the VPNs from my system.
I have tried turning my firewall off.
My Hyper-V Default Switch is using the IP
172.29.155.113I did not hibernate.
I have performed a "Reset data..." multiple times on different installation attempts.
I have removed and allowed Azure Cosmos DB Emulator to recreate the firewall rules.
I have also removed
AppData\Local\CosmosDBEmulator.The following is the HTTP response I get:
The following errors look interesting as well: