Issue with process and unsure of this error and root cause

[mahavs-gw]

we are using the TFVCGet task in our pipeline and we ran into issue couple of days ago. We havent changed the pipeline but it failed from Monday. there are no changes in the environment or access. This was working for more than 6months and we are getting the following error and troubleshooted most of the stuff but we couldnt find the root cause for this error. Not sure it throws error "##[error]Unhandled: EPERM: operation not permitted, open". can you please help me with this. Any insight would be helpful.

2024-10-23T17:01:46.6338782Z ##[section]Starting: Get DevOps folder from TFVC
2024-10-23T17:01:46.6352152Z ==============================================================================
2024-10-23T17:01:46.6352341Z Task : TFVC - Get latest
2024-10-23T17:01:46.6352440Z Description : Gets a file or a folder tree from TFVC source control
2024-10-23T17:01:46.6352579Z Version : 2.2.9
2024-10-23T17:01:46.6352662Z Author : Seva Alekseyev
2024-10-23T17:01:46.6354904Z Help :
2024-10-23T17:01:46.6355043Z ==============================================================================
2024-10-23T17:01:47.9579929Z $/SPI-GreenWave20/Main/Source/DevOps
2024-10-23T17:01:48.2173799Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts
2024-10-23T17:01:48.2175458Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/SPI-GreenWave20-CD.ps1
2024-10-23T17:01:48.4358558Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/SPI-GreenWave20-CD-RunTests.ps1
2024-10-23T17:01:48.4678022Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\SPI-GreenWave20-CD.ps1'
2024-10-23T17:01:48.7411325Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/SPI-GreenWave20-CD-Patch-Connectors.ps1
2024-10-23T17:01:48.7450872Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\SPI-GreenWave20-CD-RunTests.ps1'
2024-10-23T17:01:48.9479929Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/SPI-GreenWave20-CD-BuildDropFolder.ps1
2024-10-23T17:01:48.9524613Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\SPI-GreenWave20-CD-Patch-Connectors.ps1'
2024-10-23T17:01:49.4046206Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/SPI-GreenWave20-CI-BuildDropFolder.ps1
2024-10-23T17:01:49.4079959Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\SPI-GreenWave20-CD-BuildDropFolder.ps1'
2024-10-23T17:01:49.5885988Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/SPI-GreenWave20-CI-Patch-Connectors-BuildDropFolder.ps1
2024-10-23T17:01:49.6082001Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\SPI-GreenWave20-CI-BuildDropFolder.ps1'
2024-10-23T17:01:49.8586174Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\SPI-GreenWave20-CI-Patch-Connectors-BuildDropFolder.ps1'
2024-10-23T17:01:50.0037733Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/Modules
2024-10-23T17:01:50.0039006Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/Modules/ScriptModules.ps1
2024-10-23T17:01:50.2183485Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/Modules/SPI-GreenWave20-CD-ScriptModules.ps1
2024-10-23T17:01:50.2373902Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\Modules\ScriptModules.ps1'
2024-10-23T17:01:50.4209135Z $/SPI-GreenWave20/Main/Source/DevOps/Scripts/Modules/SPI-GreenWave20-CI-ScriptModules.ps1
2024-10-23T17:01:50.4412083Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\Modules\SPI-GreenWave20-CD-ScriptModules.ps1'
2024-10-23T17:01:50.6841390Z ##[error]Unhandled: EPERM: operation not permitted, open 'c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\Modules\SPI-GreenWave20-CI-ScriptModules.ps1'
2024-10-23T17:01:50.7039686Z ##[section]Finishing: Get DevOps folder from TFVC

[sevaa]

EPERM normally means the service account under which the AzDevOps agent runs doesn't have the permissions to the target directory.

If you are not sure what is the service account, run a deployment with a command line task with a whoami command.

To test the permissions, run a deployment with a task that writes into the target folder. Something like echo Boo >c:\WebSites_Shared\Deployment\Drop\DevOps\Scripts\Modules\boo.txt. If that fails, you would know the permissions are off.

Now, whether the service account was changed recently, or the permissions were changed recently - I won't know about that.

[sevaa]

@mahavs-gw Do you have any new diagnostics on this? I'm suspecting the problem is in your agent/account/filesystem setup, not in the code of the extension per se, but only you can confirm or deny that.