Hello,
I am having this error i n my Workflow designer when I try to start a workflow.
Can anyone help please?
Regards,
Ketsia
Being a VAR you can have access to a VAR pack which contains all the products of Laserfiche for testing purposes, this has to be renewed every year.
For your demo license, can you check to see if the license has expired. In the install directory of both workflow and Laserfiche Server you will find an LF.LICX file which you can open in notepad and look for an expiration date. (don't forget the date will be in US format).
Hi Ketsia,
What version of LF workflow and LF server are you using?
What Licensing model is this? Avante, Rio etc?
This error was also discussed here - https://answers.laserfiche.com/questions/53229/Laserfiche-Workflow-91-License-Error-0645WF1
Hope this helps poing you in the right direction! 
Hi Chris,
Am using LF Avante 10 and for WF designer its version is 10.0.0.249.
Regards,
Ketsia
Hi Ketsia,
Is this your VAR pack or is this on a customer site?
Cheers!
Hello,
what do you mean by VAR pack? It is a demo license
Being a VAR you can have access to a VAR pack which contains all the products of Laserfiche for testing purposes, this has to be renewed every year.
For your demo license, can you check to see if the license has expired. In the install directory of both workflow and Laserfiche Server you will find an LF.LICX file which you can open in notepad and look for an expiration date. (don't forget the date will be in US format).
The VAR demo uses Avante, so Workflow doesn't have a license in this case. In Avante and Rio cases, Workflow is considered licensed when it is monitoring a licensed Avante or Rio repository. So in this case, the error would indicate the LF Server license has expired or no monitored repository is configured.
For legacy United or Team systems, Workflow requires a license. It's not stored in the install folder. You can provide a new license through the Workflow Admin Console (Server Configuration\Licenses) and the server will store it where it needs it and load it without requiring a restart.
I am having the same issue. I have found 4 copies of this file. I am showing an expired date for the \Laserfiche Workflow 9\Licenses and \laserfiche Workflow9 -- 2017-12-24.
The other two files are showing 2018-12-24. Can I just change the two expired dates and save the file?
This is on our test server...
Thanks!
Sue
Hi Sue,
workflow is actually licensed by your LF server. Check the LF.licx file in the server directory C:\program files\Laserfiche\Server\lf.licx
Hi Chris and thank you :)
The date on that file is 2018-12-24. See attached...
Any other ideas?
Thanks again,
Sue
Actually, according to our records, you're running Laserfiche United, so Workflow needs its own license. You can look in the C:\Program Files\Laserfiche\Laserfiche Workflow 9\Licenses\70 folder if you want, but the easier way to check (and replace) a Workflow license is from the Workflow Administration Console. Look under Server Configuration\License and it will indicate if it's expired or not. If it's expired or you don't see one, you'll need to get one by reactivating your Workflow key.
Thanks Miruna!
I found the expiration under the Server Config\Licens under the WF Admin console.
So... I have gotten to the properties following these:https://www.laserfiche.com/support/webhelp/workflow/9.0/en-us/content/resources/configuration/Config%20Manager/Configuring%20License%20Information.htm
And based on our portal info it doesn't look like we have any more activations. How do I get reactivated? Thank you again with all your help. I'm the newbie :)
That's ok, the number refers to activating new instances. If you're not moving the Workflow Server, you can reactivate that instance. This white paper should have the instructions you need (See the section on "Activation using the activation utility"). Then once you obtain the new license, come back to the Workflow Admin Console and click Import to replace the license. You don't need to restart services after that, the Server will load the new license within a minute or so.
Thanks Miruna!!
Did you create that doc just for me 
? (April 2018)
So I don't have to move the files as stated in the doc? Just go back to Workflow Admin Console and Click Import to replace the license?? -- as stated in your previous response
Also-- I noticed in the NEW lf.licx file that was generated there was no expiration date...
I went ahead and imported with using the Workflow Administration Console and BINGO! We are active again :)
Thank you so very much Miruna for your quick responses and support.
Have a lovely day and week!
It may be helpful to know that WF makes multiple connections to the LF repository--in addition to the connections that are configured for individual WFs there is a connection made in the WF Config Mgr. When there is a licensing issue it will appear that these connections are working properly (both the Config Mgr and individual / common profiles) but they will need to be removed and re-created
What do you mean by licensing issue? Workflow reconnects to the Laserfiche Server when the server is restarted, there are no connections to clean up.
the error message this thread was started with is about licensing--its in the error message itself.
Sorry, still not following. An unlicensed server won't make connections to Laserfiche.
Though, if you're referencing the support case where the server has been rebuilt from a backup, there isn't enough information in it to know why the Subscriber was not reconnecting. Your logs might have more information on what was going on.
It appears that that error message (and those similar to it) can happen even though the server is properly licensed but one or more of the connection profiles is corrupt or had been created under a different activation. Some users may not know to look into WF Admin Console error logs (or have access to them) and so would never find a connection between this thread and the one related to the error there ("Error sending HTTP request to server," https://answers.laserfiche.com/questions/116958/error-sending-http-request-to-server)