Note:

• For all distributed and High availability (HA) environments - The Essbase Windows service cannot access a standard network share that you create. Instead, you need to mount the network share using a specified PowerShell script.

  Create the following file:

  c:\essMount.ps1

  Replace %ADMIN_USER% and %ADMIN_PASSWORD% with the actual Windows Administrator User credentials:

  $User = "%ADMIN_USER%"
  $PWord = ConvertTo-SecureString -String "%ADMIN_PASSWORD%" -AsPlainText -Force
  $creds = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $User, $PWord
  New-SmbGlobalMapping -RemotePath \\hostname\sharename -Credential $creds -LocalPath V:

  Execute the following script:

  C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -command "c:\essMount.ps1"
  

  This will mount the specified network share as the "V:" drive, which can then be used for configuring Essbase 21c.

• When using a mounted network drive or share as the Arborpath for Essbase 21c, ensure the trailing backslash is removed; otherwise, Essbase will not be able to import or upload files correctly.

  For example:

  If the network share \\hostname\share is mounted as the "Z:" drive on a Windows system, the Arborpath in Essbase should be set to Z: (without the trailing backslash), not Z:\.