Deployment Solution

 View Only
Expand all | Collapse all

Message received is "The requested task instance could not be loaded. It may not yet be replicated to this NS. "

  • 1.  Message received is "The requested task instance could not be loaded. It may not yet be replicated to this NS. "

    Posted Jan 16, 2012 05:40 AM

    SMP7.1SP2 on WinSvr2008 R2 EE

    DS 7.1 SP1 MR1a

    ---------------------------

    Hi all,

    got an error message when trying to run a DS job. Message received is  "The requested task instance could not be loaded. It may not yet be replicated to this NS. "

    This is the parent NS, not a child NS, so none of the jobs or tasks are dependent on being replicated.

    Any ideas why I might be seeing this?


    Thanks vm



  • 2.  RE: Message received is "The requested task instance could not be loaded. It may not yet be replicated to this NS. "

    Posted Jan 16, 2012 05:50 PM

    Did you follow the correct upgrade procedures?  Per this KB, there are special steps to consider when replication is involved:
    http://www.symantec.com/docs/TECH177513

    Does your Altiris Log Viewer show replication-related errors?



  • 3.  RE: Message received is "The requested task instance could not be loaded. It may not yet be replicated to this NS. "

    Posted Jan 19, 2012 04:49 PM

    And what is the TARGET of the task?  If the target is a client of a child server, then the task instance has to replicate down to the child NS and be essentially re-deployed from there.  We know that, in some instances, tasks themselves will be created on the parent, and NOT replicate prior to you (an administrator) creating a run instance of the task.  DS has this issue.  Some other solutions have built-in to their product a method of ensuring the task replicates at the same time as the run instance.

    Note, that when you drill down into a task that is destined for a client on a child NS, even though you're on the parent, you drill down into a direct view of the child NS iteself.  You can actually see that at the top of the pop-up window that you're no longer on the server you THOUGHT you were on.

    Take a look at that, and see if this is what you're running into.  Then simply right-click the task, replicate now, and see if the problem goes away.