A parameter cannot be found that matches parameter name 'AbortOnWarningLevel'

Sergio RSergio R Posts: 610 Rose Gold 5
in DLM Automation
If you started getting the following error:
A parameter cannot be found that matches parameter name 'AbortOnWarningLevel'
when using the DLM Automation VSTS add-on, this is caused by using a Private agent with an old incompatible version of DLM Automation installed locally.

There are 2 ways to resolve this issue:

1 - You can upgrade the local DLM Automation to version 2.1.0 or greater
(this is useful if for some reason you need to lock to a particular version of DLM Automation or otherwise need to have the application installed locally)

2 - You can uninstall the local DLM Automation - this will cause the VSTS add-on to get the latest version of DLM Automation

If you have any further issues please contact our support team at https://productsupport.red-gate.com/hc/en-us

Sergio
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
Tagged:
· Share on Twitter

Comments

  • way0utwestway0utwest Posts: 312 Rose Gold 1
    Quick note to verify this. I had this error and upgrading to DLM 1.2 fixed it.
    Editor, SQLServerCentral
    · Share on Twitter
  • Mike UMike U Posts: 316 Gold 1
    Update on this: we've now updated the VSTS Build and Release addons so that they will default to using the latest version of DLM Automation from the PowerShell Gallery, even if another version of DLM Automation is already installed on the local agent.

    If your build/release agents do not have internet access, they will fall back to trying to use the installed version of DLM Automation.

    If you need to force the addons to use a particular version of DLM Automation, you can set a specific version number to use in the task definition UI.
    Development Lead
    Redgate Software
    · Share on Twitter
  • CraigEddyCraigEddy Posts: 36 Bronze 3
    I'm having a similar issue, but with the following errors. This started today when our on-premise TFS 2018 server updated the DLM Automation Build extensions to 2.0.22:

    2018-05-08T18:03:15.1046280Z ##[section]Starting: Build FITDB
    2018-05-08T18:03:15.1202541Z ==============================================================================
    2018-05-08T18:03:15.1202541Z Task : Redgate DLM Automation 2: Build
    2018-05-08T18:03:15.1202541Z Description : Build and test databases with Redgate's DLM Automation
    2018-05-08T18:03:15.1202541Z Version : 2.0.22
    2018-05-08T18:03:15.1202541Z Author : Redgate Software
    2018-05-08T18:03:15.1202541Z Help : [More Information](https://documentation.red-gate.com/display/DLMA2/DLM+Automation+2+documentation)
    2018-05-08T18:03:15.1202541Z ==============================================================================
    2018-05-08T18:03:16.1223814Z Preparing task execution handler.
    2018-05-08T18:03:16.4036276Z Executing the powershell script: C:\agent\_work\_tasks\RedgateDlmAutomationBuild_7345fe1b-d099-46f0-a0d1-7292cd17feee\2.0.22\DlmAutomationBuild.ps1
    2018-05-08T18:03:18.6067242Z ##[warning]Could not find any suitable versions of DLMAutomation from any registered PSRepository
    2018-05-08T18:03:18.6873505Z ##[error]System.Management.Automation.CmdletInvocationException: A parameter cannot be found that matches parameter name 'MaximumVersion'. ---> System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'MaximumVersion'.
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.PSScriptCmdlet.DoEndProcessing()
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.CommandProcessorBase.Complete()
    2018-05-08T18:03:18.6873505Z --- End of inner exception stack trace ---
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
    2018-05-08T18:03:18.6873505Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
    2018-05-08T18:03:18.6873505Z at Microsoft.TeamFoundation.DistributedTask.Handlers.LegacyVSTSPowerShellHost.VSTSPowerShellHost.Main(String[] args)
    2018-05-08T18:03:18.7029855Z ##[error]LegacyVSTSPowerShellHost.exe completed with return code: -1.
    2018-05-08T18:03:18.7029855Z ##[section]Finishing: Build FITDB


    · Share on Twitter
  • CraigEddyCraigEddy Posts: 36 Bronze 3
    Wow! I think version 2.0.23 has fixed this. Thanks!

     :) 
    · Share on Twitter
  • Mike UMike U Posts: 316 Gold 1
    Yes, sorry. When we changed the addins to prefer the DLM Automation module from the PowerShell Gallery, we introduced an incompatibility with older PowerShell versions (<5.1) - as soon as the problem was reported, we shipped a fix in 2.0.23.
    Development Lead
    Redgate Software
    · Share on Twitter
Sign In or Register to comment.