I am having problems getting the team alerts to work in TFS 2010.
Under "Team > Project Alerts", I have checked the box to send both myself and a colleague an email upon a completed build. I know I have entered the correct email addresses, correct syntax as far as separating the emails, yet neither I nor my colleague receive any emails when the build is complete.
So far, I haven't found anything online regarding troubleshooting this issue. I was wondering if anyone has encountered the same problem or otherwise knows of a solution to this problem.
Usually this boils down to a configuration problem within the TFS setup.
If you have access to the tfs server, run the TFS Administration Console.
If you click on TFS / Application Tier on the left, you'll see the Application Tier settings come up. Scroll down to the Email Alert Settings.
Make sure it's enabled and has the correct configuration for sending messages.
Related
I have a problem with the Source Control settings of one of my project collections on the Team Foundation Server.
I need multiple file checkouts not possible. I know where the configuration is and what I have to change:
1-The work area of each team to establish it on the server
2-change the configuration of the team project collection to uncheck the "Enable asynchronous checkout of server workspaces" box.
3-The configuration of each project in the collection to disable multiple check-out.
To be able to do step 3 I need step 2, and this is where I have the problem, even if I put everything correctly.
At the moment of OK it seems that everything has gone well but if I go back into the screen everything continues as it was until now and nothing has changed.
I have other collections of projects where I have been able to configure this correctly, something must be escaping me and I cannot find the solution
I am using the VS2019 and the 2013 version of the Team Foundation Server
Thanks for helping, regards!
You could check whether the workspace you are using is a Local Workspace or Server Workspace:
https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/decide-between-using-local-server-workspace?view=azure-devops
If you use Server workspace, please add some screenshots in your original post to describe your issue.
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 are trying to access Test plans using the Web interface from Test Manager 2013 and we keep getting this message.
The test plan with id 328 does not exist or it’s area path is not owned by the default project team.
I read in another post that a fix would be to open the ROOT Test plan in Visual Studio and save it.
I don't know how to do that, can someone please let me know how or point me to somewhere I can learn on how to do that.
I haven't had this problem myself but what another post you mentioned means is following:
Go to Visual Studio
Search for a Work Item with ID from the error message you are getting (in your case 328)
Open this Work Item (it should be a Test Plan) in Visual Studio and save it
According to the post Cannot view any Test Suites and Test Cases in TFS 2013 Web Access despite being able to access them in MTM this should solve your problem.
Update:
What do you see if you just open TFS Web access in browser?
Can you see this "Test" part?
Can you see your Test Plans in the list of test plans of selected *Team Project"?
If you can't see your Test Plans in the list change the Team Project (just click on this and select another one)
Further update:
Please check this article describing new permissions that was added with TFS 2013 Update3: Plan Manual Tests using Team Web Access
You still access test plans and suites using either the Team Web Access or Microsoft Test Manager. But make sure that you set up access based on permissions for the area path.
We didn't have this kind of issues after upgrade to TFS 2013 Update 3 so I can't help you much...
If you don't find nothing helpful in article above consider to contact Microsoft since it seems to be an Upgrade issue.
I think this is a bug in the web access portion of TFS.
If the test plan's area includes a child node, you will get the error. For example: myArea/myChildArea. If you remove the child area, it works in web access. (Test Manager works in all cases.) My guess is that the web access logic is comparing the entire area path name as opposed to just looking at the top node of the area path.
(Problem occurs in TFS 2015)
I had similar problem and i solved it using following option.
Go to Areas on web tool and enable checkbox for sub-areas which selected under test plan, it is recommended not doing it on root areas.
I changed from running Use Visual Studio Development Server to Local IIS Web Server becasue I read it would create the virtual directories properly - it did not - once I navigate out of the account area I get
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Requested URL
https://localhost:443/xxx/Index
Physical Path
C:\inetpub\wwwroot\xxx\Index
I have been googling and trying to get it to work, but can not and can no longer debug - Now I am trying to change it back and it keeps starting in Local IIS Web. I have HOSED myself and don't know where to go from here.
Thank you
In terms of getting back to using the VS web server you should just need to:
Right click on the web project in VS
Selection properties
Go to the web tab
Select "use visual studio web server" radio button
For the sake of not leaving questions unanswered, I tried all of the suggestions above, and many more, and got nowhere. I was in an early phase at the time, and I had to move on, so I ended up creating a new solution, and porting things over. Not the best idea, but I had to go forward, and I had taken enough time. It is still living on my machine, and I plan to go back and figure it out at some point. Hopefully, I'll have more understanding and will be able to post what I did wrong so someone else can save some time. Thanks all for attempting.
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....