Condition on File Resource is not detected on network disk on Windows
search cancel

Condition on File Resource is not detected on network disk on Windows

book

Article ID: 84667

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

On Windows, conditions on file resources are not detected if the files are on the network using a UNC path, e.g.:

\\server\folder\file.txt

The Resource log displays:

<...>
2024-05-21 10:05:52 | <RESOURCE_NAME> | 0260763 | Scan Number 15 | Checking resource <RESOURCE_NAME>...
2024-05-21 10:05:52 | <RESOURCE_NAME> | 0260763 | Scan Number 15 | No file matching filter [\\server\folder],[file.txt]
<...>

Environment

OS: Windows
OS Version: All Windows

Cause

Cause type: Configuration
Root Cause: This is related to the system user defined in the Windows Services to start the EEP process: Local System does not have permission on UNC paths.

Resolution

To configure the File Resource properly, you must

  • Use UNC path to the file (\\server\folder\file)
  • Change the user of the EEP Windows services that checks the resources such that it is a Domain User instead of LocalSystem.