Sql Source Control v7.1 fails Commit action on SSMS 18.8
gholbrook_icumed
Posts: 3 New member
Sql Src Control v7.1.29.11028
SSMS 18.8 v15.0.18369.0
VS 2019 Pro v16.8.4
Sql Server v15.0.4073.23 HADR Enabled
When I attempt to Commit I get this error: policy assembly Microsoft.TeamFoundation.VersionControl.Controls is not registered
Azure DevOps Server 2019 Version Dev17.M153.5
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 Work Items. Error loading the Work Items policy (The policy assembly 'Microsoft.TeamFoundation.VersionControl.Controls, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not registered.). Installation instructions:
I have tried the update to set the RedGate_SQLSourceControl_Engine_EngineOptions.xml file by inserting this:
<TeamFoundationServerDllOverride>TfsExtendedClient</TeamFoundationServerDllOverride>
I still get the same error.
And yes, #IgnorePolicies works, but then my User Stories will not get updated, right?
So what do I do?
I have tried the update to set the RedGate_SQLSourceControl_Engine_EngineOptions.xml file by inserting this:
<TeamFoundationServerDllOverride>TfsExtendedClient</TeamFoundationServerDllOverride>
I still get the same error.
And yes, #IgnorePolicies works, but then my User Stories will not get updated, right?
So what do I do?
Tagged:
Answers
I've come across this issue a few times and the solution is installing the TFS powertools, therefore you will need to install VS 2015.
Here's the installer for that: https://marketplace.visualstudio.com/items?itemName=TFSPowerToolsTeam.MicrosoftVisualStudioTeamFoundationServer2015Power
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?
SQL Server Management Studio 19.3.4.0
SQL Source Control Version 7.7.10.18663
Error:
I will get the same Error while commiting some databasechanges. Installing the Microsoft Visual Studio Team Foundation Server 2015 Power Tools doesn't help me. Are there any other suggestions to fix the error?
Thanks!
Steffen