Why, when a remote host is defined with alias name (virtual hostname or DNS name), does the Control-M job running at the remote host fails with below error:
------------------------
An error occurred while the job: <order id> <RUNCNT> was executing
Shared Directory <Sysout Path> does not have sufficient privileges.
------------------------

The same job works fine when the remote host is defined with physical hostname.

 

When a remote host is defined with alias name, Control-M tries to access the shared SYSOUT folder by its alias name instead of the physical name.

From the AM log, below error can be found
0714 02:14:34:099 AM_SUBMIT:>>> WmiJob::isShareWritable enter
0714 02:14:34:099 AM_SUBMIT:       tmpScriptName: <\\hodtest\SYSOUT\00001_559mz.txt>
0714 02:14:34:599 AM_SUBMIT:       the shared Sysout dir DOES NOT have write access
0714 02:14:34:599 AM_SUBMIT:<<< WmiJob::isShareWritable exit with: 0

To resolve this, below solution can be used:

Step 1: In the properties of the remote shared directory, in the sharing tab, give "Everyone" full control.
Step 2: In the properties of the remote shared directory, in the security tab, give "Everyone" full control.
Step 3: 
- Please login to the remote machine and navigate to the sysout directory
- Right click on the folder, click "advanced Sharing" under share tab 
- Mark the "share this folder" checkbox, then click on the permission 
- Grant RUNAS user which is defined in Control-M Configuration Manager with full permission
- Click ok.
- Back on the NetworkPath tab, click the share button and give the permission to the desired user or everyone again.
- click DONE. 
Step 4:
- Copy the networkpath to test and ensure the RUNAS user can create a txt file for testing purpose. 

Please confirm the Control-M job should run properly in the remote host