I'm experiencing some problems while using the DocumentDB Emulator (v. 1.11.136.2).
I'm able to see the Explorer (https://localhost:8081/_explorer/index.html) but I cannot create any Database\Collection using either the Explorer and the SDK (I tried with the sample code provided by that page and my own code).
I always get:
{"readyState":4,"responseText":"{\"code\":\"ServiceUnavailable\",\"message\":\"Service is currently unavailable.\\r\\nActivityId: 9c9f56f8-91f9-4fad-b592-0c6bd5bbd300\"}","responseJSON":{"code":"ServiceUnavailable","message":"Service is currently unavailable.\r\nActivityId: 9c9f56f8-91f9-4fad-b592-0c6bd5bbd300"},
"status":503,
"statusText":"error"}
I'm running Windows 10. I already tried to restart the PC and reinstall the SDK\Emulator.
To fix this I had to perform a "Reset Data" on the Emulator.
This is probably due to some issue around updating from DocumentDb to Cosmo Db emulator.
Microsoft Support answer:
The failure is when the emulator tries to bring up the network stack.
We have seen this on some customer machines where 3rd network filter
drivers break some of the Windows networking APIs that we use.
Examples of these include drivers installed by Pulse Secure (or
Juniper network). I think we’ve also seen this type of failure with
some 3rd party antivirus products.
Typically uninstalling the 3rd party software should resolve the
issue.
I tried to change ConnectionMode to Gateway as
to
and it worked perfectly
I have been using VMWare Fusion 7.1.0 on my MacBook Pro with OSX Mavericks (10.9.5) without a hitch for several months. It was also working fine this morning until about an hour ago when I suddenly started getting an error message for any URL I tried: "Unable to connect to Proxy server."
I've tried both NAT and Bridged network adapters with no success.
There are no new software installs or updates (that I'm aware of), and I've tried restarted both the VM and the Mac itself twice.
Any suggestions?
I'm not sure how it happened, but my Network Proxy settings had gotten changed and set to use a manual proxy setup. I turned that off, and it resolved the error.
Here's how I found and fixed the settings:
Hit the Windows key (to get to the home page and do a text search)
Type "proxy" In the search results, click "Network proxy settings"
On the lower half of the screen under the Manual Proxy Setup, make sure the switch for "Use a proxy server" is turned OFF.
I'm doing web development in (primarily in Visual Studio Express 2013), so I wonder if the it jacked with my settings to allow for localhost development?
Check your VM's OS networking settings and ensure auto-detect proxy settings is not enabled.
I was working on a windows store application and got this error while trying to renew my developer license. I have tried a lot of things by running updates and restarting my computer. I am working in a VMware environment. I have not been able to renew my developer license. Any one has an idea on how I can fix this problem?
This error seems to happen with incorrect date/time or failing Internet connection:
http://windows.microsoft.com/en-gb/windows-8/activation-errors
I just started playing around with Azure platform. I tried to upload a simple application to Azure cloud to see how it works. For that I m using Eclipse Indigo and the eclipse plug-in for Azure.
However I get the following error while publishing to the cloud:
" Filed uploading deployment package (.cspkg)"
I searched aroudn and I see that other people have the same problem.
The size of the application is 382MB !!!!! I guess that s why I Get this error.
However why is the size that large?I only have a hello world app with one .jsp file.
When running to the emulator I point to the server installation that I want to use. Is afterwards the whole installation being uploaded to the cloud while publishing? Even in this case , I use Tomcat which is about 50 MB? Where are the rest 230Mb coming from ?
How can i reduce the size of my app?
I d also like to know whether the Eclipse plug-in for Azure is supported by Eclipse Indigo. I read on the Azure site that Eclipse Helios is required.
I have a web application asp.net to deploy to Windows Azure. I try to run it on local first. But when debugging, I catch this error from VS2010:
"There was an error attaching the debugger to the IIS worker process
for URL 'http://127.255.0.0:82/' for role instance
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0'.
Unable to start debugging on the web server ......."
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me.
I had similar problem with Windows 8, debuging a cloud application with Visual Studio 2012 RTM and Azure SDK 1.71, when trying to launch the application into the compute emulator. It was a very simple app, but I used Azure diagnostics. At the end these are two things I have changed that have work for me, both turning on Windows 8 features (so go to Win8 and open 'Turn Windows Features On/Off'.
Activate the checkboxes for:
Internet Information Services Hostable Web Core
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5
Internet Information Services > World Wide Web Services > Health and Diagnostics > Tracing
Internet Information Services > Web Management Tools > IIS Management Scripts and Tools
That worked for me, it makes sense, as I'm using Visual Studio 2012 and trying to get some trace information using diagnostics in Azure.
I hope this will work for you or give some tip about the problem. In the case of being useful information, remember to vote as response or as value tip.
Thanks,
Mike
This usually happens when there's a problem with the project to be deployed to the emulator (WindowsAzureProject2 in your case).
Try the following:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log file for the error messages. See more details in this answer.
Make sure your project can be started without the emulator. It's a web project, so just try to start it as a regular web project. Or publish it to the separate folder and try to create a website in IIS of it.
Check your *.csdef and *.cscfg files to make sure all the configuration is correct.
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to deployment16(6).WindowsAzureProject2.WebApplication3_IN_0, right click --> Explore.... Make sure that this folder is not empty and contains all the files required to start a web project successfully.
BTW, there's a similar question: Debugger can't connect when starting local azure project
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk
I just have today the same problem trying to Debug locally with Azure Storage Emulator in Windows 7. So in the Azure project properties, in Web tab, I checked the radio button 'Use IIS Express' and it debugged without problem. I hope this helps someone.
I encountered this exact same problem when I upgraded an existing Azure solution to the Azure SDK 2.1. After some hunting around I uncovered that the upgrade had automatically set the "Local Development Server" setting to "Use IIS Web Server".
Changing the "Local Development Server" setting to "Use IIS Express" fixed the problem immediately.
To access this setting right-click the Azure cloud project file in your solution, select the "Properties" option, tab down to "Web" and you'll see the following setup.
Also, make sure you run Visual Studio as administrator
Please check the version of emulator you have installed. If your code is created in older sdk and you have a new emulator installed it will give you this error.
Check the version of Azure APIs in your project, go to Project > references and right click on Azure dlls to check the version, same sdk version must be installed on the system, higher are optional as azure 2.x are not backward compatible.