Management Reporter 2012 RU1 Update to RU4

This question is answered

My client has rather specific database protocols.  The ldf and mdf files are renamed to meet their requirements, the application is installed on specified drives (i.e. not the c: drive).  They installed MR2012 RU1 and everything worked fine. However, there were a few reports with issues that would be resolved by using a later RU. 

When we try to install RU4, the process acknowledges MR will be updated (.29 to .33) and the MR RU4 Server component installs "Successfully".  But when the configuration console opens, it treats RU4 as a new instance and the upgrade link is not present in the Tasks pane.  The console does not show any companies as being present.  Trying to refresh the company list does lead to an error stating the database cannot be found.  After some searching, it was discovered the RU4 was installed in on the C: drive and the original RU1 install is untouched on the D: drive. 

 The event viewer does not show any errors just information messages that the MR msi ran successfully. 

Tried to upgrade using standard MR2012 method in the RU4 manual as well as the upgrade method of connecting to a copy of the ManagementReporter database like the upgrade process from MR v2.  Both methods result in a similar fashion.

The issue seems to be that the RU4 install understands it is an upgrade but something is not processed properly and when the Configuration Console (at v.33) opens it can't find the data it needs. 

Can Management Reporter be installed at a location other than the default and still be properly updated?

Any suggestions on how to update?

Thanks,

Claude

 

Verified Answer
  • Update - My client changed the registry entry to force the upgrade install to the d: drive using the following sample:

    * Select "Run" from the Start menu.

    * Click Start> Run (or Windows key + R)

    * Type regedit and click OK.

    * Scroll to the key: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion

    * On the right window, double click on the key ProgramFilesDir and modify data in this key by the new path for the installation folder.

    * For example, enter the path D: Program Files, to change the partition on which the facilities are.

All Replies
  • Update - My client changed the registry entry to force the upgrade install to the d: drive using the following sample:

    * Select "Run" from the Start menu.

    * Click Start> Run (or Windows key + R)

    * Type regedit and click OK.

    * Scroll to the key: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion

    * On the right window, double click on the key ProgramFilesDir and modify data in this key by the new path for the installation folder.

    * For example, enter the path D: Program Files, to change the partition on which the facilities are.