Trying to resume a Measure-FleetCoreWorkload pass after it stops with an error. After the stoppage with errors seen below, I try to resume Measure-FleetCoreWorkload pass again but after starting things up it just continues to add line after line of
2024-10-08T13:32:44: COMPLETION CHECK 4275 : 0/240 done (0.00s, total 0.00s)
What steps need be taken to get it going again, or to clean things up? I used the original VMFleet with success back in 2019/2020 before version 2.0 came out and was hoping to see a full pass using the new functionality. Its stopped on me twice so far.
PS>TerminatingError(): "The pipeline has been stopped."
>> TerminatingError(Move-Item): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The process cannot access the file because it is being used by another process."
>> TerminatingError(Move-Item): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The process cannot access the file because it is being used by another process."
2024-10-07T15:58:10: Iteration file content saved to C:\ClusterStorage\collect\result\error for triage
Move-Item : The process cannot access the file because it is being used by another process.
At C:\Program Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1:8399 char:24
writeErrorStream : True
Exception : System.IO.IOException: The process cannot access the file because it is being used by another
process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileInfo.MoveTo(String destFileName)
at Microsoft.PowerShell.Commands.FileSystemProvider.MoveFileInfoItem(FileInfo file, String
destination, Boolean force, Boolean output)
TargetObject : C:\ClusterStorage\collect\result\result-qos2458-vm-base-SERVERNAME-048.xml
CategoryInfo : WriteError: (C:\ClusterStora...SH51C05-048.xml:FileInfo) [Move-Item], IOException
FullyQualifiedErrorId : MoveFileInfoItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at Start-FleetResultRun, C:\Program
Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line 8399
at RunInner1VCPUMatrix, C:\Program
Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line 7339
at Measure-FleetCoreWorkload, C:\Program
Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line 7387
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {22, 22}
PSMessageDetails :
Exception : System.IO.IOException: An item with the specified name
C:\ClusterStorage\collect\result\76dc3cbb-d6b1-4624-a425-b8f265cbba81 already exists.
TargetObject : C:\ClusterStorage\collect\result\76dc3cbb-d6b1-4624-a425-b8f265cbba81
CategoryInfo : ResourceExists: (C:\ClusterStora...25-b8f265cbba81:String) [New-Item], IOException
FullyQualifiedErrorId : DirectoryExist,Microsoft.PowerShell.Commands.NewItemCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock><Process>, <No file>: line 52
at DoIteration, C:\Program Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line
7937
at Start-FleetResultRun, C:\Program
Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line 8363
at RunInner1VCPUMatrix, C:\Program
Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line 7321
at Measure-FleetCoreWorkload, C:\Program
Files\WindowsPowerShell\Modules\VMFleet\2.1.0.0\VMFleet.psm1: line 7387
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {0, 1}
PSMessageDetails :
Trying to resume a Measure-FleetCoreWorkload pass after it stops with an error. After the stoppage with errors seen below, I try to resume Measure-FleetCoreWorkload pass again but after starting things up it just continues to add line after line of
2024-10-08T13:32:44: COMPLETION CHECK 4275 : 0/240 done (0.00s, total 0.00s)
What steps need be taken to get it going again, or to clean things up? I used the original VMFleet with success back in 2019/2020 before version 2.0 came out and was hoping to see a full pass using the new functionality. Its stopped on me twice so far.