It sounds like you don't have rights to install to /opt/remedy/product/7.0
Was the original installed as root (or have you forgotten to do the "export 
ARNONROOTINSTALL=TRUE" before running the installer?

7.1 did not have an installation XML file (The install was not XML based for 
what to install).   

When you select the server the installer reads the 
/etc/arsystem/{servername}/armonitor.conf file to get the original path.

There should be an installation log file in /tmp or /usr/tmp that can give you 
better info on what you are seeing

Fred

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Jason Lander
Sent: Tuesday, October 18, 2011 9:19 PM
To: [email protected]
Subject: AR System Server 7.1 Upgrade to 7.5 Issue

Hi All,

I am currently performing an upgrade on a client's UAT AR System 7.1 
environment.  I've barely started, and I've already hit my first snag.
 
The clients AR System 7.1 P6 Server is installed on a UNIX environment (Solaris 
10).  The installation directory is /opt/remedy/product/7.0.
 
When I run the AR System 7.5 P7 installer, and enter the correct AR System 7.1 
P6 Server installation directory, the next screen displays the following error, 
No features are selected to install.
 
If you go back to the previous screen and change the installation directory to 
/opt/remedy/product (or any other incorrect directory) it will allow you to 
continue (as it obviously thinks it is a fresh install) up until the point 
where you enter the AR System Server name.  After selecting the server, I 
receive a different error, The current installation directory does not match 
the server installed at /opt/remedy/product/7.0. Go back to the previous screen 
and change the installation location for the AR System Server you want to 
upgrade..  This error proves that the installer does indeed know that the 
installation directory is /opt/remedy/product/7.0 but for some reason, it just 
cant read in the products installed for it.
 
My guess is that it's due to a missing ARSystemInstalledConfiguration.xml file 
from the previous install.  The installer is probably trying to read in the 
information from that file so that it knows what was previously installed.  
Unfortunately none of the servers (not even the Productions servers) have this 
so I cannot test this theory out.
 
Has anyone come across this issue before?  If not, can anyone supply me with an 
AR System Server 7.1 ARSystemInstalledConfiguration.xml file that I can hack 
(and test my theory out with)?

Cheers,

J



_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to