locked
Get-TFSWorkspace throws the error "Unable to retrieve the registration information for 'ISCCProvider'." RRS feed

  • Question

  • In our build process I have to do some processing of directories in source control (rename, copy, add some SQL files, check in).  I use a powershell script to accomplish all of this.  It was working until we upgraded our TFS environment from TFS 2013 to 2015 Update 2.

    This is essentially the part that is failing:

    Add-PSSnapin Microsoft.TeamFoundation.PowerShell
    $tfsServer = "http://tfs.XXX.com:8080/tfs"
    $tfs = Get-TfsServer -name $tfsServer
    $workspace = Get-TfsWorkspace -Server $tfs -Computer STL7174D

    The last command returns the following error:

    Get-TfsWorkspace : Workspace(s) not found : Unable to retrieve the registration information for 'ISCCProvider'.
    At line:1 char:14
    + $workspace = Get-TfsWorkspace -Server $tfs -Computer STL7174D
    +              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Get-TfsWorkspace], Exception
        + FullyQualifiedErrorId : Get-TfsWorkspace,Microsoft.TeamFoundation.PowerTools.PowerShell.GetTfsWorkspaceCommand

    Any ideas?

    I'm using the TFS 2015 Powertools with Visual Studio 2015 Update 2 and TFS 2015 Update 2

    Thanks,

    Dave Rodecap

    Tuesday, April 5, 2016 6:49 PM

Answers

  • It turns out that we needed to add the collection to the end of our TFS URL:

    $tfsServer = "http://tfs.XXX.com:8080/tfs/DefaultCollection"

    This solved the problem and everything works as expected.

    Friday, April 8, 2016 3:15 PM

All replies

  • Hi Dave Rodecap,

    Thank you for posting here.

    I think you could use the following code to get the workspace, specify which workspace you want to get.

    Or refer to the code in this link, use another method to get workspace.

    https://blogs.msdn.microsoft.com/jmanning/2006/09/30/get-workspace-ps1-easier-access-to-that-wonderful-workspace-instance/

    $WorkSpace = Get-TfsWorkspace -Server $tfs -Owner $Owner -Name $Workspacename


    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.

    Wednesday, April 6, 2016 5:59 AM
    Moderator
  • It turns out that we needed to add the collection to the end of our TFS URL:

    $tfsServer = "http://tfs.XXX.com:8080/tfs/DefaultCollection"

    This solved the problem and everything works as expected.

    Friday, April 8, 2016 3:15 PM
  • Hi,

    Thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.

    All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.



    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, April 11, 2016 3:20 AM
    Moderator