N
Nicolas Bsag
Guest
Hi,
I've scoured the web for several hours (quite literally) and am still unable to solve a rather unsettling issue with Visual Studio 2015.
Context: my company uses Visual Studio 2015 Community edition. Our machines all pertain to the same domain (managed by a Samba-3 domain controller using OpenLDAP as a backend) so we all use domain accounts to log into Windows.
Issue: Visual Studio 2015 encounters a problem while trying to renew the 30-day license when using a domain account. We get this message, no matter which Microsoft account is in use: "We could not download a license. Please check your network connection or proxy settings".
However this problem does not occur when using a local Windows account, and the license can be renewed just fine.
Even more puzzling is that when using a domain account, every time we start Visual Studio, it says we are disconnected: "An error has occurred and we can no longer retrieve user information [...] Please reenter your credentials for this account". We can then log on successfully, but if we restart Visual Studio, it says we are disconnected once again.
This problem does not occur either when using a local account.
Both issues can be reproduced on any machine in our network, and using any of our individual Microsoft accounts (registered using our work mail addresses).
Since we can validate the license just fine when using a local Windows account, this is not a proxy or firewall issue. It seems to have something to do with our domain.
If you have any idea, I'll be happy to hear it. As said above, I already scoured the web thoroughly, but it does not seem anybody has brought up a similar issue before, with the exception of one thread, which sadly does not offer any solution. I cannot link to because my account hasn't been verified yet, but you can find it easily by searching for "VS2015 Community cannot download license nick sagal".
Other remote threads dealing with "could not download a license" error were mostly related to proxy settings or IE TLS shenanigans, which have not helped in our case.
Cheers,
Nicolas
Continue reading...
I've scoured the web for several hours (quite literally) and am still unable to solve a rather unsettling issue with Visual Studio 2015.
Context: my company uses Visual Studio 2015 Community edition. Our machines all pertain to the same domain (managed by a Samba-3 domain controller using OpenLDAP as a backend) so we all use domain accounts to log into Windows.
Issue: Visual Studio 2015 encounters a problem while trying to renew the 30-day license when using a domain account. We get this message, no matter which Microsoft account is in use: "We could not download a license. Please check your network connection or proxy settings".
However this problem does not occur when using a local Windows account, and the license can be renewed just fine.
Even more puzzling is that when using a domain account, every time we start Visual Studio, it says we are disconnected: "An error has occurred and we can no longer retrieve user information [...] Please reenter your credentials for this account". We can then log on successfully, but if we restart Visual Studio, it says we are disconnected once again.
This problem does not occur either when using a local account.
Both issues can be reproduced on any machine in our network, and using any of our individual Microsoft accounts (registered using our work mail addresses).
Since we can validate the license just fine when using a local Windows account, this is not a proxy or firewall issue. It seems to have something to do with our domain.
If you have any idea, I'll be happy to hear it. As said above, I already scoured the web thoroughly, but it does not seem anybody has brought up a similar issue before, with the exception of one thread, which sadly does not offer any solution. I cannot link to because my account hasn't been verified yet, but you can find it easily by searching for "VS2015 Community cannot download license nick sagal".
Other remote threads dealing with "could not download a license" error were mostly related to proxy settings or IE TLS shenanigans, which have not helped in our case.
Cheers,
Nicolas
Continue reading...