hi cdtj
the issue u mentioned here is the same which we faced also for our one of
the client who uses sdm heavily.
Sdm was 12.6 . We added another webengine also to divide the users load as
there were huge login session at a time ...Approx 200+ on each webengine .
...But still the issue didn't solve and users were unable to login or was
taking long time to login...However those who already logged in can able to
do work .
We multiple times recycle the service sometimes it fixed sometimes takes
time..Later on we remove eem authentication and give open access to all....
After that we came to.knoe that the problem is with ldap authentication .
As the sdmlogin method is like once the first user not login to interface
the second one will not login until the first one login ....N so on.....As
it work on serially login method.
However we found on eem that there was one forest was not configured which
causes the issue.. how ever we fixed it...And sdm was perfect for somedays
with eem authentication .
But after some days same thing was happening again.and when we remove eem
it got ok....We were in a big problem during those days as CA was also not
supporting as the sdm 12.6 is outdated.
And we cannot leave this on open access..Then later on we open a case on
Microsoft Windows to look into windows patch and apply necessary patch if
needed as the OS was 2008. Mircorsoft also advised us to update perl58.dll
file of sdm directory . We somehow tried hard to.get the support of CA on
this and finally succeeeded and got.this.
After this our issue resolved permanently .
So I suggest to.first look into it eem and check whether any forest is
showing cross sign or not..Try to update it with latest password if not
configured.
Also try to use open access for all role so then u can sure where is there
problem exactly.
.
On 20-Apr-2017 1:06 am, "cdtj" <communityadmin@communities-mail.ca.com>