System.ArgumentException: The parameter is incorrect

[vasiliisorokin]

Getting error during tests in azure pipeline using VSTest version 17.11.0 (x64)

Error Message:
   System.InvalidOperationException : Test execution was skipped due to a prior exception in the harness.
---- System.ArgumentException : The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
  Stack Trace:
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
----- Inner Stack Trace -----
   at EnvDTE.Commands.Item(Object index, Int32 ID)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

[vasiliisorokin]

UPD: it started to happen on 20240912.1.0 windows-2022 image version in azure pipelines, on 20240811.1.0 it was ok

[sharwell]

It's hard to tell where this is being thrown. Are we able to narrow it down, e.g. to one of these?

vs-extension-testing/src/Microsoft.VisualStudio.Extensibility.Testing.Xunit.Shared/Harness/VisualStudioInstance.cs

Line 258 in 0b36151

if (dte.Commands.Item(WellKnownCommandNames.IntegrationTestServiceStart).IsAvailable)

vs-extension-testing/src/Microsoft.VisualStudio.Extensibility.Testing.Xunit.Shared/Harness/VisualStudioInstance.cs

Line 266 in 0b36151

if (_inProc.IsCommandAvailable(WellKnownCommandNames.IntegrationTestServiceStop))

[vasiliisorokin]

Not sure, I suppose its first one.
I experienced this only during azure pipeline run and only after image update, I created this issue on their side actions/runner-images#10644