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:[email protected]] Gesendet: Donnerstag, 19. Januar 2012 18:50 An: [email protected] 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 [email protected] https://lists.sourceforge.net/lists/listinfo/arsperl-users
