Related
I have projects that I have controlled be Azure DevOps. Every time when I open some of these solutions in the Visual Studio I get following error in the team explorer:
So when I re-enter my credentials I get the same error again. But when I restart Visual Studio my project is suddenly properly connected to Azure DevOps.
Could you tell me why I have this issue and how to solve it?
You may try the following items:
Go to Control Panel > Credential Manager, and remove all Windows Credentials related to TFS.
Close all Visual Studio instances, and delete the %LOCALAPPDATA%\.IdentityService folder if it exists.
Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
As #4c74356b41 mentioned, repair VS.
As stated above, try doing only this step and see if it fixes the problem. It did for me.
Close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService if it exists.
It saves doing all the other steps.
The same issue is still occurring in 2021.
I had tried the sign out/sign in method, I had tried the local app data deletion method.
No luck with either.
What worked for me were the following steps.
Click on your name in the top right corner of Visual Studio and select Account Settings
Now rather than signing out, look below this to the All Accounts section. On some it will say "We need to refresh the credentials for this account"
Re-enter your credentials here.
This fixed the issue for me. I hope this helps someone else with this annoying issue.
Much easier solution to this. Close any open visual studio instances, restart visual studio as an administrator and connect to your ADO instance, i got this issue on cloning a repo personally, when i re-tried cloning again via web ADO the next time VS opened it worked just fine.
I've just had this same error as part of a wider issue with not being able to clone my DevOps projects, getting "connection reset" messages in Chrome and general weird behaviour for anything that tried to use my Microsoft login.
After a lot of hunting around, the cause of the issue turned out to be the Intel Killer wifi service. I opened the Killer Control Center app and turned off everything and all the issues disappeared:
Once I'd found the cause, a bit of googling turned up this post that suggests the Killer Prioritization Engine may be the root cause:
Bruno Nepomuceno 🎮 [MSFT] ··· I had the same issue and after a long
time I found out what was going on. My network card has a feature
called "Killer (I know, ironic) Prioritization Engine" and that was
on. Somehow it was interfering with the connection with Azure DevOps.
When I turned it off (and you can do it using the Killer Control
Center app), it started working.
I have an ASP.NET Core application which was running fine but while developing (and after the Windows 10 April update, most likely just a coincidence) suddenly, I got two messages:
This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed,
create an association in the Default Apps Settings page.
Unable to start program 'programName' Invalid pointer
Result: I cannot debug/ run my application anymore. (Start Debugging/ Start Without Debugging)
I found some scary search results talking about a corrupt file system but I don't think that it is something like that in my case...
I checked my startup projects, restarted Visual Studio, restarted the whole system... nothing helped.
Update: After installing the latest Visual Studio update (15.7.1), the message I get when I activate the JavaScript debugging again has changed. Now it states:
Cannot connect to runtime process, timeout after 10000 ms - (reason:
Cannot connect to the target: connect ECONNREFUSED 123.0.0.0.1:53232)
Result: Still the same. Only the error message changed.
Any hints, ideas about that one? Thank you!
If not an answer at least a workaround. I can work again if I tweak the debug options
Debug -> Options -> General -> Enable JavaScript debugging for ASP.NET
(Chrome and IE)
If I disable this feature, I can debug and run my application again. But I still don't understand why this is happening now nor how to use JavaScript debugging now...
I had this problem with Visual Studio 2017. It was caused by my antivirus (bitdefender) blocking a chrome temp file. I set it to ignore that file and that fixed my debug issues.
The file was C:\Users\[username]\AppData\Local\Temp\vschrome_diag.lnk
According to this, re-installing chrome may fix the problem.
Error launching vschrome_diag when Visual Studio 2017 starts debug on Chrome
I am trying to run any program on visual studio 2013 update 3 and I get the following alert box:
Process with an Id of #### is not running.
Every time there is different ID number showing.
and in the error windows, I get this error message:
The program '[3148] iisexpress.exe' has exited with code -1073741816 (0xc0000008) 'An invalid handle was specified'.
Sometimes it runs and in the browser I get the following message:
The webpage is not available.
Why is this occurring and how can I resolve it?
The following steps fix the problem for me:
Close Visual Studio
Navigate to the folder where your solution files are stored and delete the hidden .vs folder.
Restart Visual Studio
Hit F5 and IIS Express should load as normal, allowing you to debug.
Note: Based on my experience and others in the comments, this problem seems to be caused by moving a project between workstations, environments, or versions of Visual Studio. There must be some environment specific information contained in the .vs folder.
Open Visual Studio as an administrator
Right-click your project and click on 'Unload Project'
Again, right-click your project and click on 'Edit PROJECT_NAME.csproj'
Find the code below and delete it:
<DevelopmentServerPort>63366</DevelopmentServerPort>
<DevelopmentServerVPath>/</DevelopmentServerVPath>
<IISUrl>http://localhost:63366/</IISUrl>
Save and close the file .csproj
Right-click your project and reload it
First Error
For the first error:
Process with an ID #### is not running.
The following steps worked for me:
Close all instances of Visual Studio.
Rename the IISExpress folder (in my PC is in C:\Users\jmelosegui\Documents).
Add the _CSRUN_DISABLE_WORKAROUNDS Environment System variable with the value of 1.
Start Visual Studio in administrator mode. (In Windows, right click the executable file and select Run as administrator).
Second Error
The second error:
The webpage is not available
What caused this error:
I deleted IIS Express Development Certificate while playing with the SSL.
The following steps worked for me:
Go to Control Panel.
Select Add/Remove Programs.
Locate IIS 8.0 Express.
Right click on it then click Repair.
Your certificate should be back!
With respect to the first error:
Process with an ID #### is not running
This situation will sometimes occur when IIS Express fails to bind to a port. A likely reason for that is that some other process has already bound to that port. Visual Studio will launch the IISExpress.exe process (which will fail to bind to the port and exit again) and then attach to the now-terminated process, resulting in the above error.
To check, note the port number in your project settings (e.g. 12116) and then try:
netstat -ano | find "12116"
If another process has the port open, this will give its PID. You can then choose to kill the offending process or reallocate your own port number.
If you are using a 64-bit machine
Then the problem maybe due to Visual Studio use of 32-bit IIS-Express.
Solution: In Visual Studio, go to Tools menu > Options > Projects and Solutions > Web Projects > Enable the option "Use the 64 bit version of IIS Express" and click ok
I had the same problem. Just restarting Visual Studio worked for me.
My fix was simple, I was missing prerequisites. I needed to install .NET Core SDK
Kilanny's answer is correct. Most machines in 2015 are 64bit, so there's a lot of chances that you just need to enable the 64bit option under the Tools main navigation link menu. No need to configure other files or hard code ports. Besides, port assignment should be dynamic. This fix applies to 2013 With Update 3 and Visual Studio 2015 Community Edition.
Check the images below for a mini tutorial:
(I'm just improving Kilanny's answer)
It looks like there are many solutions that work and some that don't...
My issue kept surfacing after a few test iterations.
Yes restarting the PC and/or VS would resolve the issue...but temporarily.
My solution was to undo a security change I had enabled a couple days
earlier to Controlled folder access under Ransomware protection.
I undid this change by:
(right click Start)
Setting->Update & Security->Windows Security->Virus & threat protection-> Virus & threat protection settings->Manage settings
Under Controlled folder access
Click->Manage Controlled folder access
(this is also the Ransomware protection screen)
Turn Controlled folder access off.
This was 100% the issue for me as I was able to run my test without restarting VS.
Another reason this can happen is for a .NET Core Web app if you upgrade the Microsoft.AspNetCore.Components.* NuGet package to a new version but don't install the new SDK,
In my case it was upgrading Microsoft.AspNetCore.Components.WebAssembly from 6.0.0 to 6.0.1 and didn't install .NET 6.0.1 SDK
go to Properties of the start up project, increment port number of the Project Url is probably the quickest way to get around this problem which I didn't read anyone mentioned yet.
And you don't need to restart VS as it can be a pain sometimes if you needed a few other instances needed to be running.
My solution to this on a new machine and fresh install of VS 2022 was to install the 3.1 framework. So check to make sure whatever framework the project is expecting is installed on your local machine.
I had a similar problem with Chrome. It appears that VS can't attach to the Chrome process for some reason.
Solution:
Close Chrome
With Chrome closed, start the web project and allow VS to open Chrome.
For me, none of the other solutions worked.
The things I tried:
Updating and patching everything associated with Visual Studio
Reinstalling Visual Studio
Reinstalling IIS Express
Several reboots
Adding the _WORKAROUND thing to the PATH
Renaming the IIS folder under documents to regenerate the IIS config
Manually editing the csproj file and removing the whole IIS settings section
Changing the IIS executable usage to 64bit in VS settings
Changing the port of IIS in the projects settings
After checking if the problem was persistent over different projects, it turned out that the problem only occurred in one specific projects. I figured that I had to delete all the user specific files in the solutions folder (such as bin, obj, *.suo, ...)
I just deleted the whole solution folder and reverted the files in git.
TLDR:
Try deleting user specific files/folders like bin, obj, *.suo, ...
Reboot your computer before trying any of these!
Some of these may be helpful. Doing the netstat trick
netstat -ano | find
helped me as another application was using my port, but didn't completely solve my problem. IIS Express still kept crashing. It wasn't until I rebooted my win 10 PC (first time in over a week), that my problem completely cleared up.
Head to the following directory
%userprofile%\documents\IISExpress\Config directory
Delete all files within that folder. Restart visual studio and works like a charm.
I had the same problem, and what needed to be done was setup IIS Express properly.
I right clicked on my project Properties => Web (tab) and on Servers:
Project URL was already pre-populated and I clicked the button "Create Virtual Directory".
I had just reinstalled (refreshed) windows and the IIS was not setup b/c it was new.
I came across the same problem and found that somehow the file 'applicationhost.config' (in ..\Documents\IISExpress\config) had a different localhost port number (in the 'sites' section) to the one specified in project\properties\web. Changed them to the same number and the problem went away
Close VS.
Navigate to the folder of the solution and delete the hidden .vs folder.
Restart VS.
Hit F5 and IIS Express should load as normal, allowing you to debug.
If this not working, then:
right click your solution and go to properties
Click left menu Web tag
Click checkbox "Override application root Url"
and run again your project.
For me this was the solution,
Close all running Visual studio instances
Open the solution folder and remove the .vs folder (hidden folder)
Open Run Command
Type iisreset and press Ok, and you may see a command prompt and
wait for it to complete and it will close automatically
Now Open visual studio and run your project, it should run.
So, nothing worked for me and this happened to happen to me when I got a new machine. Apparently it didn't have the older versions of .Net on it. Went into VS Installer and checked the box for .Net 5 Runtime (VS 2022). Working fine now on all .Net 5 Projects.
TL;DR: if you do have the right .NET Core (or .NET I guess) runtime installed, install any patch updates or reinstall the latest version if there aren't any.
Detail:
Similar to a couple of other answers where they just didn't have the right .NET core installed. I was trying to run a .NET Core 3.1 web app which had worked fine previously for months, and this suddenly started happening.
I did have 3.1 (runtimes 3.1.21 and 3.1.22) installed. However a new one (3.1.23) had been released 12 days earlier, and installing that fixed the problem.
I have no idea if this was because it's aware that there's a new patch and I didn't have it so it wouldn't run, or if there was just something wrong with my 3.1.22 installation. Worth trying installing latest patch, or reinstalling existing installations.
I encountered this while trying to run a project I'd run many times on a machine I'd used for the project many times. Cleaning up my IIS Express directory and my .vs directory didn't work, nor did setting environment variables. I even tried re-cloning my repository to a different folder, but no success.
By trying to run via command line, I found a more useful message:
dotnet run --project [startup project path]
I saw that the project was trying to run using .NET 6.0.5, but I only had .NET 6.0.4 installed. Installing the latest .NET 6.0.5 from the Microsoft website worked.
I also had the same problem, doing the above didn't work for me. What my error turned out to be was twofold.
I had Opera as my default browser and it couldn't attach to that.
I had multiple startup projects so it wouldn't let me switch to IE until I change the default startup project back to just the MVC shell.
I set that project specifically as the startup, then I switched it back to launching IE and it started debugging again.
What I did to make this go away:
Open C:\Users\gr_mext1\Documents\IISExpress\config\applicationhost.config and remove all <site> entries in <sites> do not remove <siteDefaults>!
In your project, go to Properties, Web and click "Create Virtual Directory".
Close and re-open visual studio, load your project and run
Fixed!
None of the listed solutions worked for me. Problem was some sort of conflicting state in local applicationhost.config file. Fix is easy, just delete one in your solution. For VS2015 it should be located in <path_to_your_solution>\Solution\.vs\config\. When you launch Debug, VS will recreate that file based on settings in your project file.
Deleting the hidden .vs folder didn't work for me since the port specified in my app was being used by another app. Doing the following worked for me:
Went to properties and then click the web tab.
Changed the port number in the Start Url and the Project URL.
Clicked Create Virtual Directory.
Save and Press F5.
cmd - regedit-HKEY_LOCAL_MACHINE-SYSTEM-CurrentControlSet-Services-HTTP-START=3
Computer restarted.
worked for me!
Tried most of the things here to no avail, but finally found a fix for my machine, so thought I'd share it:
Following previous advice in another question, I had used netsh to add :: to iplisten. It turns out undoing that was my solution, by simply replacing add in their advice:
netsh http delete iplisten ipaddress=::
You can also do this manually by deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\ListenOnlyList from the registry and restarting the service/your PC.
I update my Visual Studio to 2019 version and has this problem, I tried all solution from this question but it doesn't help to start my ASP.NET MVC 5 project with IIS Express. After I remove IIS Express (using Control Panel), download last version from www.microsoft.com and install it. After this everything works fine.
After some weeks i got update for Visual Studio and I got this problem again. I remove IIS Express and reinstall and it works fine now.
p.s. repair didn't help me, only uninstall and install.
Latest Comment
I believe my problem occurs when using Nuget, however, if you are reading because of the TF30063 error. Have a look at the answer I provided and accepted.
Original Post
I am getting this error message when I try to check out. This happens randomly and can occur even if minutes ago the same instance of visual studio allowed me to check something else out for edit.
The current workaround is to reopen VS2010.
Using W7x64, vs2010 ultimate with TF2010 and sql2008 on my local dev machine. I am not part of a domain. I am the administrator of this computer.
Additional 2011-08-09
When the problem occurrs, I "close solution" under file. And then reopen the solution. I then get a uid/pwd box. I put my admin uid/pwd into it and then get a further error message. Again, closing vs2010 and reopening solves the issue.
Additional: 2011-08-30
I believe this has to do with nuget. I have provided an answer and so far after many months I have not had a TFS error. Where I should have had an error given the types of operations I have been performing which were identical to the scenarios making it fail.
I noticed that the problem occurred mostly after i installed a nuget package. After adding a nuget package i found that I could not check out. Restarting Visual Studio helped.
Based on this discussion:
http://nuget.codeplex.com/discussions/254328
i used this solution which appears to be working:
(I have copied the solution here if ever the webpage disappears)
Control Panel / Internet Options / Security Tab
Select "Local Intranet"
Click Sites button
Click Advanced Button
Add your TFS server http address to the list. e.g. http://tfs
Restart Visual Studio
Source: http://blog.rthand.com/post/2011/08/26/Fixing-combination-of-NuGet-and-Team-Foundation-in-workgroup-configuration-401-Unauthorized.aspx (Go straight down to The Solution half way down).
Don't let the Internet Options part fool you. I do not use Internet Explorer and this solved my issue.
I found this issue and the accepted solution didn't work for me. For me the problem occurred when trying to add a NuGet package to my project (through either the console or the GUI) and it would show the login prompt but not accept my user/password. It would try around 4 times and then fail and roll back the installation.
It turns out for me the issue was that I had Fiddler open and as soon as I closed it (to undo the proxy settings) I was then able to install the package without any issue. I didn't even have to restart Visual Studio to get it working.
Just thought I'd share this for the next person who comes across this issue.
I want to add a solution for people who are using VisualStudio online. My problem was that I was logged into VS2013 with the wrong Microsoft Account.
I would like to point that the accepted solution didn't work for me - probably it is for IE users.
My fix was to "clear the package cache"
Open VS
Go to Tools-> Options
Open "NuGet Package Manager" and select General
Click in the button: "clear the package cache"
When I had this problem I checked Event Viewer on my TFS machine and it showed a bunch of insufficient permissions Windows Sharepoint Service errors. I ended up just disabling the Sharepoint aspects of TFS since I wasn't using them anyways.
Got the error TF30063: You are not authorized to access Collection when comparing or merging the solutions in tfs 2012.
I found that enabling and disabling the windows authentication in IIS did randomly fix the error but found the disk space issue,
Once i cleared it, and enabled the windows authentication for TFS in IIS, it was a fix for me.!
-Pasha
This answer got me far enough to solve:
Control Panel / Internet Options / Security Tab Select "Local
Intranet" Click Sites button Click Advanced Button Add your TFS server
http address to the list. e.g. http://tfs Restart Visual Studio
On our internal network, for some reason, our computers don't always recognize other computers as being part of the domain - resulting in connections being sporadic/intermittent. My user had a restricted list set by domain policy, so I couldn't edit it. However, I could change the connection from just the computer name to the computer's fully qualified domain name and that appears to have solved the problem.
I've tried to install Visual C# 2010 Express edition onto my PC, but whenever I try to run it, I get a error message.
Invalid license data. Reinstall is required.
I've already tried reinstalling it, and the message persists.
OS is Vista Home Premium. I already have VC# 2008 Express installed.
I am using Visual Studio 2013 and I have the same issue but it occurs when I try to open a solution that was made using Visual Studio 2010.
The solution for me is to open the solution file (.sln), using notepad and change this line:
[# Visual Studio 2010]
to this:
[# Visual Studio 2013]
I just right-clicked, and opened with Visual Studio XXXX (in my case 2015). Then save it. Done.
I have the same problem with Windows 7 Pro. Have tried everything suggested by the Microsoft people, including uninstalling, cleaning up, reinstalling both from the web installer and the VS2010 Express iso - with the same result every time.
To say it's frustrating is an understatement and the disinterest from Microsoft in fixing what appears to be a common problem (you can find lots of search engine 'hits' for the problem, none for a solution) is quite unbelievable.
Since this is virtually a virgin Win7 install, the only conclusion is that MS have broken their licesing checks again (why check for a license on a free product?).
Edit: Following further investigation I have concluded that the advice given by Microsoft is useless and does not attempt to diagnose the problem. It simply assumes a corrupt installation source. I believe that the problem is in fact corrupt permissions/ownership of registry keys. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Licenses and subkeys needs to be owned by SYSTEM with admins having full access. On my affected system the owner cannot be displayed and no permissions are shown when viewed by admin.
I don't have the definitive fix for this so far, as I cannot adequately edit the permissions for the affected registry keys.
Re-installing Windows is an almost certain fix, but also an extremely drastic one.
I have had this EXACT problem with VS2010 Professional Trial / Evaluation download. I can provide clear and concise steps to reproduce:
Set your system clock ahead by 1 day (oops!)
Install the trial software.
Set your system clock back to the correct date.
Start VS2010, you will receive the vague message indicating "Invalid license data. Reinstall is required."
In my case, the resolution was quite simple - set the clock back ahead to the wrong date. The next day, I was able to set the clock back to the correct date and continue using the product.
Based on other answers to this question, it would appear there are numerous reasons that you could receive this message. This specific issue is most likely to be encountered by someone with a "virgin" install of Windows since it is not so difficult to set the clock incorrectly when setting up a new computer and then fix it later (and if you fix the clock hours after installing the product, it might be hard to put it all together and realize what happened).
Hope this helps someone else.
I had this issue but I was able to resolve this by right clicking and using Run as Administrator. This boots up the program just fine.
This worked for me on Vista. It's based on work-around at MS: http://connect.microsoft.com/VisualStudio/feedback/details/520110/invalid-license-data-reinstall-is-required
Download subinacl command line tool
http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=e8ba3e56-d8fe-4a91-93cf-ed6985e3927b&displaylang=en
Run these commands:
subinacl /subkeyreg HKEY_CLASSES_ROOT\Licenses /setowner=everyone
subinacl /subkeyreg HKEY_CLASSES_ROOT\Licenses /grant=everyone=f
Start VS 2010 Express again and this time it asks for a license key.
(On Windows 7 Home I had to run the above commands twice before they worked correctly)
I got the problem when instelled MS SQL 2012 with IngegrationService, the MS Visual Studio 2010 (Isolated) was installed from sql installer .
This VS returned error: Invalid license data. Reinstall is required.
I've fixed the problem by reinstalling SSDT with MS VS 2012 (Integrated)
http://msdn.microsoft.com/en-us/jj650015
I had this problem when installing a new SQL Server 2012 standalone Server.
Cause: When installing SQL Managemnt Tools it will install the VS Shell. It seems like this is all you need but this ist not enough! (it actually shows it will install VS)
Strangly the path and the application are shown in windows put you can't open them without the error.
Fix: You need to also install "SQL Server Data Tools" via Feature Add with the SQL-Server.iso
Hope this helps someone... i took me quite a while.
I get this error only when trying to open older solution files. For instance, I've got VS2013 installed and this error message pops up when I double click on a VS2010 solution file.
Getting rid of it is so simple:
Launch VS2013
Open the old solution file by clicking
"File->Open->Project/Solution..." from the menu (or simply by
pressing Shift+Ctrl+O)
Save the solution with the new format by clicking "File->Save
Solution As..." and overwrite the old file.
It appears that this has been reported as a bug, but has been closed as "Not Reproducible". One suggestiong from the Microsoft supporter is to redownload and reinstall:
Please try downloading the complete ISO from http://www.microsoft.com/express/Downloads/#2010-All, mount it as virtual drive. Then execute Visual C# setup from the ISO media and select an option to remove the product. Once the Visual C# has been uninstalled, please try installing it again from the ISO media.
It sounds a bit far fetched to me, but you might want to give it a try.
If that does not help you, I would suggest that you either post a new bug report to Microsoft or vote to reopen the existing one (I am not sure if/how this is possible).
I have faced this problem when installing the Visual studio 2010 - C# express using the local administrator account, then trying to register the application using another account that doesn't have Admin privileges, due to corporate polices this account can’t edit in the Registry by any means, so suddenly that’s how I figured out how to solve this issue I open VS 2010 as a local administrator then entered the registration key, and it is worked , I don’t understand how do that Microsoft itself didn’t mention this solution or even try hard to investigate or solve this issue
I just encountered this problem on a virgin install with a system that has a bad clock battery (when I turn off the power, it resets the date/time. Syncing to time.windows.com again allowed me to run VS2010 successfully.
It was not the clock for me, and all the hours spent re-downloading and reinstalling were a waste of time (except for the last one, of course....).
Also, for some odd reason, just adding Read permissions to the HKCR node using psexec -i -s regedit did not work by itself.
To fix my problem on Windows 7, I made sure (using psexec -i -s regedit) that my login account had full control permission over every node in the registry and that the everyone group had read permission over every node in the registry, and did all of the steps in the following link (rebooting after each step):
http://windows.microsoft.com/troubleshootwindows7sp1
This is probably overkill, but after spending 10+ hours trying to get this working, I am just happy it works... Good luck!
I was stuck for several days with the same problem. Investigating the registry i found several keys in HKCR were i was denied access even as adminstrator. Among these keys were the Licences key. Tried a lot of things to resolve this access problem but could not fix it.
Finally i worked around this problem with a reinstall of Windows 7 - choosing the Upgrade option when prompted to choose between upgrade or a fresh install. Had to reinstall video drivers but all my programs and user accounts survived.
http://windows.microsoft.com/en-US/windows7/Installing-and-reinstalling-Windows-7
After the upgrade i have access to the HKCR\Licenses again and Visual Studio 2010 starts as expected.
I had this problem and finally got passed it. I tried the solutions above to no effect. (I set my license keys to open permissions, set my clock forward, etc.) After two days I gave up...
In the end, I installed VS 2012 Express, which could handle VS 2010 solutions but could not compile 2010 code (without a COFF error). After finding this article on requiring VS 2010 to be installed to compile 2010 solution in VS 2012, I reinstalled VS 2010 even though I assumed it wouldn't work on its own. I tried opening 2010 anyway and it worked!
Analysis: as per the previous correct note by reece (and the original workaround author), I used ProcessMonitor to see what devenv.exe tries to do and fails.
Unfortunately, it was attempting to read a number of reg keys which were not under the Licenses node (so it wouldn't have been enough to take ownership of the latter with subinacl). Furthermore, even after taking ownership, the affected keys still yielded "ACCESS DENIED". Doing it as Administrator was equally useless. Plus, Visual Studio didn't fall for any date change nonsense either.
Solution - Don't try this at home :D though: I downloaded pstools and ran psexec -i -s regedit to get System privileges, then I changed permissions on the entire HKCR node to allow Everyone to Read (:P what can I say, viva el comandante).
I want to point out that adding "Everyone" to have read permissions on HKEY_Classes_Root did fix this issue for me.
I am not sure exactly what permission is needed, but this "worked for me" ... YMMV
This may also occur if you are trying to invoke an xml file instead of the exe application.
An another solution I have found to work is the one mentioned Mac by over at SuperUser: https://superuser.com/questions/651261/how-do-i-fix-an-invalid-license-data-reinstall-is-required-error-in-visual-s
When simply reinstalling the Visual Studio 2010 shell doesn't work, he points out that installing it through SSMS 2010 can solve the problem:
I was able to resolve my issue without making any manual changes to
the Windows Registry by installing SQL Server Data Tools 2010, which
is also free and includes the Visual Studio 2010 Shell.
You don't have to go through the entire install process. I cancelled the process when it was done installing the shell and it worked our fine.
If you're here from Google and are experiencing this issue with GFI MailEssentials's config export tool, check to make sure you aren't trying to open WebMon.SettingsImporterTool.exe.xml instead of WebMon.SettingsImporterTool.exe
If you have "hide common file extensions" enabled, you will see the .exe but not the .xml
Just happened to me with a new install of Visual Studio 2010 ultimate in a new computer.
This new computer had the internal time correctly set, but the date was set to one day late. I installed Visual Studio 2010 with the incorrect date. Then, I noticed of the incorrect date and changed it by sync'ing with a NTP server, and from that moment Visual Studio 2010 would not work... so I'll have to stop using Visual Studio 2010 until DateTime.Now > installationDate.
I met the same problem yesterday.And I fixed already.
Please follow the steps:
Run setup.exe again; Change or Remove Microsoft Visual Studio 2010;
Upgrade license Key (Enter new license key); Complete.
GOOD LUCK !
To everyone who has internet connection. Don't mingle with your
registry it's just a waste of time. Set your CMOS clock right then
just click on the button that say's "Obtain registry key online" fill
up the form(two fields are only required) then the registry key would
show up to your screen then just copy and paste it. then everything
works fine. sorry I can't post any images I still need to earn more points...
Background: Visual Studio 2012 Pro installed by Administrator account.
As "Joe User" (member of Win 7 Users group, but NOT Adminstrators) I got the error message.
On reading this forum I concluded this is a generic error message.
Steps to fix:
As an adminstrator, open HK_CLASSES_ROOT.
Open context menu on the Licenses subkey
Select Permissions...
Set Full Control for all users.
Now log on as "Joe" again.
Voila!
Next, as Administrator change the permission on HKCR/Licenses back to read only for Users.
Two hints for developers.
If you can develop and run an application as an ordinary user, then presumably your poor
clients don't need admin rights to run it either.
Don't leak security information in "helpful" error messages. Microsloth are probably following their own advise and giving a vague and unhelpful error message here.
I have no idea why changing the permission to FC then back again to the original setting worked. I can only assume the Visual Studio writes something to that key the first time it runs.
While none of the above solution worked for me (else than running the application with an other username),Renaming the application folder in %appdata% fixed the porblem for me.
"C:\Users...\AppData\Roaming\Microsoft\MS Project"
I had this issue while installing dynamic ax setup in VM, while installing it was showing me to 'licence is not valid, Reinstall visual studio shell 2010 version', so i uninstalled the visual studio shell 2010 version and its following component and tried to install again the AX admin it worked.
I'm having this problem with Visual Studio 2015 installed.
ramonsantana over at forum.unity3d.com had the solution for me: https://forum.unity3d.com/threads/if-anyone-is-having-visual-studio-shell-2010-invalid-license-data-reinstall-is-required.298824/
Copied here for reference
Use regedit go to HKEY_CLASSES_ROOT and look for Visual Studio.DTE
Since i have Visual Studio 2015 CTP installed i have 3 DTE, one is
VisualStudio.DTE, the other Visual StudioDTE.10.0 and
VisualStudio.DTE.14.0 Go to VisualStudio.DTE.14.0 ( or whatever
version of Visual studio you have installed) and click CLSID.
Copy the
Default (Double click Default and Copy the key inside), now go back to
Visua Studio.DTE and double click the Default there and paste the key
you just copied.
Almost there
On VisualStudio.DTE go to CurVer and
double click the key there to Edit it. Change the 10.0 in the end to
12.0 or 13.0 or 14.0, depending on what version of Visual Studio you have and you are done.
Installing SQL server data tools for visual studio 2010 did it for me! SSDT has an VS2010 IDE along with it, which overwrites the required registry entries.
You can find SSDT here.
My problem:
VS works fine, but when I create new Solution Setup and Deployment it make Setup file but when I run this Setup file, it say: "Invalid license data. Reinstall is required."
subinacl do not work.
My PC:
OS: Windows 7 64bit.
Visual Studio 2012
My way:
Close Visual Studio
Run regedit.
Pull down HKEY_CLASSES_ROOT
Looking for Licenses
Right click on Licenses -> click Permissions... -> click Advanced -> click User you want edit -> click Edit -> choose This key and subkey -> check all Allow: Full Control, Query Value, SetValue, Create Subkey, Enumerate Subkeys, Notyfy, Create Link, Delete, Write DAC, Write Owner, Read Control... -> check Apply these permissions to objects... -> click OK -> click OK -> click OK -> Close Registry Edit
Start VS
Hope this help
This was my problem with my Visual Basic Net 2005.
This is how I got it solved:
Click start :-> type run (Or press win+r)
Type regedit
Click HKEY_CLASSES_ROOT
Click Licenses
Double click (Default)
Clear all text written in Value data field
Press Ok
Run again Microsoft visual studio
Believe it or not, I have found cases where this problem occurred due to a build error when the build error was due to an error in xcopy in the pre-build events.
We had this problem at a colleges computer, and after trying everything here we set to forget it and fix the error from xcopy. When this was fixed the Visual Studio 2010 shell error stopped popping up, for some reason.