Eric, I can empathize. Ours failed, too. However, our environment is Windows 2003/SQL Server. PROD ARS 6.3 P18 --> P21 File Replacement Method Failed (followed special instructions in readme for upgrading from P19 or older) PROBLEM: Could not log into Remedy at all. ERRORS: After restarting ARS service, we received: Sat Mar 10 02:04:21 2007 390695 : An error has occurred while loading a plug-in. (ARERR 8756) Sat Mar 10 02:04:21 2007 WebService.dll: The specified module could not be found. RPC Program Not Registered (yes db was running and absolutely no other error in the arerror.log than the one above) ...and "AR System ONCRPC Port Mapper encountered a Problem and Needed to Close" which I assume was related to the message directly above. BACK OUT: We had to back out. Nothing we did would allow us to connect to Remedy. We stopped services and replaced with original files. Server came back up on P18. WORKAROUND: Decision was made to run the installer on Prod as we did in DEV. In Dev we had went from ARS 6.3 P18--> P20 using the installer because of all of the concern about missing files. When P21 came out we did the file repl method P20 -->P21 in DEV and that worked. So... This combination worked on PROD.. Run installer on ARS 6.3 P18 --> P20. File repl P20-->P21. Success Run Flashboard ARS 6.3 P20 Installer. Success Run Email 6.3 P21 Installer. Success RESULT: Production is UP on ARS 6.3 P21, FB P20, Email P21, MidTier 7.0.01 P1 with special FB fix. All errors originally reported above are no longer occurring. QUESTION: Anyone else attempt a file repl method from a patch 19 or lower than 20 to P21 and succeed? Thanks in advance, Michelle ________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Cleereman (IT) Sent: Friday, March 09, 2007 3:43 PM To: [email protected] Subject: Problems Applying ARServer 6.3 Patch 21 on Production Server ** Hi All, Under Aix 5.2, Oracle 9.2.0.4.0 (local database), we've used the manual copy method to install ARServer 6.3 Patch 21. We are using a script to execute this, so the manual install has been identical on all three servers. This worked fine on DEV and QC. On PROD, we see the following lines echoed to CON when trying to run "arsystem start" after the patch has been applied: (ARNOTE 0) Server indicates that it's up. (ARNOTE 0) Server (pid:18403474) died with 0. Tried 4 restarts in 30 seconds. I give up... The pid varies, and the ARError.Log does not indicate why the Server dies. 9 out of 10 times, it is actually dead. The other 1 of 10 restarts, the CON indicates it's death, but it's still running, and able to be connected to by clients. If the patch is backed out, the previous unpatched 6.3 works fine. We've patched and unpatched this several times, with the same results. Our Unix Admins and DBAs have verified that the JDKs, DB, and OS are all patched to the same levels no all three servers. We've compared the files paths, sizes, permissions, and ownerships of the patched files on all three servers and they match. We've also compared the ar.conf, armonitor.conf, etc... We initially thought this may be an issue with TSM, as we backup the file system on PROD, but not DEV or QC. We had Production Control kill off the backups, and tried it again. Same results. If anyone has any thoughts on this, we'd much appreciate them. Eric Cleereman __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
