What sort of migration? Changing Workflow connection profiles has nothing to do with the AD users.

Hey, probably didn't explain this very well.

Let's imagine there is Server A and server B, server A is the source server, and server B is the destination server. I've copied the LF repository DB, the LF volumes and the WF DB over to Server B and re-configured everything in the new environment on server B.

Now several months have passed and new documents and new users have been added to Laserfiche, but no WF changes/template changes or system design changes have been made, just new documents and new users.

So I'm going to re-copy the repository DB and robocopy over the volume changes to update the repository (I've matched the drive letters so no volume re-configuration is necessary). However I don't want to copy over the whole WF database as nothing has changed apart from new users being added with their respective home folder locations. I'm wondering is simply copying over the dbo.user_param table here is going to have any adverse effects on the rest of the DB (I can't see or think why, but just wanted to be sure). The reason behind this, is I don't want to have to iterate through the many workflows to update the connection profiles (again). Unless there is a way you know of to update many workflows connection profiles in one go (this would be a good feature request actually).

Hope this helps explain a bit better....

Cheers!

Ok, that makes a lot more sense now. Thanks!

As long as the user SIDs match, that should be fine. Any new trustee directories will not be picked up this way.

If you are swapping out the repository, you should stop the Subscriber and reset the ASN value in HKLM\Software\Laserfiche\Workflow\Monitored Repositories\<repo GUID>. Set it to 0 so the Subscriber will only process events going forward. Otherwise, depending on whether it's behind or past the ASN number in the real repo, it will either process events again or ignore events until the number saved in its registry matches the ID of an event coming in.

Hi Miruna, I can't seem to find that registry key on the WF server?

This key was missing becuase the user the WF service was running as, didn't have rights to create the key.

Hi Miruna, Just picking back up on this, if I stop the WF and subscriber service, and set the ASN to 0 on the WF server, once I re-start the services again, there are several hundred workflows triggered. How can I clear the subscriber queue?

It sounds like your server had a backlog of events that were processed by the subscriber and matched its starting rules but didn't start a workflow yet.

Workflow writes these events to Windows message queues while they're waiting for the Workflow server to pick them up.

Control Panel\Administrative Tools\Computer Management\Services and Applications\Message Queuing\Private Queues. You can clear any queue whose name starts with "lfwf"

Thanks Miruna,

So I've stopped both WF services, deleted all the queues in there that start lfwf (which was all of them actually), cleared the ASN to 0 and re-started everything. The workflows have now all stopped running which is fab, however I now can't get any action to appear in the subscriber tracer. It seems to no longer be monitoring the repository, I've double checked the monitored repositories in the WF configuraiton manager, and that's all correct.

I also notice that refreshing the registry that the ASN keep rising, it's currently at 18476744. Is there something else I need to do in order to get this working?

What if I match the ASN value from the previous WF server? Will that help it match up?

Cheers!

I will have to raise a support case for this, as the migration is this weekend and it's not picking up any changes in the repo right now, so this is super urgent!