When I go to my project properties page under the Signing tab and click "Create Test Certificate" I get the error "Object already exists. (Exception from HRESULT:0x8009000F)"
I've also opened past projects that I've created certificates for and tried to create new ones but I get the same error.
I had no problems creating certificates in the past. I am using Windows 7 and am running VS 2012 as administrator.
Anybody encounter this problem before?
John
this solved the issue for me HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid This key should ideally have the GUID of the machine without curly braces, so {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} becomes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Related
I have used the TFS to Excel functionality for several years. Last Friday it suddenly stopped working. I get the error TF84021 Can't create the work item list. If I try again it will spin and then bring up the same error. This usually happens 2 or 3 times then Excel will open as a read-only which removes the link to TFS. I have tried to configure the server connection and get error TF400324. Services not available from server. The underlying connection was closed.
This is impacting a small group of people with the same job function (Scrum Masters and BAs). Management and developers can use it just fine.
My help desk remoted into my machine and tried it with his creds and it didn't work. We ran it through Fiddler and the log showed an error but it didn't have any information.
I am using TFS2017 Version 15.117.27414.0 which I believe is update 3, Visual Studio 2017 and Excel 2016. As well as ADO in the cloud (not on prem).
I have gone into Excel to verify the com add-in is present and checked. I have reinstalled the add-in just in case it was corrupted. I have tried to remove my TFS server and re-add although I knew that couldn't be the problem as it occurs on ADO as well.
I'm at a loss. Any thoughts as to what to try next?
We are using TFS2010 (for source control only), and until recently everyone was using VS2010. Our developers just installed VS2012.
Pulling down code works fine in Visual Studio. When you go to "Pending Changes" in Team Explorer, we are seeing TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have been added to Team Foundation Server., twice, at the top. We can still check-in code from VS - seems this error is ignored.
However, we are unable to shelve changes - when you attempt to shelve, the same error comes up in a popup, and the shelveset is not saved.
We can shelve using the command prompt (tf shelve), and can still shelve using VS2010, so it doesn't seem to be a permission issue. Also, the TFS administrator is not seeing the error message, and can shelve from VS2012 with no error.
Any thoughts as to what could be causing VS to error out here? We've tried clearing out the TFS cache, creating a new workspace, and gone over every option we could find in Visual Studio.
I had the same issue. Tried many different stuff from web sites and non of them helped. Finally find the solution for this. Follow these to make it work:
1) Create temporary AD User
2) You will need to transfer all old user configuration into a new temporary account. If you are OK with using the temporary account you may just keep it and get rid of old account. Go into the machine that TFS is installed and Run this command: TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:oldAccount /toaccount:temporaryAccount
(TFSConfig is in C:\Program Files\Microsoft Team Foundation Server XX.0\Tools\)
3) If you don't want to use temporary account you will need to convert from temp account to your old account. To do that run the same command wit changing the user names:
TFSConfig identities /change /fromdomain:mydomain /todomain:mydomain /account:temporaryAccount /toaccount:oldAccount
That's all you need to do.
Up until yesterday, my connection to Team Foundation Service was working perfectly.
A separate requirement caused me yesterday to rename my computer. After that, there were some errors about the workspace which I was able to fix with the TF command, but I can't find anything about this new error, which arose after I renamed the workspace:
Please note that the blacked-out email addresses are all three identical.
I have no idea how to "specify one of the following workspace specs" from a MessageBox! Any ideas?
TFS for years has been among the worst user experiences I've ever seen.
For me it helped to just sign out from TFS via the "Configure Team Projects" window, and then log in again.
Connect to TFS DB and refer DefaultCollection db.
[dbo].[tbl_Workspace] this table is used to store workspace info
[tbl_WorkspaceMapping] this table is used to store mapping created above.
[dbo].[tbl_WorkingFolder] this table is used to store working folder mapping.
Exit your tfs client and perform below steps.
delete your workspaces causing issue from table [dbo].[tbl_Workspace] and [tbl_WorkspaceMapping] and start accessing your tfs client by configuring new workspace.
I had to guess at a "tf" command line argument set, but, I found that the workspace carried the same name as the computer, after renaming both. So I did this to myself.
After using "tf" to change the workspace name from "WIN8DEV" to "WIN8DEVWORKSPACE" this particular problem vanished.
I am in need of help getting Local Development STS running. I just started with MSDN tutorials and got stuck when trying to build WCF service using WIF. So far I did following:
Installed "Identity and Access Tools" in my Visual Studio 2012
Created new WCF Service project in new solution
Right clicked projects name and selected "Identity and access..."
Selected "Use the Local Development STS" option on first tab and changed token
type to "SAML 2.0" on "Local Development STS" tab
Clicked "Ok"
I end up with following that informs me about problems with certificate:
I verified that the file is there physically.
I verified access to it - System, Administrators and my user have full access to it (only last option is unchecked)
I tried to install the certificate manually, but it is protected with password and I cant find it anywhere
I tried to toy around with "Identity and Access..." wizard
I tried to google the answer
I tried to check if I have certificate like that installed, there are tree Personal certificates in my Local Machine store, but I have no idea how to check their subject or whatever else
So far I wasn't successful. Could anyone advise how to fix the situation, so I can be sure I have proper certificate installed, I would be eternally grateful.
Erchi
Are you using the .NET 4.5 tutorials - WIF Code Sample Index?
To check the subject:
Start / Run / mmc
File / Add - Remove Snap In
Certificates - Add.
My User Account - Finish - OK
Expand the tree as required - double click on certificate - Details.
During web application creating i got below popup message:
"Visual studio does not have permissions to read the template information from the registry. this is often caused by registry permission problem."
Any one have any solution?
Please help me. i wana to see Visual Studio new features.
Thanks
this might be quite late as an answer, but I excpierienced the same problem and I found the solution on a msdn page : here is the original solution message :
I came across this issue with Visual Studio 2010 and Windows 7. I did not find this problems source as of yet but, I have found many Visual Studio users encountering it. I tried Michael's solution to this problem and it did more damage then anything else. It even went as far as to make Visual studio to boot into "Shell mode" and tell me the registration was not valid.
Using System Restore I rolled back the changes made by the subinacl tool and Michaels script (it probably was not meant for Windows 7, causing the errors in the first place) .
being a long time visual studio user and a pretty good trouble shooter, I knew the subinacl was the proper tool to correct the problem, but the script was incorrect for my perticular setup. I adjusted the script as follows: (this is a batch script)
cd /d "%programfiles% (x86)\Windows Resource Kits\Tools"
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /setowner=domain\user
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /grant=everyone=f
/grant=administrators=f /grant=system=f
pause
I tried to include the "setowner" command with the grant commands (on the same line) but it would throw errors all the time.
This script fixed MY "Requested registry access is not allowed" with Windows 7 and Visual Studio 2010.
if you want to try this script: Follow Michael's instructions, but use the script provided in this post and replace the "domain\user" with the proper credentials. You may also need to change the Path of Windows Resource Kits if you installed it in a diffrnet place or are not using a 64 bit OS. Before using this script please backup your registry.
I hope that that helped!
*the original web page was : http://social.msdn.microsoft.com/Forums/en-US/c273b0e1-7f46-4065-afaf-4edf285d2531/vista-wpfapplication-requested-registry-access-is-not-allowed
I had this problem too. Followed the post by user2698666 without success. Stuck Process Monitor on it and found there were more registry entries causing a problem called WDExpress. Thought I'd post my fix incase anyone else has same problem:
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /setowner=domain\user
subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /grant=everyone=f /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT\WDExpress* /setowner=domain\user
subinacl /subkeyreg HKEY_CLASSES_ROOT\WDExpress* /grant=everyone=f /grant=administrators=f /grant=system=f
I had the problem with Visual Studio 13, where i wanted to add a webtest project for my newly created solution.
Tried the above trics to set ACL but it didn't work.
Finally used the Procmon.exe to locate what visual studio was doing (Include only process name devenv.exe) and look for result Access Denied. It will tell you what registry key is not accessible.
In my case it was the regkey HKCR.webtest (HKEY_CLASSES_ROOT.webtest) that caused the problem. Taking ownership and assigning acces to this solved my problem.
I do not know how the root cause of the problem.
The above didnt work for me as I kept being denied in regedit even though i was admin.
I found this on another site:
psexec -i -d -s c:\windows\regedit.exe
psexec is available from Microsoft here
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
This gave me full registry access. I tried to give admin owner to specific keys like above but VS 2012 express was still throwing that registry permission error. So I finally just added Administrator to the permission list of the entire HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ directory in regedit. Then gave admins full control.
This worked. I can now create a project without that infernal error!
This issue has nothing to do with permissions in the context discussed. The issue is caused by an incorrect path to the template files in the registry due to sloppy installation program testing by Microsoft. The incorrect path throws an error when a user tries to start a new project and, true to Microsoft style, displays a generic and meaningless error message about permissions.
Here's the issue specifically. In some machines (assuming C: is the primary drive and user1 is the user's login name and version 2013) the location of the template files is C:\users\user1\my documents\visual studio 2013\projects. Unfortunately, the installation path written by the installer in the registry is C:\users\user1\documents\visual studio 2013\projects. So, it's pointing to \documents while the correct location is \my documents. To be sure, look where your visual studio 2013\projects folder is located - either documents or my documents - and change the registry key to the correct location.
For my example the key is at HKEY_CURRENT_USER\software\Microsoft\VisualStudio\12.0\NewProjectDialog\MRUSettingsLocalProjectLocationEntries the path is located in the Value0 entry. Check it and change to make it point to exactly where your project folder is.
Lars Meldgard's use of ProcMon was a good tip and helped me. I just wanted to include a picture of what an access denied looks like in ProcMon. I had to do it one registry key at a time--this wasn't the only one. It was very cumbersome and slow, but I was able to knock them off one by one and give full rights on each one. (That part is a hassle too, because I had to take ownership, then close regedit, then go back in so I could set the permissions; you can't do it all in one fell swoop.)