Joe, Mark, et al

Thanks for your input. I'll confirm the AREA plugin is being loaded and see if 
there are indicators for errors. 

--
Shyam




________________________________
From: Joe D'Souza <jdso...@shyle.net>
To: arslist@ARSLIST.ORG
Sent: Wed, April 21, 2010 10:02:18 AM
Subject: Re: AREA LDAP issue after upgrading to AR Server 7.1.0 Patch 9 upgrade

** 
Shyam,
 
That's the same 
thing I would ask that Mark did. It appears as though the AREA plugin is not 
being called at all in the logs if that is all you see in your plugin log 
file.
 
Joe
-----Original Message-----
>From: Action Request System 
>  discussion list(ARSList) [mailto:arsl...@arslist.org]on Behalf Of 
> Walters, Mark
>Sent: Wednesday, April 21, 2010 10:21 
>  AM
>To: arslist@ARSLIST.ORG
>Subject: Re: AREA LDAP issue 
>  after upgrading to AR Server 7.1.0 Patch 9 upgrade
>
>** 
>  
>  > 
>Are 
>  there any entries from the AREA plugin at all?  Are you sure it’s being 
>  loaded?
> 
>Mark
> 
>From:Action 
>  Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On 
>  Behalf Of Shyam Attavar
>Sent: 21 April 2010 15:19
>To: >  arslist@ARSLIST.ORG
>Subject: Re: AREA LDAP issue after upgrading to 
>  AR Server 7.1.0 Patch 9 upgrade
> 
>** 
>I have set the log 
>  level to Finest for plugin logs and I only see the following entries... I 
>  don't see any failures in the log.
>
><PLGN> <TID: 
>  56671136> <RPC ID: 0000000110> <Queue: 
>  ARDBC     > <Client-RPC: 390695> /* Wed Apr 21 
>  2010 06:59:12.9027 */+GLEWF 
>  ARDBCGetListEntryWithFields      -- vendor 
>  REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin 
>  Setttings
><PLGN> <TID: 56671136> <RPC ID: 0000000110> 
>  <Queue: ARDBC     > <Client-RPC: 390695> /* 
>  Wed Apr 21 2010 06:59:12.9027 
>  */-GLEWF                               
>  OK
><PLGN> <TID: 56671136> <RPC ID: 0000000111> <Queue: 
>  ARDBC     > <Client-RPC: 390695> /* Wed Apr 21 
>  2010 06:59:12.9030 */+CT    
>  ARDBCCommitTransaction           
>  -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION
><PLGN> <TID: 
>  56671136> <RPC ID: 0000000111> <Queue: 
>  ARDBC     > <Client-RPC: 390695> /* Wed Apr 21 
>  2010 06:59:12.9030 
>  */-CT                                  
>  OK
><PLGN> <TID: 56671136> <RPC ID: 0000000112> <Queue: 
>  ARDBC     > <Client-RPC: 390695> /* Wed Apr 21 
>  2010 06:59:13.0009 */+GLEWF 
>  ARDBCGetListEntryWithFields      -- vendor 
>  REMEDY.ARDBC.SERVER.ADMINISTRATION table Server Info Plugin 
>  Setttings
><PLGN> <TID: 56671136> <RPC ID: 0000000112> 
>  <Queue: ARDBC     > <Client-RPC: 390695> /* 
>  Wed Apr 21 2010 06:59:13.0010 
>  */-GLEWF                               
>  OK
><PLGN> <TID: 56671136> <RPC ID: 0000000113> <Queue: 
>  ARDBC     > <Client-RPC: 390695> /* Wed Apr 21 
>  2010 06:59:13.0027 */+CT    
>  ARDBCCommitTransaction           
>  -- vendor REMEDY.ARDBC.SERVER.ADMINISTRATION
><PLGN> <TID: 
>  56671136> <RPC ID: 0000000113> <Queue: 
>  ARDBC     > <Client-RPC: 390695> /* Wed Apr 21 
>  2010 06:59:13.0028 
>  */-CT                                  
>  OK
>
>I do see the 
>  following in aruser.log:
>
> LOGIN 
>  FAILED   loginid   (password)
>
>I also see the 
>  following in arapi.log during log-in time:
>
><API > <TID: 
>  0089148320> <RPC ID: 0000015023> <Queue: 
>  Fast      > <Client-RPC: 390620   
>  > <USER: loginid 
>                                        
>  > /* Wed Apr 21 2010 07:15:11.5996 */+GSI    ARGetServerInfo 
>  -- as user 436557 from Remedy User (protocol 13) at IP address 
>  ipaddress
><API > <TID: 0089148320> <RPC ID: 0000015023> 
>  <Queue: Fast      > <Client-RPC: 
>  390620   > <USER: loginid 
>                                        
>  > /* Wed Apr 21 2010 07:15:11.6036 
>  */-GSI              
>  FAIL
>
>But nothing in any 
>  of the logs indicate what could be causing the authentication 
>  failure.
>
>Any other configurations to 
>  check?
>
>Thanks,
>--
>Shyam
>
________________________________
 
>From:Joe D'Souza 
>  <jdso...@shyle.net>
>To: arslist@ARSLIST.ORG
>Sent: >  Tue, April 20, 2010 6:31:17 PM
>Subject: Re: AREA LDAP issue after 
>  upgrading to AR Server 7.1.0 Patch 9 upgrade
>
>** 
>Shyam,
> 
>Enable the 
>  plugin log and set it to Fine and see what you get when you are trying to 
>  authenticate using the plugin..
> 
>Joe
>-----Original 
>>    Message-----
>>From: Action Request System discussion list(ARSList) 
>>    [mailto:arsl...@arslist.org]on Behalf Of Shyam 
>>    Attavar
>>Sent: Tuesday, April 20, 2010 7:49 PM
>>To: >>    arslist@ARSLIST.ORG
>>Subject: AREA LDAP issue after upgrading to AR 
>>    Server 7.1.0 Patch 9 upgrade
>>** 
>>Dear Listers,
>>
>>We 
>>    upgraded our test environment from AR Server 7.1.0 Patch 006 to Patch 
>> 009. 
>>    As part of the upgrade we upgraded the AREA LDAP plugin as well. After 
>> the 
>>    upgrade, we are unable to authenticate against LDAP. We can login to the 
>>    system by setting a local password in the user form. I have reconfigured 
>> the 
>>    AREA LDAP entries from the AR System Administration Console, but unable 
>> to 
>>    resolve the issue.
>>
>>Anyone else seen this issue after upgrading to AR 
>>    Server 7.1.0 Patch 009? if so, how were you able to resolve the 
>>    issue?
>>
>>Environment:
>>AR Server on RHEL 
>>Oracle 10gR4 on RHEL 
>> 
>>
>>Thanks in 
>>    advance,
>>--
>>Shyam_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to