Access denied errors when running the Clearwell Utility

book

Article ID: 100034097

calendar_today

Updated On:

Description

Error Message

Example using the Clearwell Utility to stop the eDiscovery Platform (eDP) services:

Stopping All Clearwell Services...

======== target = stop-services
Buildfile: D:\CW\V82\build.xml
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: logs\ant_output.log (Access is denied)
...

Cause

It seems that on Windows Server 2012, the usual methods of disabling User Access Control (UAC), including C:\Windows\System32\UserAccountControlSettings.exe are not sufficient. The only reliable way to disable UAC is to update the Windows Registry directly.

A reliable indication that UAC has not been fully disabled is that a standard command prompt will NOT include Administrator: in the title (Figure 1).

Figure 1.
Command prompt when UAC is not fully disabled

In contrast, a command prompt launched when UAC has been fully disabled should include Administrator:  in the title (Figure 2).

Figure 2.
Command prompt when UAC is fully disabled

 

Resolution

As detailed in the eDP Installation Guide, UAC must be disabled. This is required both for the product installation and for everyday usage of eDP.

To reliably disable UAC do the following steps:

1. Launch a PowerShell console as administrator

2. Run the following command to disable UAC:
Set-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value "0"

3. Reboot the server.

NOTE: If UAC keeps getting re-enabled, please check for Group Policies that may affect it.

Issue/Introduction

The Clearwell Utility is reporting Access Denied errors, even though it is being run by a user with administrative privileges.