If you upgraded to 6.2.X and encountered issues, reverted to an earlier version, and now are upgrading to a 6.2.X version, all chart data from the time you reverted to the earlier build will be missing.
To avoid this issue, follow the steps below before you install 6.2.X. Following these steps, chart data from the time of the initial upgrade is removed, chart data from the time of reverting is retained, and chart data from the time of the new upgrade is available and correct.

Note: Be sure to back up your Intermapper Settings\Chart Data folder before following these steps.

For Example:
If you upgraded to 6.2.X from 6.1.5 in May, and found that the upgrade was causing problems, then downgraded back to version 6.1.5, all of the chart data generated for the time while on 6.2.X would be missing since it’s not compatible with earlier versions. Now it’s July, and you upgrade to 6.2.2. All the chart data from the time you downgraded appears to be missing. Run the command below (for your OS) to remove the chart data that was created by 6.2.X. All chart data created after you downgraded, and all data created after the recent upgrade will appear. You will lose only the data that was created during the initial 6.2.X upgrade.


  1. Open the cmd window as an administrator (right click it in All Programs > Accessories and choose either Run as Administrator or More > Run as Administrator).
  2. cd “C:\ProgramData\InterMapper\InterMapper Settings\Chart Data\”
  3. del /S n*
  4. Verify that no chart data files start with "n" using this command:
    dir /S n*

Success looks like this:

  C:\ProgramData\InterMapper\InterMapper Settings\Chart Data>dir /S n*
  Volume in drive C is OSDisk

  Volume Serial Number is D05F-5A8E

  File Not Found

  C:\ProgramData\InterMapper\InterMapper Settings\Chart Data>

cd /"Library/Application Support/InterMapper Settings/Chart Data"
rm */n*

rm /var/local/InterMapper_Settings/Chart\ Data/*/n*

Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case