1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Few of the items you can look at; some may seem obvious and you probably already checked them out, but I will list them just for scrutiny:
- Please validate if the latest versions are installed for both SSM and AWS PowerShell modules in the EC2 Instances (1-2).
- Can you please confirm if there are no AntiVirus/Security Software which may be scanning the folders and thus the process?
- If the system is too busy when taking the snapshot, the VSS backup may also time out. Is there a maintenance window to execute the same process off hours in case this is not the case?
- Check the SSM logs from the instance during the execution of the Snapshot, under "C:\ProgramData\Amazon\SSM\Logs" to see if something is outstanding around the time the Backups is being executed.
I hope the above information can led to a path of troubleshooting to find new clues.
References
- Amazon SSM Agent Releases - https://github.com/aws/amazon-ssm-agent/releases
- Installing the AWS Tools for PowerShell on Windows - https://docs.aws.amazon.com/powershell/latest/userguide/pstools-getting-set-up-windows.html
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
Thanks for the suggestions.
The initial error I posted is the first few lines of the error. I have copied the entire error below: Encountered unexpected error. Please see error details below Message : The process cannot access the file 'C:\ProgramFiles\Amazon\AwsVssComponents\vsserr.log' because it is being used by another process. Data : {} InnerException : TargetSite : Void WinIOError(Int32, System.String) StackTrace : at System.IO.__Error.WinIOError(Int32 errorCode, StringmaybeFullPath)at System.IO.FileInfo.Delete()at Microsoft.PowerShell.Commands.FileSystemProvider.RemoveFileSystemItem(FileSystemInfo fileSystemInfo, Boolean force) HelpLink : Source : mscorlib HResult : -2147024864 MyCommand : Remove-Item BoundParameters : {} UnboundArguments : {} ScriptLineNumber : 740 OffsetInLine : 9 HistoryId : 1 ScriptName : C:\ProgramData\Amazon\SSM\InstanceData<instance-id>\document\orchestration\d8987ebd-b404-4fd3-90d8-5729d9a39426\runPowerShellScript_script.ps1 Line : del $vssStdErr PositionMessage : At C:\ProgramData\Amazon\SSM\InstanceData<instance-id>\document\orchestration\d8987ebd-b404-4fd3-90d8-5729d9a39426\runPowerShellScript_script.ps1:740 char:9
PSScriptRoot : C:\ProgramData\Amazon\SSM\InstanceData<instance-id>\document\orchestration\d8987ebd-b404-4fd3-90d8-5729d9a39426\runPowerShellScript PSCommandPath : C:\ProgramData\Amazon\SSM\InstanceData<instance-id>\document\orchestration\d8987ebd-b404-4fd3-90d8-5729d9a39426\runPowerShellScript_script.ps1 Invocation
We've checked all of the items above. The last thing that we did was exclude the folder from A/V but that did not make a difference. It seems like the issue is as stated above, that the ec2-vss-agent.exe process is causing the issue. Any other ideas as to why that process would be keeping the vsserr.log open even after the VSS Run Command completes?