Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

[jeff m. <jcm...@je...>]

None that I know of. If other people want to take a crack at it.. please do.

jeff


On Jan 19, 2012, at 2:06 PM, Eric Wolf wrote:

> So are you saying there is no workaround?
> 
> On Thu, Jan 19, 2012 at 12:36 PM, jeff murphy <jcm...@je...> wrote:
> 
> On Jan 19, 2012, at 12:50 PM, Eric Wolf wrote:
> 
>> When I take identical login code from the working 7.5 installation and attempt to login to the 7.6.04 release, I get an RPC bind failure (ARERR 90).  If I use the exact credentials in the 7.5 user tool, I can login to the 7.6.04 installation.
>> 
>> Has this caused anyone else problems?  Am I on the right track in thinking I need to recompile the module for the 64 bit windows installation?
> 
> 
> Yes, this is an existing issue. If I take a stub C program that basically builds a control struct and sends it to ARVerifyUser() it works just fine (when compiled on a 64bit linux system). If I take that exact code and paste it into a Perl XS file, it fails with the RPC error (90 Can't Encode Arguments). I spent quite a bit of time looking into this. The BMC libraries embed the RPC libraries (instead of using the libc routines) so stepping into the function doesn't work.. so it's hard to judge exactly why it's unable to encode the RPC call. Basically you pass in the control struct and the RPC routine translates it to XDR. That's where it seems to be failing. I wasn't able to figure out what the exact issue is.. but for some reason perl + arlib + 64 bit has some inscrutable interaction that arlib + 64bit alone don't have.  
>