If you upgraded remedy, and your perl scripts are expecting the remedy libs in a certain location/version, and they are no longer available in that format, arsperl will not work. Upgrade arsperl, compile it against the version of the api's available on your server. An alternative approach would be to place the 6.3 api somewhere, then set the ld_library_path so it reaches the 6.3 api prior to the 7.1 api in the sessions where you use arsperl.
Axton Grams On Tue, Oct 21, 2008 at 8:02 AM, Urban, Robert (, externer Mitarbeiter) <[EMAIL PROTECTED]> wrote: > Hi Folks, > > on a Solaris10 (Niagara2) system we upgraded from v6.3p20 to v7.1p004. Now > I can no longer (using arsperl "ars_Login()") get an API connection to > "localhost". If I explicitly use the network-name of the system I can > establish a connection. Has anyone else seen this? We always configure > ars to use a specific port (3311), and a telnet to this port is successful, > which indicates that the connection is getting as far as the > application-level. > Most network-applications I've seen explicitly provide a configuration > parameter to control which interfaces an application will "listen" on. > I know of no such parameter for ars. > > Any ideas? > > Rob Urban > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
