Source Control Disabled

Source Control Disabled

• Amritha Chand

  You shouldn't need to add users to the service users group. That group is reserved for the identities that run the services.

  How do you have the groups and permissions set up for the Team Project(s)

  The information at this link discusses administering source control permissions: http://msdn2.microsoft.com/en-us/library/ms181455(VS.80).aspx

  Please reply back with more details about your group(s), permissions if the problem persists.

  
  

• Rassol

  Amanda,

  The privilege AdminProjectRights is a discrete permission managed by the Source Control component of Team Foundation. You can view the permissions associated with the two groups with this command: tf perm /group:groupName $/teamProjectName

  You can also use the tf perm command and include a permission by specifying /allow:permissionName[,perm[...]]

  -jeff

  
  

• George Birbilis

  In my case it was indeed the fact that the user had files checked out on the machine on which I was trying to modify source control settings. As soon as I made sure that no files were checked out on the machine, the source control context menu re-appeared. Thanks for the tip. I would never have figured that one out.
  

• nikos_22

  I too am having problems. I have 2 clients on different machines connected (as Team Foundation Server Administrators) to a Team Project using the same user credentials. One one machine I have the 'Source Control...' context menu item when I select 'Team Project Settings', and on the other I do *not*, even though I am connecting to the server and the project with the same credentials. There does not appear to be any relationship between the order these client machines connect - one machine always shows the problem and the other does not. The only difference I can see is that the client that 'works' has Team Suite installed and the one that does not has Team Developer installed (obviously both with Team Explorer installed.)
  
  In my case, I can use the following:
  
  tf configure $/"my project name" /server:server_name
  
  ...to manage checkin policy and I do *not* get the error described in the previous post when managing policy this way; however, there is no way for me on the machine showing the problem to get access to the Source Control configuration dialog for the Team Project in question using the Team Explorer UI.
  
  I have also compared the permissions on both machines (by comparing the output of the 'tf perm $"my project name" /server:server_name' run on each machine). They are IDENTICAL.
  
  What can I check to fix this It is really frustrating.
  
  

• syhzaidi

  I am having the same issue. I am in the Project Administrators group for the project, but the Source Control option under Team Project Settings is grayed out. All other Team Project Settings are active.

  There are multiple projects on the same Team Foundation Server, and Source Control is active for the other projects.
  

  I can open the settings by running the following from the command line:
  tf configure $/project /server:server_name
  

  The source control settings window opens.  When I add a check-in policy and click OK, I get the following error message:
  System.Web.Services.Protocols.SoapException: TF14098: Access denied: User username needs Admin.ProjectRightsPermission(s) for $/project. at Microsoft.TeamFoundation.VersionControl.Server.Repository.CreateAnnotation(String AnnotationName, String AnnotatedItem, Int32 Version, String AnnotationValue, String Comment, Boolean Overwrite)
  
  The username executing this command is a member of the [SERVER]\Team Foundation Administrators group and the [project]\Project Administrators group.
  

  How do I give this user the permissions needed to set check-in policies
  

  
  

• Paula M

  Could the problem exist because there are users with files checked out That is the only difference I can see between the project that allows me to change the source control settings and the project that does not.

  I checked the group permissions, and AdminProjectRights is allowed for both groups. I also added this permission explicitly to the user (it should have been inherited from the group), and I still receive the same error message.

  >tf perm /group:"Team Foundation Administrators" $/"my project"

  =============================================================================
  Server item: $/my project (Inherit: Yes)
  Identity: [SERVER]\Team Foundation Administrators
  Allow:
  Deny:
  Allow (Inherited): Read, PendChange, Checkin, Label, Lock, ReviseOther,
  UnlockOther, UndoOther, LabelOther, AdminProjectRights,
  CheckinOther
  Deny (Inherited):

  >tf perm /group:"[my project]\Project Administrators" $/"my project"
  ===============================================================================
  Server item: $/my project (Inherit: Yes)
  Identity: [my project]\Project Administrators
  Allow: Read, PendChange, Checkin, Label, Lock, ReviseOther,
  UnlockOther, UndoOther, LabelOther, AdminProjectRights,
  CheckinOther
  Deny:
  Allow (Inherited):
  Deny (Inherited):

  
  

• Tony Sperling

  I am having same issue but I can see SCC under team project from a different client so it seems like I have correct permission.

  I tried it after deleting the cache and that too did not help.

  Any idea, why

  
  

• Gunnar Adler

  Sorry for the delay. I am still having this issue.
  
  I tried to replicate on another project, and having files checked out does not seem to be my problem. I'm still unable to change the options for one of my projects.
  
  

• David Searles

  I've found that the TFSServer account has access to this option, the only differencne I can see with it's rights and mine is that it is a service account. How do I add users to the service users group
  
• Source Control Disabled