When I try to deploy a windows 10 app using remote debugger, I get this error "DEP0100 - deployment failed due to a developer licensing issue windows 10 while trying to remote a windows store app."
From what I understand, there is no concept of windows developer licensing in windows 10, all I have to do is to enable developer mode from settings.
I have still tried to renew developer license using powershell.
Is there any solution for this issue?
PS. Remote debugging was working earlier, it suddenly started giving this error.
Edit: This is happening only when remote debugger is running as a service.
This may seem like a really dumb solution, but I had the same issue and couldn't find what's wrong, until I enabled developer mode and it all worked.
To enable developer mode on Windows 10:
Click Start
Type "For Developers Settings"
Switch to "Developer Mode"
Not sure about this, but make sure the account you're using to run the service is allowed to do developer stuff on your machine.
Here's what I would do:
Generate an account on the machine with admin rights (e.g.
"myadminuser")
Log in as "myadminuser" and enable developer mode for
that account on the machine. (You might have to provide a Microsoft
account here) This will allow the account to install apps.
Configure the service to run with user "myadminuser".
I didn't try this, but this should work.
Related
I have a Windows 2016 Server with IIS 10.0.14393.0 installed that is maintained within an isolated VM environment. (The entire VM environment is isolated from the real-world.)
The web server is configured with three websites through IIS, and each website is assigned a dedicated IP. The contents in each of these websites is a single "hello world" html page that can be accessed via a browser from from my development workstation using Microsoft Edge, but I cannot access these pages using Chrome. The simple hello world html page was created only to assist in troubleshooting this issue.
The error received in Chrome is ERR_TIMED_OUT and based on the IIS logs, the request is never reaching the web server. IIS logs do indicate the request/reponse when accessing using Edge.
From my workstation, I can successfully ping the web server, traceroute output does not indicate any unexpected hops, etc. From all indications, the problem appears to be isolated to Chrome and only when accessing the sites on that server. I have other servers (W2016 and W2019) in the real-world with a similar configurations and real applications deployed there that work as expected with any browser.
I am using the latest Chrome Version 105.0.5195.102 (Official Build) (64-bit) and can access other web based content within this VM environment using Chrome, just not on that one server.
I am almost to the point of deleting that VM instance and starting over so any ideas/suggestions are appreciated.
The error received in Chrome is ERR_TIMED_OUT
This is a communication problem indication that there is a problem with the user's local network connection. It can appear when your internet is too slow or your connection is taking too long, or the page or website you are visiting may be too busy, or when the website in question is not set up correctly, or even if the website is trying to perform more than your server can manage.
I'm not sure if you've seen the following methods, but you can try.
Method 1: Browse in Incognito Mode and Remove Extensions.
You should first browse the website in incognito mode to check if you
can open the website normally, if so then the culprit of the
ERR_TIMED_OUT error may be your plugin or extension. Therefore, you
need to enable extensions one by one to check for errors, and if there
is an error enabling an extension, you need to remove it from your
browser.
Method 2: Delete the Default Chrome Folder
Press Win + R keys at the same time to open the Run
Type %LOCALAPPDATA%\Google\Chrome\User Data\ in the box and click OK.
Close your Chrome if it is opened.
A new window pops out, find the folder named Default. Backup the folder anywhere else, then right-click the folder to choose Delete.
After you have deleted the folder successfully, open your Chrome and
then visit the webpage again that you searched before to check if the
error still appears.
Method 3: Update Network Drivers
If your network driver is out of date, you may encounter ERR_TIMED_OUT
errors. Here's how to update network drivers.
Right-click the Start button to select Device Manager.
Scroll down to find Network Adapters and click on it to expand it.
Right-click on your network device and select Update Driver.
Select Search automatically for updated driver software option to start to search and update your network driver to a new version.
After that, restart your computer and open the sites again with Chrome
to see if you can open them.
Method 4: Disable Firewall & Antivirus Software
Sometimes, your firewall or antivirus software may cause trouble.
Therefore, you should try to disable them and check if the problem can
be solved. If you find it helpful to disable these programs, you can
check the firewall settings. Allow Chrome to connect to public or
private networks. If it doesn't work. Permanently delete these
programs, and then use other antivirus software or firewalls.
Method 5: Check Hosts File
When you meet the ERR_TIMED_OUT error accessing a specific website,
you can check the Hosts file to see if the website has been blocked.
Here is the way to do that:
Press Win + E keys at the same time to open File Explorer and then go to the Local Disk C: > Windows > System32 > Drivers > etc.
Open the host file with notepad. If you see the web address that you cannot visit, delete that entire line from the host file and save.
After that, open the Chrome and see if you can open the specific
website.
Method 6: Reinstall Chrome Browser
If none of the methods above fix the ERR_TIMED_OUT error, then you
should try reinstalling Chrome. Here is the tutorial:
Press Win + R keys at the same time to open the Run box, then type appwiz.cpl and click OK to open a new window.
Find Google Chrome in the list, and then right-click it to choose Uninstall.
After uninstalling Google Chrome successfully, you also need to delete its leftover files. Open the Run box again, then type %appdata%
and click OK to open a new window.
Find the Google folder and then right-click it to choose Delete.
Go to Google Chrome’s site to download the latest version of the browser, and then install it.
The above methods are from the web article. To avoid link being unavailable, I have also presented the details. I am not sure if the above methods can help you, but I hope you can solve the problem soon.
I am developing a webpage that uses camera. When I test in Chrome in my local network, camera doesn't work and I get warning in the console:
getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See link for more details.
In the link provided there is an instruction to set some flags in Chrome. So I tried. My command looks like this:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --unsafely-treat-insecure-origin-as-secure="192.168.0.15" --user-data-dir=c:\chrome-dev-profile
But when I run Chrome I get this message:
You are using an unsupported command-line flag: --unsafely-treat-insecure-origin-as-secure. Stability and security will suffer.
What am I doing wrong?
Is there another way I can test in local network without setting up https server? I need this just for development.
Luka,
I've run into this bug just yesterday. I have not found out how to get Chrome to honor that flag on the command line yet. But I did find a workaround that works for my case.
I'm running my web services on a Linux machine that is running an ssh server. I'm testing on windows with chrome, and used putty to connect to the linux box from windows and then created a "local port forward" to make my remote linux box's ipaddress:port appear on localhost:port on windows. Depending on your platform this workaround may work for you. This approach isn't too cumbersome if you only have a few ports to forward.
In my particular case my setting for putty looked like
L8080 localhost:8080
To see more about port forwarding and ssh see: https://help.ubuntu.com/community/SSH/OpenSSH/PortForwarding
I have windows server machine on GCE.Whenever I try to take remote or RDP into machine it is showing
The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.
Please contact the server administrator
I have reset the machine but didn't work. The solutions that I got on the net needs access to the machine first, but I am not able to access the machine. Here is a link http://www.dell.com/support/Article/us/en/04/635765/EN to troubleshoot this, but I am not able to access machine as the machine is on google server.
In my case license has been expired. But I was able to take remote in admin mode. Use the command in Run to take remote in admin mode
mstsc /admin
Then I added new license to continue remote service. For more detail on remote desktop licensing check out the link https://technet.microsoft.com/en-us/library/cc732684.aspx
According to this post the solution is to delete the following key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
I Followed Sunil Garg's instructions:
mstsc /admin
to remote into the server.
Then I deleted the key. Please note you must run regedit as System user to delete the key. Use the RunAsSystem tool to achieve this
This problem made by some kind of caching of remote desktop licensing in clients you can solve this by remove the bellow key in registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
It's much easier to make a reg file and run it so .
Make a empty text file
Name it "mypatch.reg" or "mypatch.reg"
Put bellow text in it and save it
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing]
Run it by dubble click on file!
It should remove the key.
I am running a Windows Server VM Instace on Google Compute Services... I can access the instace via the "Windows Remote Desktop" no problem... I could install Team Viewer on the instance...
Because of Firewall issues I cannot run "Windows Remote Desktop" from my desktop to access that VM (google compute) Instance... Reason of why I installed Team Viewer on that VM instance...
The funny thing is that I can access that VM instance through Team Viewer Only, as long as it is connected through "Windows Remote Desktop" to a separate 3rd computer... (4G internet outside the firewall --of desktop trying to access the VM Instace through Team Viewer--).
Even if I minimize the "Windows Remote Desktop"on my laptop it will cut the connection through TeamViewer between the VM cloud instance and my Desktop computer...
Any help or ideas in there? It seems that either Team Viewer isn't able to start or somehow either the VM Windows Server screen only runs when the "Windows Remote Desktop" is running....
As I get this message:
"The screen cannot be captured at the moment. This is probably due to fast user switching or a disconnected/minimized Remote Desktop Session."
I did a complete version installation of TeamViewer as administrator, running on a Windows Server on google compute VM.
Hopefully someone out there can help me! I don't know if it may be part of the Google Compute Services Instance settings so as to limit the remote desktop only to the native "Windows Remote Desktop" program... Or perhaps a setting were since it's a VM the screen is de-activated when the "Windows Remote Desktop" program is off or minimized etc...??
My main problem is having TeamViewer work without having to initiate the native Windows RDP... In order for TeamViewer do it's job and take its place... as in the place where I am located (my desktop computer) the firewall blocks Windows RDP but does not block TeamViewer's.
I tried changing the listening port to different numbers....
According to the instructions here:
http://support.microsoft.com/kb/306759 and here:
http://support.microsoft.com/kb/304304/
Unfortunately.. when I changed it and then rebooted the Win Server 2008 VM, and checked to see if it made the change... I noticed it goes back to be on the same port again.... (of course to connect I had to do it through the original port)...
So it changes it but on rebooting it goes back to be on the same port again... I don't know if it's either because the new port was being used or there is a policy somewhere directing it always to the original port again...
I enabled those ports also to work for RDP in the Google Compute Instance interface, but still it made no difference...
It doesn't seem TeamViewer has a setting to change the port it connects with etc...
Hopefully I can find someone knowing about this issue.... The AWS instance used to work fine with LogMe In at the time.... I may end up using AWS (Amazon Web Services) again as Google Compute Srvs. won't do the job... but it's much cheaper than the AWS isntance... Thanks for helping...
In my case it happened due to slower network speed on the other side, of which I intend to take session.
The Windows Store App Cert kit fails to start.
Normally the flow is:
Start App Cert Kit
Choose Windows Store Application
Choose App
Choose Certs to Run
Run Certs
Save results
Currently, it fails just before 'Choose App'.
I get this result:
I have tried uninstalling and reinstalling, installed all updates, running appcert.exe reset. All to no avail.
I think it may have to do with the same issue I get with the Windows Store app. I have 38 languages installed (our app supports all of them) and the Windows Store app doesn't like it. I've had to escalate with customer support repeatedly for this, and have not had it resolved properly. I wonder if the same issue applies here.
So I was unable to start the UI, but I was still able to run the appcert by manually calling it on the command line as described here. It worked fine. One thing to note is that between each attempt, make sure to run appcert.exe reset.