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

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

From: Eric W. <eri...@gm...> - 2012-01-19 17:50:49

Hi Everyone,

We're in the process of transitioning to a new release of Remedy.  Our
current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and
we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008
server.  The ARSPerl installation is built on a 64 bit Red Hat Linux
server, but compiled in 32 bit mode to resolve previous RPC translation
errors. I suspect this is rearing it's ugly head again in a more covert
manner.

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?

Thanks,

-Eric

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

From: jeff m. <jcm...@je...> - 2012-01-19 18:59:25

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.  

jeff

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

From: Eric W. <eri...@gm...> - 2012-01-19 19:07:09

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.
>
> jeff
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
>
>
> --
> Arsperl-users mailing list
> Ars...@li...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>



-- 
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must
learn to sail in high winds. --Aristotle Onassis

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

From: jeff m. <jcm...@je...> - 2012-01-19 19:14:48

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.  
>

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

From: <Con...@t-...> - 2012-01-19 19:16:27

Hi Eric,

normally it shouldn't be a problem to connect with a 7.5 API to a 7.6.4 Server. It sounds more like a network issue.

Just now I tested a ARSPerl compiled against 6.3 API and it connects without any issue to a 7.6.4 (Linux)-Server

Recompiling is IMHO definitly the wrong track.

KR Conny

________________________________
Von: Eric Wolf [mailto:eri...@gm...]
Gesendet: Donnerstag, 19. Januar 2012 18:50
An: ars...@li...
Betreff: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

Hi Everyone,

We're in the process of transitioning to a new release of Remedy.  Our current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008 server.  The ARSPerl installation is built on a 64 bit Red Hat Linux server, but compiled in 32 bit mode to resolve previous RPC translation errors. I suspect this is rearing it's ugly head again in a more covert manner.

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?

Thanks,

-Eric

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

From: Eric W. <eri...@gm...> - 2012-01-19 19:30:08

Well, I'm getting the ARERR 90 back.  Is that not indicative of a
connection?

Are all of your API libraries at matching bit levels? IE: is your linux
server 32 bit or 64 bit and does your corresponding connection match 32 or
64?

On Thu, Jan 19, 2012 at 12:41 PM, <Con...@t-...> wrote:

> **
> Hi Eric,
>
> normally it shouldn't be a problem to connect with a 7.5 API to a 7.6.4
> Server. It sounds more like a network issue.
>
> Just now I tested a ARSPerl compiled against 6.3 API and it connects
> without any issue to a 7.6.4 (Linux)-Server
>
> Recompiling is IMHO definitly the wrong track.
>
> KR Conny
>
>  ------------------------------
> *Von:* Eric Wolf [mailto:eri...@gm...]
> *Gesendet:* Donnerstag, 19. Januar 2012 18:50
> *An:* ars...@li...
> *Betreff:* [Arsperl-users] Transitioned AR Server, ARSPerl no longer
> connects.
>
> Hi Everyone,
>
> We're in the process of transitioning to a new release of Remedy.  Our
> current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and
> we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008
> server.  The ARSPerl installation is built on a 64 bit Red Hat Linux
> server, but compiled in 32 bit mode to resolve previous RPC translation
> errors. I suspect this is rearing it's ugly head again in a more covert
> manner.
>
> 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?
>
> Thanks,
>
> -Eric
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
>
>
> --
> Arsperl-users mailing list
> Ars...@li...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>



-- 
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must
learn to sail in high winds. --Aristotle Onassis

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

From: jeff m. <jcm...@je...> - 2012-01-19 19:36:18

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

> Well, I'm getting the ARERR 90 back.  Is that not indicative of a connection?


90 is "Cannot establish a network connection to the AR System server". The 64bit issue includes an additional bit of text explaining why it can't connect: "RPC: Can't encode arguments".

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

From: <Con...@t-...> - 2012-01-19 19:42:59

No, ARERR 90 is generated at the client-side to indicate connections problems. But it's a very generic error message.

All servers are 64 Bit. But ARSPerl is compiled as 32 Bit (6.3 wasn't even available as 64 Bit)

What you should try is:

If you're using portmapper
rpcinfo -t <your_ar_host> 390600

If you don't use portmapper
rpcinfo -t -n <tcp_port_of_ar_server> <your_ar_host> 390600

Normal Output looks like this

rpcinfo -t -n 2001 xyz.xxx.de 390600
program 390600 version 1 ready and waiting
program 390600 version 2 ready and waiting
program 390600 version 3 ready and waiting
program 390600 version 4 ready and waiting
program 390600 version 5 ready and waiting
program 390600 version 6 ready and waiting
program 390600 version 7 ready and waiting
program 390600 version 8 ready and waiting
program 390600 version 9 ready and waiting
program 390600 version 10 ready and waiting
program 390600 version 11 ready and waiting
program 390600 version 12 ready and waiting
program 390600 version 13 ready and waiting
program 390600 version 14 ready and waiting
program 390600 version 15 ready and waiting
program 390600 version 16 ready and waiting
program 390600 version 17 ready and waiting
program 390600 version 18 ready and waiting

If rpcinfo shows correct output, then you'll have to have a look at your ARSPerl install.

KR Conny

________________________________
Von: Eric Wolf [mailto:eri...@gm...]
Gesendet: Donnerstag, 19. Januar 2012 20:30
An: ARSperl User Discussion
Betreff: Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

Well, I'm getting the ARERR 90 back. Is that not indicative of a connection?

Are all of your API libraries at matching bit levels? IE: is your linux server 32 bit or 64 bit and does your corresponding connection match 32 or 64?

On Thu, Jan 19, 2012 at 12:41 PM, <Con...@t-...<mailto:Con...@t-...>> wrote:
Hi Eric,

normally it shouldn't be a problem to connect with a 7.5 API to a 7.6.4 Server. It sounds more like a network issue.

Just now I tested a ARSPerl compiled against 6.3 API and it connects without any issue to a 7.6.4 (Linux)-Server

Recompiling is IMHO definitly the wrong track.

KR Conny

________________________________
Von: Eric Wolf [mailto:eri...@gm...<mailto:eri...@gm...>]
Gesendet: Donnerstag, 19. Januar 2012 18:50
An: ars...@li...<mailto:ars...@li...>
Betreff: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

Hi Everyone,

We're in the process of transitioning to a new release of Remedy. Our current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008 server. The ARSPerl installation is built on a 64 bit Red Hat Linux server, but compiled in 32 bit mode to resolve previous RPC translation errors. I suspect this is rearing it's ugly head again in a more covert manner.

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?

Thanks,

-Eric

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

--
Arsperl-users mailing list
Ars...@li...<mailto:Ars...@li...>
https://lists.sourceforge.net/lists/listinfo/arsperl-users

--
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must learn to sail in high winds. --Aristotle Onassis

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

From: Eric W. <eri...@gm...> - 2012-01-19 19:54:01

Yeah, not having a problem getting normal output back from rpcinfo.  Now
I'm a little befuddled as to what to look at in the install.

On Thu, Jan 19, 2012 at 1:42 PM, <Con...@t-...> wrote:

> **
> No, ARERR 90 is generated at the client-side to indicate connections
> problems. But it's a very generic error message.
>
> All servers are 64 Bit. But ARSPerl is compiled as 32 Bit (6.3 wasn't even
> available as 64 Bit)
>
> What you should try is:
>
> If you're using portmapper
> rpcinfo -t <your_ar_host> 390600
>
> If you don't use portmapper
> rpcinfo -t -n <tcp_port_of_ar_server> <your_ar_host> 390600
>
> Normal Output looks like this
>
> rpcinfo -t -n 2001 xyz.xxx.de 390600
> program 390600 version 1 ready and waiting
> program 390600 version 2 ready and waiting
> program 390600 version 3 ready and waiting
> program 390600 version 4 ready and waiting
> program 390600 version 5 ready and waiting
> program 390600 version 6 ready and waiting
> program 390600 version 7 ready and waiting
> program 390600 version 8 ready and waiting
> program 390600 version 9 ready and waiting
> program 390600 version 10 ready and waiting
> program 390600 version 11 ready and waiting
> program 390600 version 12 ready and waiting
> program 390600 version 13 ready and waiting
> program 390600 version 14 ready and waiting
> program 390600 version 15 ready and waiting
> program 390600 version 16 ready and waiting
> program 390600 version 17 ready and waiting
> program 390600 version 18 ready and waiting
>
> If rpcinfo shows correct output, then you'll have to have a look at your
> ARSPerl install.
>
> KR Conny
>
>  ------------------------------
> *Von:* Eric Wolf [mailto:eri...@gm...]
> *Gesendet:* Donnerstag, 19. Januar 2012 20:30
> *An:* ARSperl User Discussion
> *Betreff:* Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer
> connects.
>
> Well, I'm getting the ARERR 90 back.  Is that not indicative of a
> connection?
>
> Are all of your API libraries at matching bit levels? IE: is your linux
> server 32 bit or 64 bit and does your corresponding connection match 32 or
> 64?
>
> On Thu, Jan 19, 2012 at 12:41 PM, <Con...@t-...> wrote:
>
>> **
>> Hi Eric,
>>
>> normally it shouldn't be a problem to connect with a 7.5 API to a 7.6.4
>> Server. It sounds more like a network issue.
>>
>> Just now I tested a ARSPerl compiled against 6.3 API and it connects
>> without any issue to a 7.6.4 (Linux)-Server
>>
>> Recompiling is IMHO definitly the wrong track.
>>
>> KR Conny
>>
>>  ------------------------------
>> *Von:* Eric Wolf [mailto:eri...@gm...]
>> *Gesendet:* Donnerstag, 19. Januar 2012 18:50
>> *An:* ars...@li...
>> *Betreff:* [Arsperl-users] Transitioned AR Server, ARSPerl no longer
>> connects.
>>
>>  Hi Everyone,
>>
>> We're in the process of transitioning to a new release of Remedy.  Our
>> current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and
>> we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008
>> server.  The ARSPerl installation is built on a 64 bit Red Hat Linux
>> server, but compiled in 32 bit mode to resolve previous RPC translation
>> errors. I suspect this is rearing it's ugly head again in a more covert
>> manner.
>>
>> 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?
>>
>> Thanks,
>>
>> -Eric
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>>
>>
>> --
>> Arsperl-users mailing list
>> Ars...@li...
>> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>>
>
>
>
> --
> Eric Wolf
> http://www.n5ebw.com "The Ramblings of a Crazy Man"
> We must free ourselves of the hope that the sea will ever rest. We must
> learn to sail in high winds. --Aristotle Onassis
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
>
>
> --
> Arsperl-users mailing list
> Ars...@li...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>



-- 
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must
learn to sail in high winds. --Aristotle Onassis

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

From: <Con...@t-...> - 2012-01-19 20:15:02

Next step is to use the driver programm to connect to the system. It should be located in <...>/api/src/driver/driver

The command sequence is

init
log
ver

This is just to prove the the api (7.5) is able to connect to the 7.6.4 server

KR Conny
________________________________
Von: Eric Wolf [mailto:eri...@gm...]
Gesendet: Donnerstag, 19. Januar 2012 20:54
An: ARSperl User Discussion
Betreff: Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

Yeah, not having a problem getting normal output back from rpcinfo. Now I'm a little befuddled as to what to look at in the install.

On Thu, Jan 19, 2012 at 1:42 PM, <Con...@t-...<mailto:Con...@t-...>> wrote:
No, ARERR 90 is generated at the client-side to indicate connections problems. But it's a very generic error message.

All servers are 64 Bit. But ARSPerl is compiled as 32 Bit (6.3 wasn't even available as 64 Bit)

What you should try is:

If you're using portmapper
rpcinfo -t <your_ar_host> 390600

If you don't use portmapper
rpcinfo -t -n <tcp_port_of_ar_server> <your_ar_host> 390600

Normal Output looks like this

rpcinfo -t -n 2001 xyz.xxx.de<http://xyz.xxx.de> 390600
program 390600 version 1 ready and waiting
program 390600 version 2 ready and waiting
program 390600 version 3 ready and waiting
program 390600 version 4 ready and waiting
program 390600 version 5 ready and waiting
program 390600 version 6 ready and waiting
program 390600 version 7 ready and waiting
program 390600 version 8 ready and waiting
program 390600 version 9 ready and waiting
program 390600 version 10 ready and waiting
program 390600 version 11 ready and waiting
program 390600 version 12 ready and waiting
program 390600 version 13 ready and waiting
program 390600 version 14 ready and waiting
program 390600 version 15 ready and waiting
program 390600 version 16 ready and waiting
program 390600 version 17 ready and waiting
program 390600 version 18 ready and waiting

If rpcinfo shows correct output, then you'll have to have a look at your ARSPerl install.

KR Conny

________________________________
Von: Eric Wolf [mailto:eri...@gm...<mailto:eri...@gm...>]
Gesendet: Donnerstag, 19. Januar 2012 20:30
An: ARSperl User Discussion
Betreff: Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

Well, I'm getting the ARERR 90 back. Is that not indicative of a connection?

Are all of your API libraries at matching bit levels? IE: is your linux server 32 bit or 64 bit and does your corresponding connection match 32 or 64?

On Thu, Jan 19, 2012 at 12:41 PM, <Con...@t-...<mailto:Con...@t-...>> wrote:
Hi Eric,

normally it shouldn't be a problem to connect with a 7.5 API to a 7.6.4 Server. It sounds more like a network issue.

Just now I tested a ARSPerl compiled against 6.3 API and it connects without any issue to a 7.6.4 (Linux)-Server

Recompiling is IMHO definitly the wrong track.

KR Conny

________________________________
Von: Eric Wolf [mailto:eri...@gm...<mailto:eri...@gm...>]
Gesendet: Donnerstag, 19. Januar 2012 18:50
An: ars...@li...<mailto:ars...@li...>
Betreff: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

Hi Everyone,

We're in the process of transitioning to a new release of Remedy. Our current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008 server. The ARSPerl installation is built on a 64 bit Red Hat Linux server, but compiled in 32 bit mode to resolve previous RPC translation errors. I suspect this is rearing it's ugly head again in a more covert manner.

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?

Thanks,

-Eric

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

--
Arsperl-users mailing list
Ars...@li...<mailto:Ars...@li...>
https://lists.sourceforge.net/lists/listinfo/arsperl-users

--
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must learn to sail in high winds. --Aristotle Onassis

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

--
Arsperl-users mailing list
Ars...@li...<mailto:Ars...@li...>
https://lists.sourceforge.net/lists/listinfo/arsperl-users

--
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must learn to sail in high winds. --Aristotle Onassis

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

From: Eric W. <eri...@gm...> - 2012-01-19 22:23:00

In the control record for logging in, I have the following after typing
"log"

Control record:
   Authentication string () :
   User name () :
   Password () :
   Locale[.charSet] () :
   Time zone () :
   Server () :

What is the purpose of "Authentication string", and how do I specify a TCP
and RPC port in this?

Thanks for all of your help with this by the way, I haven't had to go this
in depth with a connection problem before.

-Eric

On Thu, Jan 19, 2012 at 2:02 PM, <Con...@t-...> wrote:

> **
> Next step is to use the driver programm to connect to the system. It
> should be located in <...>/api/src/driver/driver
>
> The command sequence is
>
> init
> log
> ver
>
> This is just to prove the the api (7.5) is able to connect to the 7.6.4
> server
>
> KR Conny
>  ------------------------------
> *Von:* Eric Wolf [mailto:eri...@gm...]
> *Gesendet:* Donnerstag, 19. Januar 2012 20:54
>
> *An:* ARSperl User Discussion
> *Betreff:* Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer
> connects.
>
> Yeah, not having a problem getting normal output back from rpcinfo.  Now
> I'm a little befuddled as to what to look at in the install.
>
> On Thu, Jan 19, 2012 at 1:42 PM, <Con...@t-...> wrote:
>
>> **
>> No, ARERR 90 is generated at the client-side to indicate connections
>> problems. But it's a very generic error message.
>>
>> All servers are 64 Bit. But ARSPerl is compiled as 32 Bit (6.3 wasn't
>> even available as 64 Bit)
>>
>> What you should try is:
>>
>> If you're using portmapper
>> rpcinfo -t <your_ar_host> 390600
>>
>> If you don't use portmapper
>> rpcinfo -t -n <tcp_port_of_ar_server> <your_ar_host> 390600
>>
>> Normal Output looks like this
>>
>> rpcinfo -t -n 2001 xyz.xxx.de 390600
>> program 390600 version 1 ready and waiting
>> program 390600 version 2 ready and waiting
>> program 390600 version 3 ready and waiting
>> program 390600 version 4 ready and waiting
>> program 390600 version 5 ready and waiting
>> program 390600 version 6 ready and waiting
>> program 390600 version 7 ready and waiting
>> program 390600 version 8 ready and waiting
>> program 390600 version 9 ready and waiting
>> program 390600 version 10 ready and waiting
>> program 390600 version 11 ready and waiting
>> program 390600 version 12 ready and waiting
>> program 390600 version 13 ready and waiting
>> program 390600 version 14 ready and waiting
>> program 390600 version 15 ready and waiting
>> program 390600 version 16 ready and waiting
>> program 390600 version 17 ready and waiting
>> program 390600 version 18 ready and waiting
>>
>> If rpcinfo shows correct output, then you'll have to have a look at your
>> ARSPerl install.
>>
>> KR Conny
>>
>>  ------------------------------
>>  *Von:* Eric Wolf [mailto:eri...@gm...]
>> *Gesendet:* Donnerstag, 19. Januar 2012 20:30
>> *An:* ARSperl User Discussion
>> *Betreff:* Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer
>> connects.
>>
>>  Well, I'm getting the ARERR 90 back.  Is that not indicative of a
>> connection?
>>
>> Are all of your API libraries at matching bit levels? IE: is your linux
>> server 32 bit or 64 bit and does your corresponding connection match 32 or
>> 64?
>>
>> On Thu, Jan 19, 2012 at 12:41 PM, <Con...@t-...> wrote:
>>
>>> **
>>> Hi Eric,
>>>
>>> normally it shouldn't be a problem to connect with a 7.5 API to a 7.6.4
>>> Server. It sounds more like a network issue.
>>>
>>> Just now I tested a ARSPerl compiled against 6.3 API and it connects
>>> without any issue to a 7.6.4 (Linux)-Server
>>>
>>> Recompiling is IMHO definitly the wrong track.
>>>
>>> KR Conny
>>>
>>>  ------------------------------
>>> *Von:* Eric Wolf [mailto:eri...@gm...]
>>> *Gesendet:* Donnerstag, 19. Januar 2012 18:50
>>> *An:* ars...@li...
>>> *Betreff:* [Arsperl-users] Transitioned AR Server, ARSPerl no longer
>>> connects.
>>>
>>>  Hi Everyone,
>>>
>>> We're in the process of transitioning to a new release of Remedy.  Our
>>> current install level is 7.5 Patch 6 on a 32 bit Windows 2003 server, and
>>> we are moving to a 7.6.04 SP2 installation on a 64 bit Windows 2008
>>> server.  The ARSPerl installation is built on a 64 bit Red Hat Linux
>>> server, but compiled in 32 bit mode to resolve previous RPC translation
>>> errors. I suspect this is rearing it's ugly head again in a more covert
>>> manner.
>>>
>>> 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?
>>>
>>> Thanks,
>>>
>>> -Eric
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>>
>>>
>>> --
>>> Arsperl-users mailing list
>>> Ars...@li...
>>> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>>>
>>
>>
>>
>> --
>> Eric Wolf
>> http://www.n5ebw.com "The Ramblings of a Crazy Man"
>> We must free ourselves of the hope that the sea will ever rest. We must
>> learn to sail in high winds. --Aristotle Onassis
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>>
>>
>> --
>> Arsperl-users mailing list
>> Ars...@li...
>> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>>
>
>
>
> --
> Eric Wolf
> http://www.n5ebw.com "The Ramblings of a Crazy Man"
> We must free ourselves of the hope that the sea will ever rest. We must
> learn to sail in high winds. --Aristotle Onassis
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
>
>
> --
> Arsperl-users mailing list
> Ars...@li...
> https://lists.sourceforge.net/lists/listinfo/arsperl-users
>



-- 
Eric Wolf
http://www.n5ebw.com "The Ramblings of a Crazy Man"
We must free ourselves of the hope that the sea will ever rest. We must
learn to sail in high winds. --Aristotle Onassis

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

From: <Con...@t-...> - 2012-01-20 06:53:39

You only have to specify User name, Password and Server. The other fields can be left empty. For setting the port you can use the ssp command. First field is tcp port, second one rpc port wich can be also left empty.

KR Conny

________________________________
Von: Eric Wolf [mailto:eri...@gm...]
Gesendet: Donnerstag, 19. Januar 2012 23:23
An: ARSperl User Discussion
Betreff: Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.

In the control record for logging in, I have the following after typing "log"

Control record:
Authentication string () :
User name () :
Password () :
Locale[.charSet] () :
Time zone () :
Server () :

What is the purpose of "Authentication string", and how do I specify a TCP and RPC port in this?

Thanks for all of your help with this by the way, I haven't had to go this in depth with a connection problem before.

-Eric

On Thu, Jan 19, 2012 at 2:02 PM, <Con...@t-...<mailto:Con...@t-...>> wrote:
Next step is to use the driver programm to connect to the system. It should be located in <...>/api/src/driver/driver

The command sequence is

init
log
ver

This is just to prove the the api (7.5) is able to connect to the 7.6.4 server

KR Conny
________________________________
Von: Eric Wolf [mailto:eri...@gm...<mailto:eri...@gm...>]
Gesendet: Donnerstag, 19. Januar 2012 20:54

An: ARSperl User Discussion
Betreff: Re: [Arsperl-users] Transitioned AR Server, ARSPerl no longer connects.