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.
Related
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
I have tried following the solution to this question.
All instruments work perfectly but leak instruments cause this error:
An error occurred trying to capture Leaks data, Error retrieving leak information.
I want to be able to use Leak Instrument without any errors.
Image is also shown below.
Please help me. Thanks in advance.
This happened to me after updating the provisioning profile. It started working after restarting Instruments.
Switch to Console view to know the specific reason
For me the issue was caused by deleted Pod. Cleaning the project fixed that.
Try Checking your provisioning profile for Profile Tool on scheme of the app.
Go to Scheme editing window (just press command shift and , (comma)).
Set Build Configuration to Debug.
check that if you switch the Address Sanitizer.I close Address Sanitizer and then it works.
Edit Scheme -> Diagnostics
i upgrade the Xcode from 8.3.2 to 8.3.3 , it not works. Then I tried running it on true device , it works well.
rm -rf ~/Library/Developer/Xcode/DerivedData
or
rm ~/Library/Developer/Xcode/DerivedData/YouProject
close xcode restart your system then check it
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.
I see clear requirements that for building presto you need Mac OS/Linux.
https://github.com/prestodb/presto
I also see there are issues which are being discussed on getting windows support for Presto's build
https://github.com/prestodb/presto/issues/2351
What I don't see is a proper documentation of how to get started or a way around to get started with windows.
I found this link http://wheresthedocs.blogspot.com/
but I am not sure is it going to help me in getting started with presto.
If anyone has done it please provide with some basic instructions that would be very helpful!
Presto does not currently support building or running on Windows. There is a community member slowly working on getting this to work, but it is not something Facebook is working on.
In the mean time, I suggest you use Vagrant or VirtualBox to run virtualized Linux on your Windows machine.
Someone at Microsoft got this working on Azure last year with a few tweaks. http://blogs.msdn.com/b/mostlytrue/archive/2014/08/12/more-blue-coffee-presto-on-azure.aspx
I have Azure SDK 2.3 installed on my Windows 7 machine. The target .Net framework is set to 4.0. I'm able to upgrade my solution to Azure SDK 2.3 and build with no problems. However, when I try to run the solution, I get the following error:
Failed to debug the Windows Azure Cloud Service project. The output directory does not exist.
If I revert the solution back to Azure SDK 2.2, the problem goes away. So there's some configuration that's added by the Azure SDK 2.3 upgrade that is causing this issue. This ONLY happens when I'm running the Azure Emulator. One thing I've noticed is that the build process somehow removes the "Debug" folder from the csx directory. When I manually add it back in, the build process removes it again and then I get the same error above. I'm at a loss as to what might be causing this since my "Active solution configuration" is all set to DEBUG for "Configuration" and ANY CPU for "Platform". I've tried all the troubleshooting steps from earlier threads on this issue (with Azure SDK 1.8) with no luck. I would appreciate any helpful suggestions on this. Thanks.
NOTE: Interestingly enough, if I deny all rights to the DEBUG folder in CSX, the emulator launches but then it fails because it doesn't have access to the DEBUG folder. So I'm puzzled by why the VS build process wants to remove that Debug folder.
ANOTHER NOTE: Apparently, it's the normal process for VS Build to wipe out the Debug folder. The run process with debug is supposed to recreate that Debug folder with everything in it. That doesn't happen. I confirmed this by reverting it back to Azure SDK 2.2 and noted that the run w/ debug actually recreates that Debug folder. This recreation process fails to happen when I upgrade to 2.3.
For me, the issue was I changed the Debug Solution Configuration to something other than Debug. Renaming it back to Debug fixed the issue.
I was able to solve this issue by simply uninstalling Azure SDK 2.3 and then re-installing it. That's it!
Got it solved by doing the following:
Change to "Release" configuration.
Build and run.
Change back to "Debug" configuration.
Build and run. No error now.
I was seeing the same error that the csx folder was empty. Doing the following fixed my issue:
Right click your *.ccproj > Debug > Start New Instance
None of the above worked for me, what did work was deleting the file
{YourProject}.ccproj.user
Close and reopen VS, build and run