Scheduled Task runs but report shows source is offline

I have one job scheduled. When I run a test on the job, the test runs properly.  However, when the scheduled task for that job tries to run Secure Copy reports indicate that the source share is offline.  Even if I run the task manually, it reports that the source is offline.   This is the truncated report:

<Date>2/18/2021 5:00:14 AM</Date>
<Message>Retry NO.1. The path \\hvdata02\d$\hvdata\ is either offline or does not currently exist.</Message>


<Date>2/18/2021 5:00:23 AM</Date>
<Message>Retry NO.2. The path \\hvdata02\d$\hvdata\ is either offline or does not currently exist.</Message>


<Date>2/18/2021 5:00:33 AM</Date>
<Message>Retry NO.3. The path \\hvdata02\d$\hvdata\ is either offline or does not currently exist.</Message>

<Date>2/18/2021 5:00:33 AM</Date>
<Message>Source path \\hvdata02\d$\hvdata\ is either offline or does not currently exist.</Message>


<Date>2/18/2021 5:00:33 AM</Date>
<Message>There is no data to copy. All of the source directories are either offline or do not currently exist.</Message>

I have tried setting the task to run with the highest priveleges, but that doesn' t seem to help.  What do I need to change?

Parents
  • Hello David,

    Thanks for posting to the Secure Copy forum. I understand you are experiencing issues running a copy job with Secure Copy. I will need some additional information to better assist you:

    1.) What is the exact version of Secure Copy you are running (top Help menu | About)?

    2.) What is the source (Windows, NAS, etc)?

    3.) What is the target (Windows, NAS, etc)?

    4.) Is Secure Copy installed on the source, target, or another server?

    Regards,

    Trevor Taegder
    Senior Technical Support Engineer
    Quest | Support

  • Having same issue: "is either offline or does not currently exist"

    When job is run manually it works. When it runs as a task it fails. 
    SecureCopy 7.6.1.25
    Source is a NetApp
    Target Windows Server
    QSC Installed on Target

  • Hello Leo,

     

    Thanks for posting to the Secure Copy forum. You had also created a Service Request in addition to this forum post. Through the Service Request, we were able to join a call and investigate this issue further. It was determined that the cause of the issue is that the scheduled copy job that Secure Copy creates in the Windows Task Scheduler is set to run as the local System account by default. After creating a scheduled job in Secure Copy, it is typically best to go into the Window Task Scheduler directly, locate and edit the Properties of the task. It is typically recommended to set the task to run as the same domain account that is able to run the copy job successfully from the Secure Copy console. Additionally, it is typically suggested to run the task with the "highest privileges" option selected.

     

    Here is a KB article that mentions these steps:

     

    https://support.quest.com/secure-copy/kb/213920/scheduled-task-for-a-job-keeps-cancelling-itself-or-failing-213920

     

    I hope this summary may help others that may experience similar issues in the future.

     

    Regards,

     

    Trevor Taegder

    Senior Technical Support Engineer

    Quest | Support

Reply
  • Hello Leo,

     

    Thanks for posting to the Secure Copy forum. You had also created a Service Request in addition to this forum post. Through the Service Request, we were able to join a call and investigate this issue further. It was determined that the cause of the issue is that the scheduled copy job that Secure Copy creates in the Windows Task Scheduler is set to run as the local System account by default. After creating a scheduled job in Secure Copy, it is typically best to go into the Window Task Scheduler directly, locate and edit the Properties of the task. It is typically recommended to set the task to run as the same domain account that is able to run the copy job successfully from the Secure Copy console. Additionally, it is typically suggested to run the task with the "highest privileges" option selected.

     

    Here is a KB article that mentions these steps:

     

    https://support.quest.com/secure-copy/kb/213920/scheduled-task-for-a-job-keeps-cancelling-itself-or-failing-213920

     

    I hope this summary may help others that may experience similar issues in the future.

     

    Regards,

     

    Trevor Taegder

    Senior Technical Support Engineer

    Quest | Support

Children
No Data