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

Question

Trace LFDS requests

Directory Server Version 10

Updated February 3, 2022

asked on February 3, 2022 • Show version history

A customer is reporting that in the Event Viewer > Applications and Services Logs > Laserfiche > Directory Service > Server > Operational trace, they are getting an error every minute or two. The error is "TrusteeNotFoundException", but they have no idea what is causing it to be thrown.

We want to set up a Wireshark trace to figure out where/what (machine) is making the request that is generating the error, but I do not know much about setting up filtering in Wireshark. Can anyone provide steps to configure Wireshark to help pinpoint what machine is making the invalid request?

0 0

Replies

replied on February 3, 2022

Hi Burt,

Wireshark is a few troubleshooting steps further down the line here.

First, what version of LFDS is this? There are some now-fixed bugs that could cause inaccurate and excessive TrusteeNotFound exceptions to be logged.

Second, since you mentioned this message is showing up every minute or two, it's potentially indicative of a service or Workflow trying to use a repository connection profile with an LFDS service user that no longer exists. There are only so many places to check for those: Workflow, Forms, Audit Trail, Quick Fields, Import Agent, Email Archive. After you've upgraded to LFDS 10.4.5 or higher, I would start by checking out connection profiles in those applications.

0 0

You are not allowed to follow up in this post.

Sign in to reply to this post.

Asked February 3, 2022
Updated February 3, 2022
107 views