Skip to main content

I’ve been running a script on FLOW for months that unzips and deploys apps to an IIS web server by copying them to the wwwroot folder. If the app already exists and needs updating, the script backs up the existing folder, deletes it, and then deploys the new version. However, about two weeks ago, it stopped working because the Python function in the Python caller can’t delete and replace the existing directories.

I have admin permissions to the wwwroot folder, and the workbench runs correctly from my computer. But when it runs from FLOW as the application account, it fails. The app account has the same permissions on the wwwroot folder as I do, and both accounts are in the admin group.

I suspect a Windows update or a policy change might be causing this issue.

Any ideas?

Hi @smclaugh1

In this situation, are you referring to the account used to log into FME Flow or the service account responsible for running the Flow system services?

When jobs are executed on FME Flow, file system access depends on the permissions of the service account running the FME Services.

It’s possible that a recent policy change has affected the permissions of this account. If you haven't already, I recommend checking the specific folder to ensure the service account has full read and write access.

 

-Dylan

 


I’m referring to the service account that runs the Flow services, that account has full permissions to the wwwroot folder and is an admin on the web server machine. It must have been some policy change that happened a few weeks ago, nothing else has changed and the workbench still works correctly from my laptop. I also have full permissions to the wwwroot folder and am an admin on the web server machine.

 


I think I’ve found the problem, waiting for IT to repond to my ticket.

I believe the Kerberos Impersonation level for this account is set to Impersonation and needs to be changes to delegation on the web server.


Reply