ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

File trigger job on R12 Windows agent is not going to success even though file is in the path it is watching (job stays in RUNNING)

book

Article ID: 239027

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

An r12 Agent on Windows 2019 is being used for a file watcher job, trying to watch a file on a mapped drive.  Job starts, runs but stays in Running (after adding: filemonplugin.runexternal=true  and oscomponent.restoredrives=true to agentparm.txt file and restart of agent)

insert_job: ft_test__zdrive
job_type: FT
machine: windows-agent
owner: [email protected]
watch_file: "z:\foo.txt"
watch_file_type: CREATE
watch_file_recursive: false
watch_no_change: 1
watch_file_change_type: SIZE

Cause

UNC paths are recommended rather than using mapped drives

 

Environment

Release : 12.0

Component : Workload Automation System Agent

Resolution

insert_job: ft_test__zdrive
job_type: FT
machine: windows-agent
owner: [email protected]
watch_file: "\\UNC-share-on-agent\share-name\foo.txt"
watch_file_type: CREATE
watch_file_recursive: false
watch_no_change: 1
watch_file_change_type: SIZE

 

It may also be required to use an additional option on the jobs in some cases:

watch_file_win_user: [email protected]

Additional Information

https://knowledge.broadcom.com/external/article?articleId=237983