Debug Logging for Upgrades

Vishal Lahane shared this idea 3 days ago
Idea Logged

When upgrading Yellowfin, you're only asked to point to the existing installation folder, however in some cases after doing this, you still get a message that the folder is not valid. Can we enable debug logging so we can see exactly what it's looking for in these cases.

Comments (2)

photo
1

Hi Vishal,

Thanks for reaching out with your suggestion. I've logged this for review by our Development team and will keep this post updated with further information regarding this.

Thanks,

Ryan

photo
1

Hi Vishal,

When doing upgrades, Yellowfin looks for that ROOT folder (or what it has been renamed to) in order to get the program path and DB locations.

In cases where the upgrade returns "The selected directory does not appear to be a SmartReportingUpgrade directory." One of the following conditions have been met:


  1. An incorrect file path set in the configuration files.
  2. Missing core libraries of the application (pretty much the items in the ROOT folder)
  3. Renamed core application libraries. (really this is the same as 2)


However as we have seen it fail when the above conditions have not been met, we will enable debug logging to see exactly what it's looking for, and where.

This change is current in review with the dev team and will keep you posted on updates.


Thanks,

David