in
Support Center
StorageCraft Support Forums » ShadowProtect » Desktop Edition » No access to job which has been manually stopped

No access to job which has been manually stopped

Last post 07-20-2008 9:49 AM by Stoeber. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next

  • 07-20-2008 4:16 AM

    No access to job which has been manually stopped

    Reply Contact

    Hello,

    I stopped a new created job (because there was no continuation during service code 150 - snapshotname). Now there is no way to re-activate or delete this job.

    One result of this behaviour is that there is no way to create another job for this volume because SP tells me that this volume is executed by the other job.

    Any idea how to handle this stopped job? - Thanks.

  • 07-20-2008 9:49 AM In reply to

    Re: No access to job which has been manually stopped

    Reply Contact

    Problem solved ! After Booting the ws and starting SP this job could be handled again.
Page 1 of 1 (2 items)
(c) StorageCraft Technology Corporation 2008