I have implemented AREA LDAP integration for a client on ARS 7.1 patch 001. However the AREA LDAP plugin functionality appears to be very unstable. Initially I am able to login with my corporate network login successfully using AREA LDAP (the arplugin.log proves that), however whenever I restart Remedy and try to log on again, I get the standard ARERR 623 (Authentication failed). It takes several restarts of Remedy to get it working again only for it to not work again after another Remedy restart. The most difficult aspect of this issue is that when AREA LDAP is not working, the arplugin.log doees not capture any pertinent AREA LDAP activity to help troubleshoot it(it doesn't capture the failed authentication attempt when AREA LDAP is not working). Has anyone seen any behavior like this before??

have you checked the 7.1 patch002 release notes to see if what you're seeing has been addressed?

Matt,

Right now I'm still on patch 001. So far Remedy support has not suggested that I move to patch 002. Right now what happens, when whenever I restart Remedy, AREA LDAP fails. When I restart it again, it is restored and back and forth and so on. I'm just looking for any insight about ldap plugin stability when running multiple plugins.

I just upgraded to patch 002 and am still seeing the same behavior. Right now, whenever I restart Remedy, AREA LDAP fails and when I restart it again, it works again and so on. I do have 2 ARDBC plugin aliases implemented to handle the cross domain support of a CTM:People Import interface. It seems that the AREA LDAP plugin may be impacted by my multiple ARDBC plugin setup (whenever I disable the additional plugin aliases, AREA LDAP works 100% of the time)

I've attached two sets of debug log files (one when it is working and one when it is not working) - Check the arapi log files and look at the GetServerInfo (GSI) function calls. That is where the error is taking place. Any insight on this would be a godsend

Sorry for not the posting this sooner, but the root cause turned out to be that a plugin port number was not specified for the original or base ARDBC plugin. I had thought you only needed plugin ports for the just the plugin aliases you create and not the base plugin but it turns out that you do indeed need a plugin port for the base plugin as well.