HI all,
I have two near identicle workflow servers. On one server I can install and configure the workflow web and REST services. On the other, I can install the services but they are not available to configure. Any idea why?
-Ben
HI all,
I have two near identicle workflow servers. On one server I can install and configure the workflow web and REST services. On the other, I can install the services but they are not available to configure. Any idea why?
-Ben
Check either of these two registry keys:
"HKLM\Software\Laserfiche\Workflow\Web Service",
"HKLM\Software\Wow6432Node\Laserfiche\Workflow\Web Service
In the keys, you should see a 'CurrentVersion' with a value that is a subkey. (e.g. 10.2) Go to that sub key, it should have an 'InstallPath' value. The directory in the InstallPath must exist in order to see the Workflow Web Services configuration
One of our customers just ran into this. Seems that the workflow 10.2 installer forgets to create the Wow64 keys on Windows Server 2012 R2. I added the keys and restarted the workflow service, now what? How do I get the Web Services configuration added back to the configuration screen? Is there any way to configure these in the workflow administration console?
Good find.
I don't remember what I did. Perhaps restart Subscriber as well but that's all.
-Ben
Just found it, there was a problem with the non Wow64 string value. It had the wrong drive letter for the install path. Not sure where it was getting that drive letter from, I tried repairing first thing this morning when it was not working. Anyways I updated the drive letter and it worked! No service restart required, just restart the configuration utility.
Can you make sure the "Workflow" website was created under IIS? We've had a couple of cases where the site isn't created during the installation. Or just uninstall and reinstall Workflow.
The latest Workflow 10.4 installer is creating the Program Files folder with the name of Laserfiche Workflow 10.4 but setting the registry key to look for C:\Program Files\Laserfiche\Laserfiche Workflow 10.2 which does not exist.
Why can't we just stick with a folder name of Laserfiche Workflow. The version shouldn't be in the folder name since the version is always changing, and that is causing the registry keys to break.