Geeting error, Workflow in not liecnsed.
Question
Question
The Workflow Server needs a license with The Laserfiche Serial '' as a connection. [0543-WF0]
Replies
Hi, not sure if this is helpful input but by chance have you updated all the license locations? We use Rio and I had to update the Forms and Server license.
https://support.laserfiche.com/kb/1000988/license-file-locations
Hi Chris,
First thing I'd check is if there is a repository configured properly in the Workflow Configuration Manager. Workflow doesn't really need a license to function (at least in every licensing model I've ever worked with), but will throw that error if there isn't a monitored repository configured.
Could be way off base. But without getting into it further, that's what I'd check first.
Where are you getting this error? The error indicates that you are connecting to a repository hosted on a Laserfiche Server running a United license, so Workflow also needs a license in that case.
Hi Miruna,
I am getting this on Workflow Configuration Manager and Workflow Administration Console when adding or attaching the repository.
I am not familiar with a united license.. but I am using a VAR Rio. It was working previously until a server reboot.
Hm, that's ...interesting. I assumed you edited out the serial from the message in your original post.
Is your Laserfiche Server properly licensed? If you look at it in LFAdmin Console, what does it list for its license type and serial?
I have tried to generate new licx files from LFDS.
A note for anyone else looking into this issue: check what license type your Laserfiche Server is running. If it's not Avante/Rio/Subscription, you will also run into this issue. We had a similar issue where a Laserfiche Server license expired and the Laserfiche Server server license reverted to Laserfiche Classic, which Workflow cannot license against. The issue was resolved by generating a new Laserfiche Server license file from LFDS, updating the Laserfiche Server license and restarting the Laserfiche Server Service; once we performed those tasks, we were able to complete the Workflow Configuration Manager Register Repository steps without issue.