I have read through the previous answers on this topic as well as other coverage online. But I still can't get this working. I have not worked with CE/hardware code before.
I am working with legacy code for a barcode scanner in VS 2008 and deploying the application as "USA Windows Mobile 5.0 PocketPC R2 Emulator."
Initially we were getting an error that the emulator could not connect to the rest server that I was running on my machine. After researching that, I decided to host the rest server on a different machine to avoid the issue. Calls to the rest server work fine using Postman.
ERROR:
Now when I attempt to run this solution, the rest calls return the error "Could not establish connection to network."
ATTEMPTED FIXES:
I can't get a network connection to work by playing with the settings under:
File -> Configure -> then select Network tab on the Emulator Properties dialog.
Selecting the "Enable NE2000 PCMCIA network adapter and bind to:" does not work:
Every option under this results in an error that "The required Virtual Machine Network Driver could not be found. Make sure that Virtual PC 2007 is installed. You can install ..."
But of course, I cannot install because Microsoft has stopped supporting this stuff at all.
I tried selecting the "Host-only networking" option.
I tried using Tools -> Device Emulator Manager in Visual Studio and setting the emulator to "Cradle"
set up conn with my ip and dns
Why does Microsoft still hate developers?? :(
Related
I've developed a small app for Windows Mobile 6. This app uses 2 databases: a sqlite db located on the mobile device and a SQL Server database located on a server (now it's on the same PC I'm programming with, a Windows 7 system).
When I developed it, I could test the app with the Windows mobile emulator integrated in Visual Studio 2008, and it was fine.
But now I've turned on this computer again to modify the project. But now I can't test it. The emulator can't connect to the SQL Server database (the error is "SQL Server does not exist or access denied").
On the SQL Server, I've created the user the app is using and it has the permission to connect (in fact, the connection works fine from some desktop applications we have developed).
On the config of the emulator, I've checked the PCMCIA option with the connected card.
I've tried too by installing a Windows 7 system on VirtualBox on other PC, but the result is the same: I can't connect with database.
If I open the Internet Explorer on the emulator, it hasn't connection.
What can I do?
Thanks
Finnaly, I found the problem.
I was trying to connect by "localhost" and by "127.0.0.1"... but it only worked when I used the internal IP (192.168.1.X)
I'm getting an error :
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named 'minwinpc'. The Visual Studio 2017 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
I'm trying to deploy an app to my RPI 3 running Windows 10 IoT Core v.10.0.16299.15.
I've tried:
Reinstalling Visual Studio 2017
Installing Visual Studio 2017 Remote Debugger.
Restarting the VS.
I noticed that Visual Studio 2015 remoter debugger is running on raspberry pi and it has 192.168.0.6:8116 as a remote machine name while in VS2017, rpi's address is 192.168.0.6:4002. Why are they different? Can someone help me?
As Martin & Belekz mentioned,you can check the configuration of target device and firewall setting.And more,I want to add that,please note the configuration of Authentication Mode.You should set it as "Universal(Unencrypted Protocol)".Use the mode whenever you are deploying to a remote device. Currently, this is for IoT devices, Xbox devices, and HoloLens devices, as well as Creators Update or newer PCs.
Look at my post here i have the same problem and i tried several things, but only after i done this i can deploy remotely to pi again:
Uninstall old 16299 SDK and download new 16299 SDK from here
Repair VS from VSInstaller
run sfc /scannow
Also make sure you're using Universal authentication mode and type the ip without port number (or even using 'minwinpc' is enough)
hope this helps
I never deployed software from VS to a RPi using an port in the IP address before. So maybe you are doing something special, or I'm doing something basic, but;
dubble check if you need to assign a port.
Start Windows 10 IoT Core Dashboard and check if the Pi is visible
in your network.
--> If not, try to ping to your Pi, using the CMD
ping 192.168.0.6
--> If the ping fails, check your IP address of your Pi with a physical
monitor.
Check the address in the build properties according to the steps above.
Hope this helps!
You can configure the remote debugger's IP address and port to point to the correct endpoint of your Remote debugger.
Right-click the UWP app project, choose Properties, and in Debug tab you will see Start options with Target device which should be set to Remote Machine and below you can manually enter the Remote debugger's IP address and port into the Remote Machine field (192.168.0.6:8116 in your case). You should include the 8116 port in the Remote Machine field as well.
This should make Visual Studio connect to the Remote debugger instead of the RPI itself.
Also try to turn off the firewall to verify if it does not interfere with the connection.
i have see same problem in my laptop. i solve this problem by following steps..
first of all can you install Windows 10 IOT SDK in your .net?
if no then first of all download and install.
otherwise update vs 2017.
when install vs 2017 then automatically install iot sdk.
I am using MS Visual Studio 2013 Professional Edition with Update 3. When I try to deply a WP 8.1 to the mobile device, I am facing the following errors.
Error: DEP3100: Attempts to stop the application on target machine "127.0.0.1" failed.
This may cause the deployment to fail.
The network connection to the Visual Studio Remote Debugger has been closed.
Error DEP2300: The deployment tool (TailoredDeploy.exe) failed to run on the target machine "127.0.0.1".
The object invoked has disconnected from its clients.
I have earlier deployed application to this mobile device.
Why am I facing such an error now?
I manually uninstalled the app. And when I tried to re-install the app, the same error occurred. But the solution was more simpler than I thought. I restarted the phone after switching it off. Voila. Worked. I installed the app once again. Successfully debugged the application & was able to deploy it to the device.
PS: But still I don't know why this error occurred.
I deployed a web role in windows Azure, based on the following tutorial.
http://weblogs.asp.net/scottgu/archive/2013/10/22/windows-azure-announcing-release-of-windows-azure-sdk-2-2-with-lots-of-goodies.aspx
but when I try attaching the debugger I get the following message:
"there was a failure to launch the remote debugger"
apparently this is a known issue, and the suggested solution from Microsoft is to restart the visual studio and try again, which unfortunately didn't work for me
http://msdn.microsoft.com/en-us/library/windowsazure/dn459835.aspx
Remote debugging may fail to attach to an existing Cloud Service:
After deploying a new Cloud Service the debugger may fail to attach to
an existing cloud service with the error message “There was a failure
to launch the remote debugger”. To correct this problem, restart
Visual Studio and reattach the debugger to the new deployment.
So I thought to ask here in case anybody faced the same issue and found another solution other than restarting the visual studio!
I'm using visual studio 2012, with Azure SDK 2.2
Make sure that you deployed a Debug build to your web role and that you have checked "Enable Remote Debugging for all roles" on the advanced tab during deployment. Failure to do either of these could lead to the problem your seeing.
I was using Azure SDK 2.2, so as to use "Attach debugger", but unfortunately I needed to use SDK 2.1 as 2.2 needs some references that weren't included in 2.1, so I guess this is the problem.
Thank you all for your help
I tried all of the solutions above and found that none worked for me. My problem turned out to be stale or inaccessible certificates that the VS debugger uses to connect to the service. I discovered this was the problem by going to event viewer and found:
A fatal error occurred when attempting to access the SSL client
credential private key. The error code returned from the cryptographic
module is 0x8009030D. The internal error state is 10003.
I had had other problems with permissions on private keys and so I ended up deleting all of the certificates from my personal store (current user) with the "Issued To" equal to "Windows Azure Tools". When I redeployed my service VS created new certificates and uploaded them.
Voilà -- attach remote debugger works again.
I got the same exception trying to remotely debug a VM in Azure, following the guide in Debugging Azure Virtual Machines.
What worked for me was to simply install the remote debugging tools matching my version of Visual Studio (VS2013 Update2).
Further I had to add a new endpoint in the Azure portal. This didn't work initially but eventually using the same public and private port number did the trick. The default port of 4018 worked.
Start the remote debugger program on the client machine in adminstrator mode and remember to set to port number, e.g. to 4018. I chose Windows authentication as well.
From within Visual Studio: Debug menu -> Attach to Process -> [yourVMName].cloudapp.net:4018 or whatever port number you chose. You should now see a list of processes on the virtual machine.
In case its helpful for someone else, I've just spent 3 hours on this! In the end I gave up and using 'Cloud Explorer' (in VS 2013, after installing the Azure SDK) I selected 'Disable Debugging' and noticed it cleared out port rules in the Network Security Group for the VM.
I hadn't seen it set these up (which is where I'd spent hours guessing that these were the issue and trying to figure them out from patchy MS documentation, broken links, etc).
So, I 'enabled debugging' for the VM and saw it set up security rules - something it didn't do the first time!
At a guess this is because I had initially enabled debugging for my VM soon after I installed the Azure SDK into VS. Since then I rebooted the VS server, and that may have enabled something in the SDK.
Anyway - before spending hours figuring out ports, reboot the VS server and then disable/reenable debugging in Cloud Explorer - you should see a status message (in the Azure Activity Log) saying 'Configuring networking security group debugging port' - this is the magic step that it didn't do the first time around.
I think you should try lunching VS in administrator mode, and see if you always have the same problem.
Else I think you should put more details about your problem.
This is what I did to enable debugging on an Azure VM.
At the time of this writing my current setup is as follows
Windows Server 2012 R2 IIS 8.5 (Virtual Machine)
Visual Studio 2013 Update 4
Microsoft Azure SDK Tools 2.5
Update Visual Studio to the latest Azure SDK
go th the server window (server explorer)
Expand the Azure node
Expand the virtual machines node
Right click on the VM you want to debug
Choose "Enable Debugging" Visual Studio will begin to add a debugger extension to your virtual machine
Once complete, Right click on the virtual machine from the virtual explorer and choose attach debugger
I am interested in working with blob storage from a Windows Phone app.
The Windows Azure Toolkit for Windows Phone should enable this. http://watwp.codeplex.com/
They have a sample application on NuGet which you install in a default WP application from VS, by running the command:
PM> Install-Package Phone.Storage.Sample, in the Package Manager Console
http://www.nuget.org/packages/Phone.Storage.Sample
The only configuration needed to run the app is to change the default navigation page in WMAppManifest.xml to "/Pages/StoragePage.xaml".
But when I try to run this sample application in a default WP app from VS, I get the error:
"The value for one of the HTTP headers is not in the correct format. RequestId:38df4766-0da8-4212-84a1-3da0c994a876 Time:2012-06-06T14:50:02.0209600Z"
Any idea what to do to make it work?
As you just made one changes in your sample, I believe you are using Azure Storage Emulator. Have you verified if Azure Storage Emulator is running. Also be sure to have a physical network in your main machine rather then virtual network to connect as i have seen such problem with virtual network and loopback address.
It is very much machine specific issue as I just tried to exact same step with no error. There could be any random error for this issue and while you try to restart the machine, re-install sdk and other components and it will go away. I can help you to find some ways to trouble shoot it:
When you run this application in WP emulator, while using Development storage the HTTP request pass through localhost:PORT/storage_container means the network traffic is on localhost so you can run fiddler to capture traffic on 127.0.0.1 (by default it is not set so you need to configure it. Once you have network trace you can find the root cause however it would hard to find the fix, as i have seen in past.