Unknown job state Netbackup 7.5
- 12 years ago
Same/similar to EC=50 issues, not sure if these reasons are still applicable in 7.5 (two of them certainly shouldn't be) & may or may not be relevant here:
http://www.symantec.com/business/support/index?page=content&id=TECH146990
Item 2 seemed to be the most common for us or just cancelling a (probably manual) job immediately after it had started.
Quite suprised you "can right-click and cancel and delete them" as in a lot of instances they persist & require you to follow the procedures documented (altho' you do go on to say "The problem isn't they can't be deleted" !!) - so maybe not quite the same issue here.
Just as a slight aside we do see 'ephemeral' unknown jobs appear just as a new job is starting prior to the Activity Monitor being populated with the correct information, which seems in a way to tally with Item 2 (for us at least)
***EDIT***
Also found the following 'untidy' T/N:
Jobs goes into an Unknown Job State when job priority is changed
http://www.symantec.com/business/support/index?page=content&id=TECH195710(Not sure if this manifests itself in the Activity Monitor and also *possibly* only relevant to 7.5.0.3 & RHEL5.6)