Comments
4 comments
-
Hi @tomslickers
This looks like a question that one of Support engineers will need to investigate for you.
If you've a got support contract, please send us a ticket. Provide as much information as you can - screenshots of any errors, log files etc – so we can help you as fast as possible.
-
This turned out to be missing DLLs on the developer's machine. We worked around this by installing Visual Studio 2013.
-
This commit doesn't meet the server's policy requirements, or the policy isn't configured on your machine. The server returned the following:Internal error in Changeset Comments Policy. Error loading the Changeset Comments Policy policy (The policy assembly 'Microsoft.TeamFoundation.PowerTools.CheckinPolicies.ChangesetComments, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not registered.). Installation instructions:
not able to commit change into my TFS -
This commit doesn't meet the server's policy requirements, or the policy isn't configured on your machine. The server returned the following:Internal error in Changeset Comments Policy. Error loading the Changeset Comments Policy policy (The policy assembly 'Microsoft.TeamFoundation.PowerTools.CheckinPolicies.ChangesetComments, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not registered.). Installation instructions:
not able to commit change into my TFS
Add comment
Please sign in to leave a comment.
This commit doesn't meet the server's policy requirements, or the policy isn't configured on your machine. The server returned the following: Internal error in Changeset comments policy...
I confirmed that a comment is being provided for the commit.
We are using the latest version of SQL Source Control along with SSMS 2017.