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

Question

Question

Find User Activity in WF not finding all Domain accounts

asked on September 29, 2014

We have switched over 240 Users from Laserfiche Named Accounts to Windows Domain Accounts this past weekend. This morning we found that for 8 of the 240 users Workflow does not seem to find the Account against the Trustee Provider. Below is the Error Message displayed in Workflow Designer for one of the Users that it cannot Find.

    2014/09/29 12:22:02 PM    Find User    No user was found with search value 'BWMAFR\Christa.Erasmus' in user provider 'LF\VMISFDMSAFSAPP.africa.bwm-

global.com_AFSLFPROD'. [0247-WF1]

 

The strange thing is that if you manually search against the Trustee Provider via Designer, the User and all attributes are found. All 240 users have been created in the same manner and We even tried Deleting and re-creating the User against the repository to see if that would have any effect but it does not.

I read the a different thread on here where the person seemed to have a similar issue and the response to him was that the Workflow Service needed to run as a Domain account with rights to find the User. Our service is not running as a Domain account but surely if that was the case then it would not have found any of the 240 users?

The problem for us now, is that none of these 8 users are able to start Workflows as the Workflow terminate as they are not recognized and valid accounts/users.

what could be happening here?

0 0

Replies

replied on September 29, 2014

Some more info we found:

Not sure if this is an indication of anything but we found that the effected users all had multiple entries in the account_cache table. see below:

When creating this User in QA, the behavior is the same as in Production. What we found though while testing in QA, is that If we Clear the account_Cache entries for this user, Delete the Account and then Re-Create it, initially there is only one Listing with isuser = 1 that is listed in the Account_cache. However as soon as the user logs in, then the other to entries with isuser = 0 returns.

While only the one entry is listed in the Account_cache table, then the Find User activity in workflow is happy to find the user. However, as soon as the other 2 return, then the behavior returns and the Find User Activity terminates with the error message of not finding the user.

I have also now confirmed that even by changing that the Workflow Service runs logged in as a Domain account, does not change the behavior. 

We also asked the IT guys to check AD to ensure there is only one Account listed for the Users in question and everything seems normal with the Accounts and only one account each. 

Where does the account_cache populate the data from and why would it be populating this differently for the effected users?

0 0
replied on September 29, 2014

Yes, having the wrong data in the account_cache table is what is causing Workflow to fail. You can delete the 3 lines. The Laserfiche Server will cache the user again when she logs back in. We're still investigating why the account_cache table ends up with the wrong data.

0 0
replied on September 29, 2014

Hi Miruna,

 

What would the the suggestion be then for us for now?

We have tried deleting the incorrect data but as mentioned they all return when they log back in. The major concern is that these users have not lost a days worth of productivity as they are unable to initiate any workflow or action them.

0 0
replied on September 29, 2014

All 3 rows return when the user logs in?

0 0
replied on September 29, 2014

that is correct,

0 0
replied on September 29, 2014

One more thing we noticed when reviewing the account_cache data, Majority of the working users only have one entry in the table, however there are some that have 2 and a couple that also have 3 entries in the Table, but they still seem to work fine.

The only aspect that the 8 users have in common is that they all have 3 entries each in the table.

0 0
replied on September 29, 2014 Show version history

Is there more than one domain called BWMAFR?

0 0
replied on September 29, 2014

No, there is only the one Domain called BMWAFR

0 0
replied on September 30, 2014

A support case had been opened for this issue. Working with your reseller, we found that when running the powershell console app from this page, it indicated that there are duplicate domains using the NetBIOS name, BWMAFR.

 

Once that has been addressed, then the Laserfiche Server should only record a valid row of data into the account_cache table. Then Workflow should function properly when finding users.

0 0
replied on October 1, 2014

Hi Alexander,

 

thank you for the update. Our IT is busy looking into this. Could you possibly shed some light how the NETBIOS names are effecting the Windows Account Names though? We are a bit unclear as to how they effect each other?

Also Keep in mind that BWMAFR is our Domain name so we trust that the test was done correctly and has therefor provided the correct results?

0 0
replied on October 1, 2014 Show version history

Having multiple domains with the same NetBIOS name will cause the name to SID translation to be ambiguous, which could lead to various issues. These issues aren't just limited to what you're running into with Workflow, but there could be security concerns.

0 0
replied on October 2, 2014

Hi Alexander,

We do not have multiple Domains on our network so this does not apply to us. 

Our IT have however fixed the duplicate Netbios names and we have re-tested and the behavior is the same. If anything we now have 9 instead of 8 users that it does not find.

Our IT is asking for additional options to be checked and troubelshoot. 

0 0
replied on March 8, 2015

Hi All,

 

We have had the exact same issue as yourself Vincent. A case was logged with Tech Support. They are working on a fix, which is SCR 121410.

I am not sure how far away this fix is form be patched?

 

cheers

 

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

Sign in to reply to this post.