Karthick,
Is the AR server able to access the LDAP server? Use the ldap.exe from the AR Server and see if it works on that. Does the bind user have any double byte characters for a password? There used to be (and I think there still is) an issue with the AR Server not able to authenticate users that have double byte characters for a password. These are the two things that I can think of from the top of my head with the absence of detailed errors in the arjavaplugin log. Joe _____ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Karthick S Sent: Wednesday, April 10, 2013 9:49 AM To: arslist@ARSLIST.ORG Subject: Re: AD Integration ** Plugin Log: <PLGN> <TID: 032312> <RPC ID: 0000000108> <Queue: ARDBC > <Client-RPC: 390695> /* Wed Apr 10 2013 15:07:56.9240 */-GE OK <PLGN> <TID: 032312> <RPC ID: 0000000109> <Queue: ARDBC > <Client-RPC: 390695> /* Wed Apr 10 2013 15:07:56.9390 */+CT ARDBCCommitTransaction -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION <PLGN> <TID: 032312> <RPC ID: 0000000109> <Queue: ARDBC > <Client-RPC: 390695> /* Wed Apr 10 2013 15:07:56.9390 */-CT OK <PLGN> <TID: 032844> <RPC ID: 0000000110> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:18.7050 */+VL AREAVerifyLoginCallback -- user sundararajan <PLGN> <TID: 032844> <RPC ID: 0000000110> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:18.7050 */-VL FAIL <PLGN> <TID: 032844> <RPC ID: 0000000111> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:29.8460 */+VL AREAVerifyLoginCallback -- user ali\sundararajan <PLGN> <TID: 032844> <RPC ID: 0000000111> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:29.8460 */-VL FAIL <PLGN> <TID: 032844> <RPC ID: 0000000112> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:45.9870 */+VL AREAVerifyLoginCallback -- user Sundararajan@ali.local <PLGN> <TID: 032844> <RPC ID: 0000000112> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:45.9870 */-VL FAIL <PLGN> <TID: 032844> <RPC ID: 0000000113> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:51.7840 */+VL AREAVerifyLoginCallback -- user Sundararajan@ali.local <PLGN> <TID: 032844> <RPC ID: 0000000113> <Queue: AREA > <Client-RPC: 390695> /* Wed Apr 10 2013 15:08:51.7840 */-VL FAIL <PLGN> <TID: 032312> <RPC ID: 0000000114> <Queue: ARDBC > <Client-RPC: 390695> /* Wed Apr 10 2013 15:09:18.5340 */+GLEWF ARDBCGetListEntryWithFields -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Form I have Give the RPC Program number correct and even checked the cross reference blank password, but still nothing happening. On Wed, Apr 10, 2013 at 11:45 PM, Hullule, Kiran <kiran_hull...@bmc.com> wrote: ** What does your arplugin log shows for +VL (VerifyLoginCallBack) call, invalid credential? Found user but password bad? Invalid bind user? Invalid bind password? User not found? I am sure you will see something useful. Make sure you have 390695 set under EA tab for external authentication rpc socket also cross reference blank password is checked . From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Karthick S Sent: Wednesday, April 10, 2013 7:12 PM To: arslist@ARSLIST.ORG Subject: AD Integration ** Hi All, I have configured AREA LDAP and i have verified the LDAP connection through ldap.exe, the connection was established. After configured the AREA form, I have updated the EA tab in Server information, still i am unable to achieve AD integration. Please help me on this. -- Thanks and Regards, Karthick S _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
