I restarted IIS on our TFS server, and ever since then I haven't been able to access my workspace.
Regardless of what I do, it continually creates a workspace owned by a service account, and not my corporate account.
A couple days ago I had opened SSMS 2008 with "Run as different user" and used that service account. That's the only way I can think that it got in the picture.
So if I run tf workspaces /owner:* I see two workspaces, one owned by me, and one owned by the service.
When I open VS2010, it loads the workspace owned by the service account, and I can't view the other workspaces. Running tf /delete on the wrong one deletes it and running tf /remove:* clears my cache, but when I open VS2010, it is created again.
I tried running VS2010 with "Run as different user" and used my credentials, with no luck.
Anyone have any ideas as to how to get my workspace back??
You can change the owner of a workspace using the /newowner flag to the tf workspace command. For example:
tf workspace /collection:http://server:8080/DefaultCollection workspaceName;oldOwner /newowner:newOwner
This should work as a stopgap measure to allow your old workspace to be owned by the service account. To update this, make sure that you do not have credentials saved for your TFS server in Control Panel -> Credential Manager. These credentials will always override your logged in user credentials or anything specified to runas.
So, not an answer, but a workaround.
I set the actual workspace to public, and now I can at least load it.
I have no idea why VS/TFS thinks I am a service account.
EDIT: Turns out I had the service account credentials for the tfs server saved in Credential Manager. Removing the credentials and restarting VS2010 resolved the issue.
Related
I was trying to check in some changes to tfs, then I got a prompt asking me for my credentials. My password seems not to work anymore (I don't know why). Since the tfs is for my own personal use and installed on my local machine, I'd just to start over, i.e. created a new instance of the source control.
First of all, is there a way, I can reset the password? If not, how do I create an new instance of tfs on my machine?
Thanks for helping.
Clean the Cache folder under: C:\Users\username\AppData\Local\Microsoft\Team Foundation\x.0\Cache.
Go to Control Panel--Credential Manager, remove all credentials.
Go to Team Explorer--Manage Connections--Connect to Team Project, click Servers, and remove your TFS, then re-add it.
I'm using tfs and when I try to request a code review I get the error in the image bellow. I am able to perform check-ins and shelves.
The other users from the team that I am in are able to request a code review from the same user and in the same path that I am using.
If all of your team users except you works well. I was wondering if it is related to your VS.
For this issue, you can try below methods to see if you can fix it:
Repair your VS
Try to delete TFS cache by going into default C:\ {User Profile
Folder}\AppData\Local\Microsoft\Team Foundation\x.0\Cache and VS
cache in Appdata folder.
Try to use your account on another computer or use another account
on your computer to request a code review.(Make sure your account of
permissions without any problem)
We have got an implementation of TFS 2013 and the Visual Studio is configured to work with TFS 2013. Until recently when the developers are working on separate project everything went on smoothly.
Now when multiple developers are working on a single project, there is a problem of Multiple Check outs for the same file. The fact is Visual Studio is configured to work with Local Workspaces and hence the Multiple Checkouts. I tried to change the workspace from Local to Server by following the instructions from this post.
However, the developers now face an error (TF14098: Access Denied: User username needs PendChange, Lock permission(s) for $/myproject/file.aspx) when trying to checkout.
Itreid searching for this error on the internet but could not resolve this nor could I find any resolution for this.
Help is very much awaited and appreciated on this.
You are having trouble with permissions. Check if any the group you are the member is denied for PendingChange and lock or its directly denied for you. Note in TFS permissions, Deny always takes precedence. You must make sure your users and all the groups your users belong to have the allow permissions of PendingChange and lock in the project.
You can use the command Tf perm to check what are the security permissions for this project . Navigate to the project location and enter it. This will basically tell you list of all users/groups with their permission. Then change the security in web access.
I just reinstalled IIS7.5 after a lot of ugly messing around. I admittedly had no idea what I was doing.
I finally was able to renamed my windows\system32\inetsrv folder so that when I reinstalled IIS, I would get the default settings.
I took a wild guess at running this and it got my site running: aspnet_regiis.exe -i
Now I just can't Publish from Visual studio to any site under wwwroot.
for example, I get the error: Unable to create the Web site location 'c:\inetpub\wwwroot\WebApplication5'. Access is denied.
My work around is to Publish elsewhere and then copy the code there--and that works.
Goodness knows what else I broke in the process, but my web site appears to work except that I can't use the Publish functionality in VS2010 because of the Access Denied error.
Do I have to grant some ASPNET built in user rights to this folder?
Here's a snapshot of the rights on my wwwroot folder:
If you are able to run your application after copying from a different location, the problem is not with IIS or the worker process; it would most likely be a permissions problem with your windows user and process (in this case, visual studio).
Try running visual studio as an administrator (if you are not a local administrator of the machine). If that works, you can give full access to your inetpub folder for your user.
Late to this thread but I fixed this issue by going to:
c:\inetpub\wwwroot\myApplication > right click > properties > security > select Users(myMachine\Users) change access to full
Hopefully this thread is still alive. I had this problem and here is how I resolved it:
Try opening a file on the remote site from Visual Studio by File>Open File...
If you don't have access you will be challenged with Windows Sign in. Here you can enter your credentials for accessing the REMOTE site. Once you enter the credentials and the file is successfully opened you will be able to publish. Occassionally (I don't know why) the credentials will become invalid at which time all you have to do is open a file and reenter them.
Another solution is to create a share to your local c:\inetpub\wwwroot dir (give yourself read/write permissions) and publish to the share like so: \\mypc\wwwroot\mywebsite. It helped me get around the annoying UAC security without disabling it.
Web Deploy is likely to execute under the user name Local Service. Check the permissions for this user.
I'm having a similar problem
Access to the path 'C:\Sources\x\bin\Debug\netcoreapp2.1\publish' is denied.
Unable to create the Web site location Access is denied.
Access is denied because a subfolder is open in file explorer and locked by file explorer.
We have a an ASP NET MVC website solution which only one out of three devs on the team is able to publish to the live server. When I, and another colleague, attempt to publish the site from VS 2010, the output window will display an error:
Unable to create the Web site
'\blah'. The path '\blah' does not
exist or you do not have access. The
specified path is invalid.
This points to a logon issue which my account, but the developer who can publish the site is a member of all the same user groups as me. As a long-shot, we gave Everyone full access to the folder, but this did not resolve the problem.
Can anyone suggest a more detailed way to try and figure out why we cannot publish the site? There must be a permission set somewhere that is allowing my colleague to publish the site from Visual Studio.
I had this problem and racked my brain trying to resolve it so I wouldn't have to copy the publish files to a remote server manually. I spent a great deal of time actively trying to get this to work.
Here's how I solved the problem: I went to File>Open in Visual Studio 2010 Express and navigated to the remote server (\\255.255.255.255\folder1\folder2\folder3 and so on). Right away I was challenged for a User Name an Password. I entered the credentials for the REMOTE server, checked the box to 'Remember my credentials'. I immediately tried to publish and voilá - it worked like a charm.
I hope this saves a lot of people a lot of time.
I had this issue - certain members of our team were able to publish directly from VS2010, whereas for some reason I was always getting permission denied errors, even though we were all able to connect to the server we were trying to deploy to. I fixed it in the following way:
Go to "Server Explorer".
Right click "Servers" and go to "Add server..."
Type in the name of the server you are trying to connect to, and then click on "Connect using a different user name..." - put the credentials for logging into the server in here.
Click OK and wait for it to add the server.
Now try and publish to that server and it should be ok...
Not sure why I needed to do this and others were able to deploy without adding the server in this way... remains unexplained.
According to the comments below:
You may need to restart Visual Studio in order for this to take effect.
This should also work for newer versions of Visual Studio
Faced the same problem today. In my situation I had to close VS2010 and open it NOT as an admin and it worked without any problems.
This got me for a long time...Go to Project - Properties and select the Package/Publish Web tab. Under the header "Web Deployment Package Settings", there's a ellipsis button that you can use to map to the location you want to publish. You will be asked for your credentials during that process.
Are you using web deploy (right click and choose Publish)?
Have you tried copying the ProjectName.Publish.xml file from the one machine where you can publish to the other two machines? The login credentials for publishing are saved in this file.
In IIS can you check to see that all users/groups are listed under Management Service Delegation in IIS Manager? It is listed under the Server node in IIS. Alternatively you can give all administrators access by clicking on Edit Features from the side-menu and checking Allow Administrators to bypass rules.
You could also check under IIS Manager Permissions for the individual site to see if the person that can publish is listed under there and you are not.
I just recently setup MSDeploy access on my server and found the following two tutorials helpful:
http://william.jerla.me/post/2010/03/20/Configuring-MSDeploy-in-IIS-7.aspx
http://code-inside.de/blog-in/2011/04/03/howto-setup-of-webdeploy-msdeploy/
I have also found that mapping a drive to the UNC location can be a work around.
#soupy1976's solution has also worked for me.
I can not explain why one day it will work and one day it won't
Frustrating....