Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Oct 18, 2021 5:02:49 AM
Apr 23, 2018 7:23:58 AM
An existing User Directory Connector (UDC) stopped working.
The following error is displayed:
The User Directory Connector (UDC) is not configured because the following error occurred. Setting up connection to LDAP root node failed. Check log file
Configuring an identical connector with the same parameters on another server is working fine.
When starting a sync, the following exception is thrown in the User Repository logs:
Repository.UserDirectoryConnectors.LDAP.GenericLDAP.GenerateUserQuery(String[] toFilterOn)?? at Repository.UserDirectoryConnectors.LDAP.GenericLDAP.SyncUsers(String[] usersToFilterOn)?? at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)?? at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)????Exception rethrown at [0]: ?? at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)?? at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed,
LDAP filter strings are stored for UDC. If the LDAP filter is removed from the database (by using pgadmin, for example), leaving the string as a null value rather than an empty string, the Qlik Sense Services will not be able to correctly interact with the UDC anymore.
Hi Chetan,
Below is LDAP filter field.
(&(objectClass=user)(memberOf=CN=Qlik_Users,OU=BI_Users,DC=ultimatix,DC=net))
Please arrange SPOC and screen sharing session for above prod issue as this is being escalated by business users.
Thanks.