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
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 am using the Azure Mobile App quickstart ToDoList example to get started with cross platform app. I have set up the back-end and it is working on localhost - I can hit it using Swagger and gets posts etc are working.
I then set up the client application (Xamarin.Forms). I am running the client application on my Android device and all works great when back-end is in Azure, including the offline sync element. The problem is that I have to work locally for now but I cannot sync with the db when running on localhost.
At first the debugger was giving me a "connection refused" error, so I followed the steps here and in various other sources including using my laptop IP and setting firewall rule, adding binding to port in IIS Manager and applicationhost.config, and changing ApplicationURL in Constants.cs.
Now, I get no connection refused error, but the data is not getting to the db, athough the localdb on the tablet seems to be working - it is failing when I try to sync to/from db.
Not too familiar with networking but it may be important to note that when I use localhost:portnum/tables/todoitem in browser I get results in XML but when I use 192.168.0.10:portnum/tables/todoitem I get "Bad Request - Invalid Hostname".
By default, your Mobile App .NET server backend application will run in IIS Express. This is problematic when debugging with a client application running in another device on your network, or in a virtual machine in Hyper-V (such as Windows Phone Emulator). IIS Express will host your server application under localhost, which makes the application unreachable to other devices or virtual machines. Your client application running on Windows Phone Emulator has a different meaning for localhost. The same is true for the Visual Studio Emulator (which runs in Hyper-V) and the Google Emulator.
It is simpler to configure your machine to host your Mobile App .NET server backend application on IIS, as this allows you to control the binding of the server application to an IP address, rather than localhost.
For information on this, see: https://github.com/Azure/azure-mobile-apps-net-server/wiki/Local-development-and-debugging-the-Mobile-App-.NET-server-backend
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.
Windows 7, VS2012-Update1, x64.
If i start e new MVC-project, and add the Azure project to it. I can't debug it locally in the azure emulator.
The error:
Operation taking longer than expected
A 64-bit debugging operation is
taking longer than expected. This may be caused by incompatibilities
with 3rd party networking softwar. See help for troubleshooting these issues.
When i Terminate that message (twice):
Windows Azure Tools for Microsoft Visual Studio
There was en error attaching the debugger t the role intances
'deployment18(18).mvctest.Azure.Website_IN_0' with prces Id:'8752'.
Unable to attach. The Microsoft Visual Studio remote debugging monitor
has been closed on the remote machine.
The first message, I already found that if you change your website target to x86 that this can solve the problem. (this solved a problem for debugging unit-tests)
But if I change it to x86, the nex message pops up:
Windows Azure Tools for Microsoft Visual Studio
Cannot start debugging. The role was built for a platform incompatible with the windows azure compute emulator. On this system the compute emulator supports anyCPU and x64.
If i start without debugging (not x86), the windows emulator starts, and the website opens.
Is there a solution to solve this that we can debug x64 websites on the azure emulator?
Thanks.
Problem solved:
The issue was, that oour normal account didnt had admin privileges, and that we had to use an other admin user his credentials to run it in admin mode.
If i logged on with that admin user and started everything, that user couldn't also load the azure emulator.
Every co-developer had the same issue.
But when the normal account had back the admin privileges, the emulator started normally.
So i assume that there was something missing for those admin account (what i don't know)
Ensure that the remote debugging service and the machine debug manager (for x64) are properly installed and running (services in Automatic, especially not disabled).
You can also try to download and reinstall the remote debugging tools following instructions here
Even if it is on the same machine, chances are that debugging for the emulator goes through the remote debugging path
Been googleing this for a while now and it looks like the problem is connected to network drivers installed on windows. Do you have a VPN installed? Uninstall it and try again.
Otherwise it could be some of the network card drivers. Same here, uninstall and try again.
Some people have solved this by upgrading visual studio.
I am using some example code, http://www.windowsazure.com/en-us/develop/nodejs/tutorials/app-using-socketio/, to create a basic socket.io app with the WorkerRole. Upon starting the emulator, I go to access: 127.0.0.1:81, but IE will not load the page saying it's not accessible.
Here is the output of powershell
PS Y:\Project\WorkerRole1> Start-AzureEmulator -launch
Creating local package...
Starting Emulator...
Role is running at tcp://127.0.0.1:81
Role is running at tcp://127.0.0.1:8
Started
Edit: Another note, I am using the Parallels VM with Windows 8 on OSX 10.8.2
Please check the value of process.env.port to see if it's 80 or 81. This might because you are listening on 80 but the local emulator use 81.