Thanks for your patience. We are aplogize for the incovienve this issue may have caused.
Please make sure you are using:
- Windows 2008 R2 SP1 or higher
- PowerShell 3.0 or higher
- .NET Framework 4.6.2 or higher
If those requirements are already met and you are still facing the issue, you can you can use tools like Process Monitor/ Process Explorer to capture a trace of file events under a specific directory or use the information in your logs to diagnose your error.
Start by looking at the logs in your completed build or release. You can view logs by navigating to the pipeline run summary and selecting the job and task. If a certain task is failing, check the logs for that task. In addition to viewing logs in the pipeline build summary, you can download complete logs which include additional diagnostic information, and you can configure more verbose logs to assist with your troubleshooting.
Along, with the pipeline diagnostic logs, the following specialized log types are available, and may contain information to help you troubleshoot.
Worker diagnostic logs
Agent diagnostic logs
Other logs
Hope that helps. Please let us knoe if you have further questions.
-Grace