• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Security

Lawson Security: "LDAP: error code 53 - Unwilling To Perform"

 6 Replies
 0 Subscribed to this topic
 16 Subscribed to this forum
Sort:
Author
Messages
Rodney
Basic Member Send Private Message
Posts: 7
Basic Member
11/10/2008 4:10 PM
Is anyone receiving this message in the LSA client or on the server when making any security changes?   We were told by the GSC this is related to the size of our security classes/roles, yet told by their trainers that there is no size limit.  

Anyone else having (or had) this problem?   If so, how did you fix it.  It it simply a configuration change on your server?

Thanks,
Rodney
Deleted User
New Member Send Private Message
Posts: 0
New Member
11/10/2008 4:20 PM
We did receive that message during our load testing.  I can not remember exactly which change exactly fixed our issue, however, we implemented the following changes during our troubleshooting to resolve the issue.

TDS/LDAP  Modify Max Transactions to from   20 --> 1000
TDS/LDAP  Modify user connection timeout    300 --> 15
TDS/LDAP  Modify concurrent paged searches to   25
TDS/LDAP Modify paged searches idle timeout from  300 --> 30
TDS/LDAP   Modify connections from    15 --> 50
TDS/LDAP  Idle timeout limit (in seconds)    300 —> 15
TDS/LDAP  Number of database connections   75
WAS   Modify Thread Pool Max Transactions   20 --> 50
Rodney
Basic Member Send Private Message
Posts: 7
Basic Member
11/10/2008 5:30 PM
Thanks Chad. For the TDS/LDAP changes are you referring to the ibmslapd.conf file?

What directory/file are you referring to for the WAS changes? Thanks!
Deleted User
New Member Send Private Message
Posts: 0
New Member
11/10/2008 6:00 PM
We made the WAS changes via the admin console.  In addition, the LDAP changes were also made via the LDAP admin console.
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
11/11/2008 2:42 PM
There is no size limit, but lase loads ALOT of stuff at startup time, which could cause the LDAP server to run out of cache, and do odd things.

Also, check your version. This issue was a HUGE problem in certain patch levels of 9.0.0.3, and early 9.0.0.4. There is a patch for it, as I was at one of the clients it was originally written for.

Other than that, Chad's got a great handle on some of the settings you might look at changing.

Kwane
954.547.7210

Rodney
Basic Member Send Private Message
Posts: 7
Basic Member
11/12/2008 2:12 PM
Thanks Kwane.  Do you know which patch that would be?   Lawson support seems to have no knowledge of this error or any patch that would fix it.   They are in troubleshoot mode right now with the anticipation that this will take a long time to analyze, change and correct.

Thanks for the help.
Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
11/12/2008 6:19 PM
I'll see if I can find it this evening.

Kwane