Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Security
Lawson Security: "LDAP: error code 53 - Unwilling To Perform"
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
224
Members:
0
Total:
224
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Security
Lawson Security: "LDAP: error code 53 - Unwilling To Perform"
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Rodney
Basic Member
Posts: 7
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
chad208
Advanced Member
Posts: 25
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
Posts: 7
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!
chad208
Advanced Member
Posts: 25
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
Posts: 479
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
Posts: 7
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
Posts: 479
11/12/2008 6:19 PM
I'll see if I can find it this evening.
Kwane
You are not authorized to post a reply.