documentdb emulator gatewayservice crashing on startup

▲
5
▼

I was looking to learn about documentdb and installed the emulator seemingly without error. However, upon startup I have a service crashing:

GatewayServiceStartup

Judging from the title I am guessing it is an important service to the emulator. Interestingly enough it seems like the emulator continues to load and attempts to open : https://localhost:8081/_explorer/index.html

without success.

using the command prompt I attempted to start the gateway services manually and here is the results:

C:\Program Files\DocumentDB Emulator\Packages\GatewayService\GatewayService.Code>documentdb.gatewayservice.exe /?

Unhandled Exception: System.Runtime.InteropServices.COMException: Invalid value for registry (Exception from HRESULT: 0x80040153 (REGDB_E_INVALIDVALUE)) at System.Runtime.InteropServices.RuntimeEnvironment.GetDeveloperPath() at System.AppDomain.SetupFusionStore(AppDomainSetup info, AppDomainSetup oldInfo) at System.AppDomain.SetupDomain(Boolean allowRedirects, String path, String configFile, String[] propertyNames, String[] propertyValues)

C:\Program Files\DocumentDB Emulator\Packages\GatewayService\GatewayService.Code>documentdb.startupentrypoint.exe /?

Unhandled Exception: System.Runtime.InteropServices.COMException: Invalid value for registry (Exception from HRESULT: 0x80040153 (REGDB_E_INVALIDVALUE)) at System.Runtime.InteropServices.RuntimeEnvironment.GetDeveloperPath() at System.AppDomain.SetupFusionStore(AppDomainSetup info, AppDomainSetup oldInfo) at System.AppDomain.SetupDomain(Boolean allowRedirects, String path, String configFile, String[] propertyNames, String[] propertyValues)

C:\Program Files\DocumentDB Emulator\Packages\GatewayService\GatewayService.Code>

Is the gateway service relevant? Any idea how to fix?

Quick Edit: I have followed the directions listed here: https://docs.microsoft.com/en-us/azure/documentdb/documentdb-nosql-local-emulator#troubleshooting

No etl file is generated to be emailed.

Thanks in advance

azure-cosmosdb
asked on Stack Overflow Feb 2, 2017 by Chris • edited Feb 2, 2017 by Chris

5 Answers

▲
4
▼

I fixed this issue simply with LODCTR /R to fix performance counters.

C:\WINDOWS\system32>LODCTR /R

Error: Unable to rebuild performance counter setting from system backup store, error code is 2
C:\WINDOWS\system32>LODCTR /R

Info: Successfully rebuilt performance counter setting from system backup store
C:\WINDOWS\system32>

I just needed to run it twice to succeed.

answered on Stack Overflow Feb 5, 2018 by Jani Hyytiäinen
▲
2
▼

I got the following exception when debugging the GatewayServiceStartup process:

Cannot load Counter Name data because an invalid index '' was read from the registry.

Fixed it using Cannot load Counter Name data because an invalid index -Exception:

In an elevated command prompt:

C:\windows\SysWOW64> lodctr /r
answered on Stack Overflow Jun 7, 2017 by tjeerdhans
▲
0
▼

Chris- The recommendation is to send dump and/or trace files to askdocdb@microsoft.com. Specific instructions for retrieving the files are provided here: https://docs.microsoft.com/en-us/azure/documentdb/documentdb-nosql-local-emulator#troubleshooting. -Mimi

answered on Stack Overflow Feb 2, 2017 by Mimi Gentz
▲
0
▼

Working with askdocdb@microsoft.com, we were able to resolve the issue.

Reviewing the crash dump files turns out that a perf counter was causing an issue. I disabled the perf counter and then everything worked as intended.

The perf counter in question was 2005 sqlexpress.

Special thanks to Momin for taking the time to work with me through the issue.

answered on Stack Overflow Feb 2, 2017 by Chris
▲
0
▼

I had the same problem. I unistalled Sql Server 2008 R2.Not compatible win win 10 anyway.

answered on Stack Overflow Apr 3, 2018 by Paul Stanley

User contributions licensed under CC BY-SA 3.0