Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise Resource Management

Setup Directory access

  • Last UpdatedMay 07, 2026
  • 2 minute read

Follow the principle of least privilege. Limit folder access to authorized users.

Installation Directory

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read, write, and execute permissions on the path specified in the Installation Directory field.

If the installation directory does not already exist, AVEVA Enterprise Resource Management Deployment Manager creates it automatically with permission inheritance disabled and with permissions removed for the local Users group. When you create the directory manually, ensure the appropriate permissions are configured before starting the installation.

Log Files

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read and write permissions on the log directory defined in the Log Path field. The default log path is C:\ProgramData\AvevaErm.

Note: C:\ProgramData is a hidden folder.

Oracle

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read and execute permissions on the Oracle home directory. For example: C:\oracle\product\19.0.0.

ASP.NET Temp Files

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read and write permissions on the ASP.NET temporary files directory, C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files.

Server Plugins

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read and execute permissions on the Plugins Server Path, as configured in d0073 ERM System Settings dialog and stored in the database table DFLT_ADM, column PLUGIN_SERVER_PATH.

When using .dll plugins, the Plugins Server Path is local to the server. When using Lua plugins only, the path is specified as a network share.

Import Staging Areas

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read and write permissions on all Import Staging Area directories configured in AVEVA Enterprise Resource Management in the s22015 Import Staging Areas screen (database table IMPORT_STAGING_AREA).

For simplicity, configure a single root directory that contains all import staging areas and grant access to this root directory. Restrict the access to the d0222 Import Staging Area Configuration dialog to administrative users only.

Export Staging Areas

The account specified in the Run As Username field in AVEVA Enterprise Resource Management Deployment Manager requires read and write permissions on all Export Staging Area directories configured in AVEVA Enterprise Resource Management in the s12019 Export Staging Areas screen (database table EXPORT_STAGING_AREA).

For simplicity, configure a single root directory that contains all export staging areas and grant access to the root directory.

In general, the account specified in the Run As Username field requires read access to all paths referenced within the system. For example, this includes any Template Path referenced by an Excel Report data extract and any Script Path referenced by a Lua Query data extract.

After applying or modifying directory access permissions, restart the machine.

TitleResults for “How to create a CRG?”Also Available in