locked
Changing Syncing repository? RRS feed

  • Question

  • Hi

    I have done a "move/upgrade" from TFS2010 to a new TFS2015 server.
    It seems like my moved collection still points to the old "OLDtfs server"?

    I would like to verify the "NEWtfs server" before shutting down the old, therefore i use different servernames.

    When i build Syncing repository points to the OLDtfs.

    Build output below.....

    ********************************

    Starting: Get sources
    Syncing repository: Projectname (TFVC)
    TF30063: You are not authorized to access http://OLDtfs:8080/tfs/Collectionname

    *******************************************************************

    Is it possible to change this url to "newTFS"? (i assume it wont be any risk with the in production "OLDtfs")

    Thanks for any input :)



    • Edited by Beachboy72 Thursday, February 25, 2016 12:21 AM
    Thursday, February 25, 2016 12:20 AM

Answers

  • Hi Beachboy72,

    Yes, I suppose that your collection still connect to the old build server(build controller and agent). That means your old TFS server may be used as a build server before.

    You could make your collection connect to the new build agent. In the build definition, choose the new build controller.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, February 29, 2016 1:41 AM
    Moderator

All replies

  • Hi Beachboy72,

    Thank you for posting here.

    You move and upgrade TFS from one server to another, the old TFS is still can be use. That means you have 2 TFS servers now.

    >>It seems like my moved collection still points to the old "OLDtfs server"?

    Do you mean that your new collection still use the old build server? Or I guess that you maybe still connect to the old collection on the old TFS server from Visual Studio or Web Access. If you want to use the new collection on the new TFS server, the TFS url: http://newTFS:8080/tfs/collectionname.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, February 25, 2016 5:12 AM
    Moderator
  • Thanks for answering :)

    Yes, i thing when building some path still points to the old server??

    In TFS Admin console all urls point to "NEWtfs", in Visual Studio 2015 i can connect to "NEWtsf" and see the ollection and projects.

    I have a green Agent icon, on my http://newtfs:8080/tfs  site.

    But when i start the build, i got the build output above? I could temper with acces rights so i can access the "OLDtfs2010" but i want it to access "Newtfs2015" and remove the old one when everything that i have copied/merged to my "NEWtfs2015" is working.

    Earlier in Visual Studio 2012 my web access pointed to "OLDtfs2010" before i changed the urls in admin console.

    I think i might have missed something because the build want to access the old "OLDtfs2010" url?


    Thursday, February 25, 2016 9:21 AM
  • what type of build system are you using - XAML based (old build system) or the new TFS Build vNext ?

    for XAML based build you need to check in Tfs Admin Console that you're not connection to old build agent.

    Remove the build agent & controllers and than re-add them - you need to check that they've removed from old TFS 2010 system as well.


    Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

    Thursday, February 25, 2016 7:48 PM
  • I use Visual studio build, have a build agent on another "New-TFS-Build" server, all green, and the agent starts the build. 

    Is it possible that this collection and project still points to the old server? 
    The webpage is http://NEWtfs:8080/tfs/projectname and the solution im building is something like $/projectname/Branch/Main/Solution.sln  BUT is it possibe that that the build is trying to find that url in the "OLDtfs" server, because there is the original that i copied to "NEWtfs2015 server" ?

    My main concern right now is the build to run all the way. When the build fails with
    TF30063: You are not authorized to access http://OLDtfs2010:8080/tfs/Projectname/
    My concern is not the fail, but that the url is not to http://NEWtfs2015:8080/tfs/Projectname

    Since its a copied/merged collection and project from "OLDtfs" i figured that somewhere in the solution or collection something still points towards "OLDtfs2010"?

    Thanks 

    Friday, February 26, 2016 1:59 AM
  • Hi Beachboy72,

    Yes, I suppose that your collection still connect to the old build server(build controller and agent). That means your old TFS server may be used as a build server before.

    You could make your collection connect to the new build agent. In the build definition, choose the new build controller.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, February 29, 2016 1:41 AM
    Moderator