Symptoms: - Control-M Agent failed to copy a file using a script via a Control-M job - The script is able to transfer the file successfully if executed manually - This might happen on both Regular and Remote Host / Agentless Control-M Agent - Control-M job will fail with "Access denied" Error |
Solution: - Make use of "net use" in the script to copy the file - Example: To transfer all files under "temp" directory to remote directory copy d:\temp\*.* d:\source_transfer\outgoing net use I:\\dest_transfer move d:\source_transfer\outgoing\*.* I:\incoming net use I:/DELETE Alternatively, if the job runs successfully using a domain user outside of Control-M: - Check the Control-M/Agent's Windows configuration: ctmwincfg - Check the field "Logon As User (Y/N)" and verify that its value is "Y", so that the Run As user will be used instead of the Control-M/Agent service. - Check the field "Logon Domain" and verify that the value therein matches the domain of the domain users that have access to run the jobs on this host. This will affect all jobs run on this Control-M/Agent. Additional Information: - See Knowledge Article: 000109790 - Problem in Control-M with Accessing UNC Paths via WMI Access for Remote Host |