My computer performance is substantially reduced when I run this agent.
Check the ldap.sync.interval property in the inserverUR.ini file in the Perceptive Content shared etc directory $(IMAGENOWDIR6)\etc. If this property is 0 or less, synchronization is continuous. Continuous synchronization is CPU intensive and dramatically affects performance. Change the property to the number of hours between each synchronization. It is highly recommended to set it to 1 hour or higher.
The agent is not running.
Verify the status of the agent by opening a window that accepts command prompts, navigating to the Perceptive Content local bin64 directory $(IMAGENOWLOCALDIR6)\bin64, and entering inserverUR -status. A status message informs you if the service is not installed, started, or stopped.
My LDAP users are not added to Perceptive Content.
To find the cause of this error, verify the following information.
- The agent is installed and running.
- The settings in the inserverUR.ini file are correct.
- The user who set up the agent has the necessary security privileges.
- There are no error messages in the log files located in \inserver\log. If the User Replication Agent is installed on the same server as Perceptive Content Server, review the inserverUR_<date>.log file for error messages. If the User Replication Agent is installed remotely, review the inserver_<date>.log file instead.
- The user name is 40 characters or less. If the user name exceeds the maximum characters, the agent does not add the user to Perceptive Content as a user or a group member. Instead, the agent writes it to a log file and places that file in \inserver\log.
What happens to the agent when my LDAP server is down?
The agent cannot synchronize users while the LDAP server is down. After the LDAP server is back online, the agent updates the users at its next scheduled synchronization as specified by the ldap.sync.interval property in the inserverUR.ini file in the Perceptive Content shared etc directory $(IMAGENOWDIR6)\etc.
The agent added my users to Perceptive Content, but they are not members of the groups I specified.
Ensure that the group name exists in Perceptive Content Client and that it matches the group name or group DN in the LDAP directory exactly. Check the settings in your Group sections in the inserverUR.ini file to ensure they are correct, especially the group.member.login.attr property. The agent cannot add a Perceptive Manager or a Department Manager since those user roles already have security privileges.
My group filter is not working.
Check the settings in the inserverUR.ini file. Check each group section and verify that all filters used in the group settings are correct.
I cannot import my certificate into Perceptive Content to use TLS.
When you set up the User Replication Agent with TLS, check that the command line syntax is correct for importing your certificate. Also, verify that the certificate is valid and not expired and verify that you exported the certificate from the correct HTTP address.
I cannot bind to my LDAP server when using TLS.
Verify the status of the agent by opening a window that accepts command prompts. Navigate to \inserver\bin and enter inserverUR.exe -status. A status message informs you if the service is not installed up or down. If it is down, check for binding error messages written to the inserver and inserverUR log files in the Perceptive Content local log directory $(IMAGENOWLOCALDIR6)\log. Additionally, ensure that you made the necessary changes to your inserverUR.ini file in the Perceptive Content shared etc directory $(IMAGENOWDIR6)\etc and imported your certificates into Perceptive Content Server using the procedures in the "Set up User Replication Agent with TLS" section of this guide.
Log message “Failed to query LDAP server for members of group: <<LDAP user group>>. Error: Sizelimit exceeded” appears.
This message occurs when there are more than 500 users in an LDAP group. Some operating system versions in Windows and Linux cannot support more than 500 users in a group.
Log message “Failed to add user <<username> to group <<groupname>>” appears.
One of the causes for this error message is when the group name for a group section specified in the inserverUR.ini file does not have a corresponding group name in Perceptive Content. Add the group name to resolve this issue.
Log message “Failed to query LDAP server for members of group: <<groupname>>. Error: No such object” appears.
Verify that the group.dn property in the corresponding group section in inserverUR.ini has a valid DN.
Log message “Failed to bind to the LDAP server” appears.
Check and correct the following settings in the inserverUR.ini file:
- LDAP server hostname - ldap.server
- LDAP port - ldap.server.port
- LDAP login - ldap.login
- LDAP password - ldap.password