I actually was able to get the 7.6.03 Build 001 running. There are issues with the email engine. And the path for the Tomcat to Midtier link was incorrect in the arsys.xml file. (BMC Support helped with that one)
As for the Email Engine problem I’ll probably branch a new List item. And I think the sys admin is going to give me a new VM to load a shared system. Nice clean build on a new machine. Then we switch off the old server and rename the new one. Thanks, --- John J. Reiser Remedy Developer/Administrator Senior Software Development Analyst Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tommy Morris Sent: Monday, January 24, 2011 12:28 PM To: [email protected] Subject: EXTERNAL: Re: 7.6.03 Upgrade gone bad. I had to revert back to ARS 7.5p3 from 7.6.03 and had to restore the db, then run the ARS uninstaller. Then run the 7.5p3 install as an upgrade. I fortunately did not have to reinstall ITSM or CMDB which was a huge concern. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of patchsk Sent: Monday, January 24, 2011 11:14 AM To: [email protected] Subject: Re: 7.6.03 Upgrade gone bad. ** Technically Yes, but here are the things you need to consider. When you run the upgrader it will update the binaries on the remedy app folder as well the meta data in db. In your case if the db is ok you just want to replace app then you can install on the same server as shared or as you said you can build a new server as shared and point to the same db. But if the db is also having issues then you can only restore from the tape. In your case you upgraded from 7.1 to 7.6, so that is both db and binaries. If you want to switch back to 7.1 again then your only option is to restore from the tape. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
