We have created users in the sec admin tool that have been added to LBI. While using the synchronize tool on LBI I get an error which basically is asking us to increase the page size on ADAM.
However when we do this we running into this error:
ldap policy: show values *** Error: ldap_search of ldapAdminLimits failed with 0x20(32 (No Such Object). Ldap extended error message is 0000208D: NameErr: DSID-031521D2, problem 2001 (N O_OBJECT), data 0, best match of: 'CN=Configuration,CN={1EB821E1-D8B9-4AF0-8D8D-052913263DF4}' Win32 error returned is 0x208d(Directory object not found.) )
Anybody seen this error. What can we do to resolve this?
tia,
Ruma.
Try this on your ADAM server to increase the maxpagesize from 1000 to 5000. :\WINDOWS\ADAM>dsmgmt dsmgmt: LDAP Policies ldap policy: connections server connections: set creds [domain] [user] * Please enter password for [domain]\[user]: ******** server connections: connect to server localhost:389 Binding to localhost:389 as [domain]\[user]... Connected to localhost:389 as [domain]\[user]. server connections: quit ldap policy: show values Policy Current(New) MaxPoolThreads 4 MaxDatagramRecv 4096 MaxReceiveBuffer 10485760 InitRecvTimeout 120 MaxConnections 5000 MaxConnIdleTime 900 MaxPageSize 1000 MaxQueryDuration 120 MaxTempTableSize 10000 MaxResultSetSize 262144 MaxNotificationPerConn 5 MaxValRange 0 ldap policy: set maxpagesize to 5000 ldap policy: commit changes ldap policy: show values Policy Current(New) MaxPoolThreads 4 MaxDatagramRecv 4096 MaxReceiveBuffer 10485760 InitRecvTimeout 120 MaxConnections 5000 MaxConnIdleTime 900 MaxPageSize 5000 MaxQueryDuration 120 MaxTempTableSize 10000 MaxResultSetSize 262144 MaxNotificationPerConn 5 MaxValRange 0 ldap policy: quit dsmgt: quit
Edit your LAWDIR\system\RMApiInit.properties file and increase the default.com.lawson.lawrm.MaxQueryResults=5000 if it's not already set to 5000.
You will need to bounce lawson and adam servers.
Thanks Jimmy. we were doing this whole process when we ran into the issue. After 2 days of investigation we found out that ADAM was missing a container(do not know what this exactly means) but microsoft is helping to resolve this issue.
Thanks.