Windows 10 Metadata directory access

Windows 10 Metadata directory access

ISSUE: Users are unable to run out reports due to them not being available in report manager. Users receive an error when opening or using Security Manager "Operation must use an updateable query."

If our metadata repository folder is created by an application running as Administrator (which our License Manager ALWAYS does), any application not running as Administrator (default for Report Manager and Connector) cannot write to the repository. If the user installs, selects the default Metadata path and then runs License Manager first - The problem will arise. Users who run Report Manager first won’t get the problem – even when running License Manager because Report Manager already created the repository as non admin.

SYMPTOMS: Users cannot see reports they wish to run out "Operation must use an updateable query." error Licensing for Sage Intelligence behaves differently when modules are run as Administrator.


  1. Close all Sage Intelligence modules.
  2. Locate the default Metadata repository (Default directory- "C:\ProgramData\SageAlchemex\SageIntelligenceReporting").
  3. Backup "alchemex.svd" (Default directory- "C:\ProgramData\SageAlchemex\SageIntelligenceReporting\MetaData").
  4. Backup "Config.ini" (Default directory- "C:\ProgramData\SageAlchemex\SageIntelligenceReporting").
  5. Delete the "SageAlchemex" folder and its subfolders from "C:\ProgramData".
  6. Create the folder "SageAlchemex" in "C:\ProgramData".
  7. Create the folder "SageIntelligenceReporting" in "C:\ProgramData\SageAlchemex".
  8. Create the folder "MetaData" in "C:\ProgramData\SageAlchemex\SageIntelligenceReporting". This will result in the following folder structure "C:\ProgramData\SageAlchemex\SageIntelligenceReporting\MetaData" which is the same as the default MetaData directory however this is created without elevated permissions.
  9. Restore "alchemex.svd" (Default directory- "C:\ProgramData\SageAlchemex\SageIntelligenceReporting\MetaData").
  10. Restore "Config.ini" (Default directory- "C:\ProgramData\SageAlchemex\SageIntelligenceReporting").
  11. If you are still unable to see the reports you wish to run, try the following:
  12. Navigate to "C:\Users\[USERNAME]\AppData\Local\VirtualStore\ProgramData\SageAlchemex\SageIntelligenceReporting\MetaData".
  13. Backup and cut "alchemex.svd" from "C:\Users\[USERNAME]\AppData\Local\VirtualStore\ProgramData\SageAlchemex\SageIntelligenceReporting\MetaData"
  14. Follow steps 5 to 9 above.


Windows 10 installations where License Manager is the first Sage Intelligence module run.

    • Related Articles

    • License OK button greyed out

      Your license managed has the OK button greyed out, however there are still available licenses. Resolution: Go to C:\Program Files (x86) > Common Files > BIComponents and ensure this folder is full read/write access On Windows 10, do a further check ...
    • Sage Intelligence Reporting License Allocation

      Problem - you need to change/add/delete licenses but you are not sure where they are assigned and how many are being used  To check your license allocation, do the following: Open the License Manager from the Start Menu (This will require domain ...
    • Back Up the Metadata Repository

      It is very important to always backup the metadata repository before making changes to your Sage Intelligence Reporting installations. The Alchemex.svd file and Templates folder's are the only folders that need to be backed up with our installation. ...
    • Number 75: Path/File access error

      Problem When launching any module of Intelligence Reporting, you get a file/access path error When trying to run a report you get this error Resolution Check that you have full read/write access to the Metadata Repository Check that you have full ...
    • Overlapping Windows in Intelligence Reporting Report Manager

      Problem The 'Object' and 'Properties' windows overlap. Thus making running reports impossible. Disclaimer Operating System Warning This solution requires advanced knowledge of your computer's operating system. Contact your system administrator for ...