Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: v2.1.1
    • Fix Version/s: not determined
    • Component/s: installation
    • Labels:
      None
    • Environment:

      Operating System: Solaris
      Platform: Sun

      Description

      I install b31f ee on solaris 10 sparc. Everything work well. Then I uninstall it
      and delete SUNWappserver as well. I try to install it again to same directory,
      installer will remind me one version already there, and installation will fail
      if I continue.

        Activity

        Hide
        scatari added a comment -

        Looks like the uninstallation process was not successful for some reasons. Also Could u please remove
        the file /var/sadm/install/productregistry if the installation was run as root OR $HOME/productregistry if
        the installation was run as non-root user before re-running it again.

        If you are able to successfully uninstall after deleting this file, then it is a problem with partial uninstall. I
        would advice to go through the install and uninstall sequence once again and looking at the log file during
        uninstall process to see if there are errors or warnings reported.

        Show
        scatari added a comment - Looks like the uninstallation process was not successful for some reasons. Also Could u please remove the file /var/sadm/install/productregistry if the installation was run as root OR $HOME/productregistry if the installation was run as non-root user before re-running it again. If you are able to successfully uninstall after deleting this file, then it is a problem with partial uninstall. I would advice to go through the install and uninstall sequence once again and looking at the log file during uninstall process to see if there are errors or warnings reported.
        Hide
        leonfan added a comment -

        I confirmed there is no exception in uninstallation log file. It seemed cause
        by registration data as you mentioned. Do uninstaller remove those data
        automatically?

        Show
        leonfan added a comment - I confirmed there is no exception in uninstallation log file. It seemed cause by registration data as you mentioned. Do uninstaller remove those data automatically?
        Hide
        easarina added a comment -

        I've tried GF 2.1.1 EE build 31g on Solaris and Linux machines.

        GF 2.1.1 EE uninstaller doesn't remove correspondent entries from
        productregistry file ( /usr/tmp/productregistry on Linux and
        in /var/sadm/install/productregistry on Solaris)

        With GF 2.1.1 entries in productregistry file, the attempt to install GF 2.1.1
        EE or Sailfin at the same location, will create an installer message. This
        message will tell that at this location was detected a previous installation
        and your installation may have issues if you will do the installation in that
        location. It happened, for example, if such directory doesn't exist at all.

        I believe the uninstaller have to remove correpondent entries from
        productregistry. Or at least this issue has to be documented

        Show
        easarina added a comment - I've tried GF 2.1.1 EE build 31g on Solaris and Linux machines. GF 2.1.1 EE uninstaller doesn't remove correspondent entries from productregistry file ( /usr/tmp/productregistry on Linux and in /var/sadm/install/productregistry on Solaris) With GF 2.1.1 entries in productregistry file, the attempt to install GF 2.1.1 EE or Sailfin at the same location, will create an installer message. This message will tell that at this location was detected a previous installation and your installation may have issues if you will do the installation in that location. It happened, for example, if such directory doesn't exist at all. I believe the uninstaller have to remove correpondent entries from productregistry. Or at least this issue has to be documented
        Hide
        easarina added a comment -

        This problem exists on Linux and Solaris machines, but doesn't exist on Windows,
        because for Windows installations the productregistry file would not be created
        at all.

        The work around for Solaris or Linux installations:

        Remove the productregistry file: /usr/tmp/productregistry on Linux and
        /var/sadm/install/productregistry on Solaris. Or remove correspondent GF
        entries from the productregistry file.

        Show
        easarina added a comment - This problem exists on Linux and Solaris machines, but doesn't exist on Windows, because for Windows installations the productregistry file would not be created at all. The work around for Solaris or Linux installations: Remove the productregistry file: /usr/tmp/productregistry on Linux and /var/sadm/install/productregistry on Solaris. Or remove correspondent GF entries from the productregistry file.
        Hide
        scatari added a comment -

        Does not apply to 3.1.

        Show
        scatari added a comment - Does not apply to 3.1.
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            scatari
            Reporter:
            leonfan
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: