locked
TFS Identity error after Split collection and Upgrade RRS feed

  • Question

  • Hi ,

    We're an getting  TFS Identity error (screenshot attached) during the upgrade process from TFS 2015 to TFS 2017 update1 . When we performed the split collection on TFS 2015, there we no errors and all the 3 collections were online. Now one of the duplicate collection (Legacy collection) is not letting us proceed with the TFS 2017 upgrade.

    I reran the failed job (Applypatch) from TFS Admin console but had no luck. Pleas elt me know how to proceed. Thanks

    Regards,

    Rahman.

    Tuesday, May 16, 2017 8:52 PM

All replies

  • Hi Rahman Syed,

    Thank you for posting here.

    Did you follow this instruction to split the team project collection(Rename, delete duplicate team project)?

    According to your screen-shot, you was using TFS2017 update1 RC2, according to the following link:

    https://blogs.msdn.microsoft.com/bharry/2017/02/13/tfs-2017-update-1-rc2/

    It is a known issue in TFS2017 update1 RC2, you could refer to the comment provided by Vladimir:

    We implemented a fix for the upgrade failure reported by  Kim Carlsen and  ckrueger. Sorry for the inconvenience that this issue have caused and thanks a lot for reporting it! Here are instructions on how to apply this fix, in case someone else will run into this issue:

    1) Download Microsoft.VisualStudio.Services.Notifications.Server.dll from the https://1drv.ms/f/s!AvqVNbyLcHq5h_sC0oXOKuQPyuivTw
    2) Execute net stop tfsjobagent from the elevated command prompt.
    3) Copy downloaded file to C:\Program Files\Microsoft Team Foundation Server 15.0\Application Tier\TFSJobAgent.
    4) Execute net start tfsjobagent from the elevated command prompt.
    5) Open Team Foundation Server Administration Console (C:\Program Files\Microsoft Team Foundation Server 15.0\Tools\TfsMgmt.exe)
    6) Open Application Tier > Team Project Collections page.
    7) Select Team Project collection that failed to upgrade.
    8) Click on Status tab.
    9) Select failed ApplyPatch job and click on Rerun Job link.

    You could try to fix the issue as Vladimir said, or download and use the latest version of TFS(TFS2017 update1) directly.

    Best Regards

    Limitxiao Gao


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, May 17, 2017 6:13 AM
    Moderator