You are viewing limited content. For full access, please sign in.

Question

Question

Cannot save CSV in WF, but can in Script Editor

asked on August 13, 2024 Show version history

I have a Workflow with an SDK Script that generates a CSV to a Network Location. When I test the Script in the Script Editor, I am able to save the CSV, but when I run the actual Workflow I get an error that the path is denied. I am logged in as a user named Laserfiche, and I can access the folder. And the Workflow Service is running as the same Laserfiche user. So why wouldn't it be able to save? 

I have also tested it with the location mapped to a drive named "I." Again, I can save the CSV in the Script Editor, but when I run the WF, I get an error. This time, "Part of the path was not found."

One possibility I've seen is that the path I'm currently using may not be the server's true name, but an alias. We are looking into this. But I still find it odd that the Script Editor can function if the Workflow cannot. Even if we get a new path, I'm not sure if the same issue will arise or not. Anyone seeing an issue I'm missing?

 

 

 

 

 

 

 

 

 

Update: The client has told us we have the correct server name, but it is not a Windows Server, it is an IBM iSeries Server. Should that change how we format anything in the Script? 

 

0 0

Replies

replied on August 13, 2024

The path has to be accessible from the perspective of the Workflow Server's service user. Services do no have access to mapped drives, just local drives and UNC paths. The "access to the path <path> is denied" error likely indicates that your Workflow Server is running as Local Service and can't access the network. Running it as Network Service or a domain user with rights to the remote location should clear that up.

Because the Designer (and script editor) runs as a Windows application rather than a service, it can access mapped drives available to the currently logged in Windows user.

1 0
replied on August 13, 2024

I mentioned that the Workflow is running as the same user I'm logged in as and posted an image of that service, so I don't think that's the issue, unless I'm missing something.

0 0
replied on August 13, 2024

Hey Miruna,

I am working with Chris on this and like he said, from the screenshot at the bottom of the original post, the workflow service is running as a domain\laserfiche account.  The screenshot shows that service user and the whoami showing the same user.

 

0 0
replied on August 13, 2024

What if you try saving somewhere on the C drive instead?

A mapped drive will certainly not work for the service because it is mapped to your windows session.

\\servername\path should work with proper permissions, but try C or any native drive letter first to make sure the service can actually save somewhere locally via the service.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.