Use one of the following solution to resolve this CAR if found after installing Control-M/Agent 9.0.00 Fixpack 3:
CAR00155392 : AGENT FileWatcher jobs fails on Agent after upgrade to V9FP3 when AES local.key contains x'00'

Solution 1: Downgrade back to the previous encryption method.

1. Move the <Agent>\data\keys\local.key file to a different folder.
   Keep the file in a safe location in case it is needed later.
  The local.key file should be deleted from the <Agent>\data\keys\ directory, so the Agent will revert to Blowfish encryption 
2. Extract the attached (zipped) files to <Agent>\data\
- REQUESTS.dat
- UDA.dat
- UDA_BMC.dat
Note:
- SendFiles.7z is for Windows.
- ag9UX.tar is for Unix/Linux.
3. Rerun the job.

Solution 2: Upgrade to latest Control-M/Agent V9 Fixpack:
1. Stop the Control-M/Agent
2. Restore REQUESTS.dat, UDA.dat, UDA_BMC.dat (under data) as Solution 1 above
3. Restore PASSWRDS.dat (Blowfish encrypted file from Control-M/Agent V9 FP2 or earlier) file from backup
4. Delete the local.key file (under data/keys)
5. Navigate to /data/cfg_backup and ensure that there is none AES encrypted passwrds.bak file
6. Remove the "/data/cfg_backup\passwrds.bak" if found
7. Upgraded Control-M/Agent V9 FP3 to FP4

Solution 3: Regenerate the local.key and AES encryption on Control-M/Agent V9 FP3:
1. Stop the Control-M/Agent
2. Restore REQUESTS.dat, UDA.dat, UDA_BMC.dat (under data) as Solution 1 above
3. Restore PASSWRDS.dat (Blowfish encrypted file from Control-M/Agent V9 FP2 or earlier) file from backup
4. Delete the local.key file (under data/keys)
5. Navigate to /data/cfg_backup and ensure that there is none AES encrypted passwrds.bak file
6. Remove the "/data/cfg_backup\passwrds.bak" if found
7. Rerun Control-M/Agent V9 ctmagcpk utility to update the AES encryption

Additional information:
1. Control-M/Agent for UNIX and Microsoft Windows 9.0.00.300 has updated an encryption mechanism to AES256 from Control-M/Agent for UNIX and Microsoft Windows 9.0.00.200 (Blowfish). Please check CAR00134526 in the Release Notes for 9.0.00.300.
This problem occurs when the AES key randomly generated by the Fix Pack 300 installation contains a particular byte.

2. From the release notes of PAKAI.9.0.00.400 where CAR00155392 is mentioned:
If you skip Control-M/Agent version 9 fix pack 3, this problem will not appear after installing Control-M/Agent version 9 fix pack 4.
If you didn't skip Control-M/Agent version 9 fix pack 3 and problem occurred installing Control-M/Agent version 9 fix pack 4 will not resolve the issue.

3. Following are the most common use cases: 
- Generate new AES local keys
- Transform all locally stored encrypted data from a current key to a new key:
- PASSWRDS.dat
- REQUESTS.dat
- UDA.dat
- UDA_BMC.dat
- ALL CMs that support AES
- Store the new key in data/keys/local.key
NOTES:
- The utility runs during Control-M/Agent Fix Pack 3 installation and generates new keys to replace all BLOWFISH encrypted data as above
- With “-b” flag, the utility reverts AES to BLOWFISH and deletes local key files.
- In order to run this utility, the Control-M/Agent should be down.
- This utility is not applicable for HP.