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

Question

Question

Failed to publish workflow Error code [0232-WF1] [0411-WF0]

asked on November 24, 2016

I have a workflow that includes a very simple SDK script (a few lines in C#).

            // Write your code here. The BoundEntryInfo property will access the entry, RASession will get the Repository Access session
            FolderInfo FI = (FolderInfo)this.BoundEntryInfo;
            FI.AutoVersionChildren = true;
            FI.Save();

When I attempt to publish this workflow, I get the following error:

Failed to publish workflow 'worflow_name': Access denied. "Laserfiche.Workflow.Activities, Version=8.3.0.0, Culture=neutral, PublicKeyToken=null" is not authorized to be run as part of a script. [0232-WF1] [0411-WF0]

If I disable this small script, the workflow publishes correctly. Also, I can publish it on the dev WF server but not the live server.

Any thoughts?

Thank you,

Ken

0 0

Replies

replied on November 28, 2016

Is scripting enabled on your production server?

0 0
replied on December 1, 2016

Hi Miruna! Yes, Scripting is enabled. There are several other scripts published.

0 0
replied on January 17, 2017

Did you find a resolution to this issue?

0 0
replied on January 17, 2017

Yes: the problem was that we did not have an exact match in the Custom Assembly List in the Workflow Administration Console on the Live machine (we did on the Dev machine though, that's why the difference between the two machines).

Once we added a Custom Assembly List entry for "Laserfiche.Workflow.Activities, Version=8.3.0.0, Culture=neutral, PublicKeyToken=null" the problem went away. This entry is added in:

WF Admin Console > wfhostname (prolly localhost) > Security > Scripting (double-click Scripting to open the dialog).

Also, in this dialog, on the Settings tab, ensure that you have checked "Enable scripting activities" and selected which types of scripts (C#, VB, or both).

Ken

1 0
replied on May 12, 2020

I ran into this problem when I used the resolve option to update the DLL location after copying the workflow from another machine. Instead I had to remove the reference, and re-add it through the wizard.

0 0
replied on May 12, 2020

This configuration is not supported.

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

Sign in to reply to this post.