How can we help you today? How can we help you today?
CraigEddy
When I attempt to open Tab History, this is the error I'm getting: '{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'. SSMS: Microsoft SQL Server Management Studio 11.0.5058.0 / comments
When I attempt to open Tab History, this is the error I'm getting:'{DependencyProperty.UnsetValue}' is not a valid value for property 'OpacityMask'.SSMS: Microsoft SQL Server Management Studio 11.0...
0 votes
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 / comments
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...
0 votes
You could use the Powershell script above, augmented to write the data into the table of your choice in your SQL Server instance. Just a thought... / comments
You could use the Powershell script above, augmented to write the data into the table of your choice in your SQL Server instance. Just a thought...
0 votes