All jobs on the Windows agent stop executing. The jobs start but remain in status Active indefinitely.
No errors appear in the logs but the Job Report only shows the line that calls the Job Messenger:
[Work_directory]>[Agent_bin_folder]\.\UCXJWX6M.EXE JNR=[RunID] MNR=[Client] PNR=[Agent_Port] IPA=[IP_Address] TYP=S TXT=" Job started" LOCAL=1 IPC=\\.\pipe\[Instance]_[port] TRC=0
Symptoms:
Jobs stop executing and hang in an active state
Agent tries to start jobs and writes the initial line to the report file, but stops
The message binary (ucxjwx6m․exe) is reduced to 0 bytes
Context: Occurs during normal job execution on the Windows agent
Impact: Production down; jobs cannot execute
OS: Windows
The ucxjwx6m․exe file is a critical component for executing jobs․ If it becomes 0 bytes, jobs will hang․ This is not caused by the Automic product․ Likely causes include the system running out of disk space or a security tool.
Prerequisites:
Administrator access to the Windows agent server
A working copy of the ucxjwx6m․exe file from another agent directory with the same version
Steps:
1․ Replace the Messenger Binary UCXJWX6M.EXE
Path: Agent installation directory bin folder
Action: Copy the valid ucxjx6m․exe from another agent directory on the same server to replace the 0-byte file
Expected: The file replaces successfully
2․ Restart the Agent
Action: Restart the Automic Windows agent service
Expected: The agent starts successfully
3․ Restart Stuck Jobs
Action: Cancel any tasks that are stuck in an active state and restart them
Expected: Jobs begin executing and writing to report files normally
Verify Success:
Jobs execute without hanging
The ucxjwx6m․exe file maintains its normal file size
Prevention:
Ensure adequate disk space and configure antivirus exclusions for the Automic agent directory. But, this must be done before the file becomes 0 bytes.