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
Related
I am developing for HoloLens 2 and I don't have the device (I am using the Emulator to test).
I want to build the project with Unity and send the built package to a colleague that is not a developer - meaning, he is not good with Visual Studio - and who wants to test the app.
I tried using Microsoft Store and this worked for the initial P.O.C., but after the second submission I thought that it was going to be faster, but always takes up to 3 business days, which is not acceptable as a good workflow.
I know that, in ideal conditions, I should have the HoloLens, but this is not possible for now.
Do you have any idea on how to send packages to a non-developer person so that he can test the app in another country and so that it doesn't require a certification process like Microsoft Store?
You can take a look at the Sideloading feature provided by HoloLens Device Portal. Please follow this guide to connect the HoloLens over Wi-Fi or USB and manage your device from a web browser on your PC: Installing an app. In this way, you can directly send the app package to your colleague, and he can install it without using VS.
I'm working on a fairly customized version of NOPCommerce 3.10. I don't even know how this is possible, but I have cloned an existing NOP Commerce "discount requirement" plugin, changed all of the relevant pieces of code to reflect a new name, etc, and when I run NOP Commerce locally through the Visual Studio 2012 IDE and debugger, install and then attempt to use that discount requirement plugin, as soon as I select it from the discount requirement dropdown, my entire computer immediately crashes. Not the site. Not IIS. Not Visual Studio. The whole computer immediately just turns off. I've reproduced the same issue on 3 other developer workstations, so it's not something weird with my PC.
To make matters even more confusing, I published the site, including this plugin to our staging server, and not only does it not crash the server, or the site, but the plugin actually functions completely as expected without any perceivable issues.
EDIT: If I reboot in safe mode with networking, the issue goes away and the plugin works as expected. However, if I use selective boot, disabling all startup programs and all services except those that are required for networking and SQL server, the issue recurs. I'm not an IT guy, so I really don't know what's the difference between safe mode with networking and selective boot with all but networking services disabled, but clearly there is a significant difference as it pertains to this issue.
How is this even possible, and more importantly, what could be causing this and how do I go about finding and resolving the issue?
Edit 2: If I debug on any workstation that is not the same model as mine, it works fine. I believe I have narrowed the issue down to the Intel Integrated HD Graphics display device and/or driver. I've tried several different versions of the driver to no avail, so it seems like either the issue is with the device, or it is so obscure that it's never been identified or fixed by the manufacturer.
I wanted to access my laptop using my android mobile. I have already accessed using Team Viewer. But it require a Internet connection. I want to access my laptop on my android mobile.
Is there any way to connect.
Assuming your computer is running Windows you'll most likely want to use the built in Remote Desktop Protocol.
Microsoft has a free Andeoid app in the Google Play Store here.
Microsoft has a FAQ page for their Android app here which describes the necessary setup procedure.
If your computer is a Mac or running a Linux based OS you'll probably want to look into using VNC which is usually supported right out of the box although may require some configuration.
I cant find information on this error anywhere. I am connecting to a brand new lumia icon (AKA lumia 929). Dev account is registered. I have attempted:
reinstalling windows phone SDK
restarting phone
restarting computer
ensured the app runs on the emulators properly. the only required capability of this app is network. Capabilities have not been changed from the defaults since the project was created. none of the manifest xml files have been touched.
ensured phone software version is up to date
ensured apphub account is valid and active
ensured the windows phone developer registration tool worked, unregistered and re-registered the phone to make sure
restarting the "ip over usb" windows service thingy
changing the platform built target to ARM or AnyCpu (no difference, same error)
tried alternate deployment methods such as windows phone power tools (the xap deploy) and I get the same error when trying to connect (so I know it's not an issue with visual studio, nor is it an issue with the app code)
I can successfully deploy separate code to a separate WP7 device (so I know it's not an issue with the computer)
tried multiple usb ports
tried two separate laptops
tried visual studio 2013 and 2012
The behavior is this:
Connect the phone via usb and unlock it
Attempt to connect to phone via windows phone power tools OR deploy an app via visual studio
System hangs for about 90 seconds and seems to time out
Error appears
I am able to view the phone contents, name it and explore it on my laptop, but when it comes time to deploy something I am stuck.
Error message is simply: 0x89371B01
What does that mean? Has anyone else run into this?
Have you checked the device drivers on your Windows 8.1 machine? It could be a driver issue with your USB drivers on the computer.
I have also found that, once you get it connected, going into the Device Manager and deleting the device from there and forcing it to reload has helped me in the past.
Out of curiosity, try running "sfc /scannow" at a command prompt on the PC. It may require admin elevation. I've seen some bizarre behaviors due to dll problems in sxs in win 8.1, wondering if this could be caused by that kind of thing.
Couple of things to try:
Have you installed the GDR3 Emulators and tried running it on the 1080p emulator? It looks like the 929 is a 1920x1080 phone and will have the latest the latest updates installed. First place to check.
Based on this feedback in another stackoverflow question it looks like someone was having a similar issue and disabling Hyper-V resolved it for him. If you disable Hyper-V and it works, try re-enabling it and see if you still have the issue.
jmshapland had the correct answer for me, with the same issue. Disabling Hyper-V did the trick! No thanks to microsoft phone dev center forum posting on the issue..
http://social.msdn.microsoft.com/Forums/wpapps/en-US/24bd3e48-e7b4-4d00-8d69-193f49989ce0/0x89731b01-error-during-deploy-to-device?forum=wpdevelop
Looks like I'll be disabling Hyper-V to test on my device, and re-enabling to work in emulator mode:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and
dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
OK I was able to come up with a repeatable solution for the issue. Im HOPING that by posting this I dont tempt fate and have the phone not work again!
Here are the steps I did to resolve it (not sure if all of them are necessary):
On phone, disable wireless
Connect phone to laptop
Open device manager and click to show ALL HIDDEN DEVICES (including hidden devices is important)
Uninstall ALL phone-related devices (one in portable devices, several in USB
devices) anything that mentions lumia must go
Disconnect/reboot phone
Reboot laptop (there seems to be a process keeping the port open)
I had connectivity, then I lost it, then I re-gained it using these steps and it seems to be reliable for me (so far)
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.