Comment required and Azure DevOps 2019 checking causes exception

BlueBSH

Our environment we are working with SSMS 18.8, SQL Source Control 17.2.16, and Azure DevOps 2019 (local server install) and Visual Studio 2019 16.8.5. We require comments on code checkin, and every time we try to check in code SQL Source control comes back with  

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: 

I tried changing the RedGate_SQLSourceControl_Engine_EngineOptions.xml file to say

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<!---->

<EngineOptions version="3" type="EngineOptions">

  <TeamFoundationServerDllOverride>TfsExtendedClient</TeamFoundationServerDllOverride>

</EngineOptions>

with no luck, same exception. I also can not find any references in the registry under Computer\HKEY_USERS\S-1-5-21-527237240-884357618-1801674531-3126\SOFTWARE\Microsoft\VisualStudio\16.0\TeamFoundation\SourceControl for the Check in policy libraries like you say to look for, same with the 15.0, 14.0, and 10.0 nodes under visualstudio.. Should those of been there for DevOps 2019?

BlueBSH

I found the  <IgnoreTfsPolicies>True</IgnoreTfsPolicies> tag and this solves this issue, but what do you do it you still do want to force comments on a check-in, is it even possible with devops and sql compare?

David_D

Hello @BlueBSH,

Thanks for reaching out and sharing the details.

By using <IgnoreTfsPolicies>True</IgnoreTfsPolicies>, you will be essentially ignoring all TFS policies. As for <TeamFoundationServerDllOverride>TfsExtendedClient</TeamFoundationServerDllOverride>, that will connect without using Team Explorer.

That error you are receiving is related to a policy set up by your team's server administrator to make sure commits meet requirements they specify. Commits that don't meet the policy requirements are rejected by the server. Hence, why you are receiving "This commit doesn't meet the server's policy requirements, or the policy isn't configured on your machine."

There can be multiple causes of this error, please refer to this page to try each of the options. I would recommend reaching out to your team's server admin to confirm what policies are set.
https://documentation.red-gate.com/soc/troubleshooting/error-messages/this-commit-doesn-t-meet-the-server-s-policy-requirements-or-the-policy-isn-t-configured-on-your-machine

Kind regards,
David Dang
Product Support Engineer