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

Question

Question

"user does not have enough rights to perform the action" anything workflow

asked on July 7, 2022

Hello, I have had our LF server, domain, and AD completely wiped out. We have moved to Azure and restored most of our servers. Currently, I can sign into Laserfiche with only Laserfiche accounts. I'm checking on my Workflow server and it's running, however, anytime I try to do anything on there with a local user that is part of the administrator group on the box, I get this error. 

my LFservice account is the only account I can use to access this box currently. My data sources seem to be working when the workflow runs on their own, but when I try testing them, I get "object was not found "Error message. 

What can I do to get this local account full access to everything on my workflow server? What am I missing? 

Thanks. 

0 0

Replies

replied on July 7, 2022

Hi Lucas,

First, I'm sorry to hear that. I wish you the best with recovery operations. 

Have you restored Active Directory and is the restored Workflow server still successfully joined to the same AD domain?

0 0
replied on July 7, 2022

I just had the thought that if the ANLFWFWRV\lfservice account really is a local Administrator, you can try using PsExec to launch PowerShell as the NT AUTHORITY\SYSTEM identity, and from there launch Workflow Administration Console via its exe (example).

If you're able to run the WF Admin Console as SYSTEM, you should be able to get to the Security node and re-add whatever should be there. Try giving the lfservice local account the Administrator role within Workflow.

Please let me know if that works. If it doesn't, there may be a way to get you back in by modifying the Workflow database directly, though that would be a last resort.

1 0
replied on July 11, 2022

Hi @████████, checking back in to see if you were able to get past this issue and/or still needed assistance.

0 0
replied on July 12, 2022

Hello Samuel, 

I finally got back to this and holy smokes, it worked. I'm back in. Thanks for the help. 

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

Sign in to reply to this post.