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

Question

Question

User activity issues for one User

Workflow
Updated July 25, 2014
asked on July 16, 2014

 We all of a sudden are having Workflows Terminate when the 'Route Entry to User' and 'Find User' activities are being used on one particular user. Looking at the messages on why it has Terminated 'No user was found'. I can't see how this user is any different to any other user. looking in the Admin Console.

 

So I thought I'd check these activities in the Workflow itself. I can find this User in the 'Route Entry to User' activity (along with his Workflow details like email, default folder, etc). But when I want to select him the 'Ok' button is greyed out?? See attachments. So something doesn't look right? No issues with any other user.

 

I tried deleting the user in the Admin Console and have re-added him again, but still no luck.

 

Note: In the WF Designer I am using Admin account wfuser.

 

Any help would be much appreciated.

 

cheers

Grant

Untitled.jpg
Untitled.jpg (46.22 KB)
Download
0 0

Answer

SELECTED ANSWER
replied on July 25, 2014

Just to clarify, the issue was Workflow thinking that the trustee was a group rather than a user. That is why you could find it when searching for trustees, but not when searching for users from the Find User activity.This was caused by the fact that there were 2 records in the account_cache table in the repository for the same account name, one saying it was a group, one saying it was a user.

 

Due to how the table is used, it's not likely it was the Admin console or Workflow generating the conflicting data, but it is a bug. We're still looking into how it happened.

1 0

Replies

replied on July 16, 2014

Hello Grant,

 

If you're running WF 9.1.1, you may consider KB1013462's hotfix as it solves a Find User issue.

 

Louis-Simon

0 0
replied on July 16, 2014

Hi Louis-Simon,

 

Yes I have applied the hotfix but still no luck.

 

Grant

0 0
replied on July 17, 2014

Hi Grant,

 

Have you checked you have the trustees configured correctly?

 

In the workflow designer, go to tools>Configure Trustee Directories...

 

Check that this is correctly configured and isn't pointing at anything silly or an old server.

 

Hope this helps! yes

0 0
replied on July 17, 2014

Hi Chris,

 

Yes, I have already checked this. 

 

Grant

0 0
replied on July 18, 2014

Hi Grant,

 

If you are looking into Active Directory for the user you can change what properties you are using to match the user. I assume you are matching the user from a token?

 

Check in the WF history and see which user is causing the issue then check their account configuration in AD. You may find that whichever parameter you are trying to match is different on that particular AD account. Alternatively try matching a different AD parameter from the token and see if that changes the behavior.

 

Hope this helps Grant!

0 0
replied on July 20, 2014

Thanks Chris, we are looking up Laserfiche type Trustee directory. I noticed that I can Search for the user in Tools | Configure Trustee Directories. But when we do the same search using an activity (like Find User or Route to User) this user cannot be found. I actually think there is a bug and am now talking to Tech Support. 

Thanks very much for your help.

 

cheers

Grant

 

0 0
replied on July 21, 2014

No Worries Grant,

 

Hope you get it sorted. Could you please post the solution here when you do? I''m curious cool

 

Cheers!

0 0
replied on July 24, 2014

Hi Chris and others,

 

I finally managed to solve the issue with LF Tech Support. It appears that either the Admin console OR Workflow Designer has created 2 records for this user in the Microsoft SQL database. So it sounds like a bug, I have left it with them to look for a patch. There may be others out there with the same problem. We are not sure what has caused it for only one user and not others. But this user does have a lot of workflows that route to him, therefore there could be other affected. Now it is a matter of going through these to double check.

I hope that helps?

 

cheers

Grant

 

0 0
SELECTED ANSWER
replied on July 25, 2014

Just to clarify, the issue was Workflow thinking that the trustee was a group rather than a user. That is why you could find it when searching for trustees, but not when searching for users from the Find User activity.This was caused by the fact that there were 2 records in the account_cache table in the repository for the same account name, one saying it was a group, one saying it was a user.

 

Due to how the table is used, it's not likely it was the Admin console or Workflow generating the conflicting data, but it is a bug. We're still looking into how it happened.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...