Not tried with Mid-Tier Carey, but I've tried connecting with the 7.1 user client to a 6.3p20 server and authentication failed.
Next step was then to simply de-install the client. With best regards, Robert Kern Siemens VDO Automotive AG SV IO IT BO ST Sodener Strasse 9 65824 Schwalbach, Germany Tel.: +49 (6196) 87-2546 Fax.: +49 (6196) 8779-2546 Mobile: +49 (170) 8522-515 mailto:[EMAIL PROTECTED] www.siemensvdo.com Siemens VDO Automotive AG: Chairman of the Supervisory Board: Hermann Requardt; Managing Board: Wolfgang Dehen, Chairman, President and Chief Executive Officer; Klaus Egger, Helmut Matschi, Reinhard Pinzer; Registered office: Regensburg, Germany; Commercial registry: Regensburg, HRB 10510 Important notice: This e-mail and any attachment thereof contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank you. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Thursday, September 06, 2007 2:28 PM To: [email protected] Subject: v7.1 Mid-Tier with v6.3 patch 20 ARS server... connection problems? All, Does anyone know of any issues with an ARS v6.3 patch 20 ARS server and the v7.1 Mid-tier? After a few hours of playing (fighting) with it... it appears that the Mid-Tier just will not authenticate against that patch level of the ARS server. (Well for me it will not and I have tried two Mid-Tier installs on separate hosts.) What I am seeing is the following: " Sep 6, 2007 8:13:24 AM - FINE (com.remedy.log.INTERNAL) : (Thread 11) com.remedy.arsys.goat.GoatException <init> Throw ARException - ERROR (623): Authentication failed; ERROR (623): Authentication failed; Sep 6, 2007 8:13:24 AM - FINE (com.remedy.log.INTERNAL) : (Thread 11) com.remedy.arsys.goat.GoatException <init> Throw Error - 9217 Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.DefaultAuthenticator redirectToLogin DefaultAuthenticator.redirectToLogin: url=/arsys/home Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet doThePost LoginServlet: Caught status 9388 Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.INTERNAL) : (Thread 11) com.remedy.arsys.goat.GoatException <init> Throw Error - 9388 Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet doLogin LoginServlet: Authentication status: 8 Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet authenticate LoginServlet: Authentication exception: ERROR (623): Authentication failed; Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet authenticate LoginServlet: Authenticating "USER_removed" against server "ARSServer_Removed" Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.DefaultAuthenticator getAuthenticatedCredentials DefaultAuthenticator: Using credentials from login page - "USER_removed" Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet getTargetURL LoginServlet: Target URL attribute = /arsys/home Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet doThePost LoginServlet: locale=en_US Sep 6, 2007 8:13:23 AM - FINE (com.remedy.log.SESSION) : (Thread 11) com.remedy.arsys.session.LoginServlet doThePost LoginServlet: url=https://"web_server_removed"/arsys/servlet/LoginServlet?null " When I point these v7.1 Mid-tier installs to a v7.0.1 (patch 3) ARS server then they allow the users to authenticate and appear to be working. Of course the rub is that the production server is v6.3 patch 20. I did not find any thing in the known issues ... but maybe I just have not found the correct pdf/ppt yet. Does anyone have an explanation for error 9388 means? ( It is not in the v7.1 error guide. GRRRRRR.) BTW: We really want support for Safari on the client end but I do not see it in the compatibility matrix. Oh.. now I see why it is not in the compatibility matrix... Ref: http://developer.bmc.com/jiveProd/bsdnDownload.jspa?categoryID=480&exter nalID=2053&attachID=389706 WhatsNewARS7_1-CMDB2_1-AIE7_1.ppt ( Slide 21 ) " Safari 3.0 support Not supported until Mac OSX 10.5 is released " Ugh.... now I have to go explain that to my director that he may have to upgrade his OS to be able to use Safari with Remedy. And that will only be useful after we figure out why the mid-tier client appears to not work with our v6.3 ARS server. (Sigh) I guess I have some time before the new Mac OS is released to figure this problem out. ( To bad this Safari information could not have been a note, or referenced in the compatibility matrix. The reference was to hard to find. ) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
