I'm having a strange issue with number of client jobs. I'll give you an example of the most recent instance.
1. I create a simple client side job with one "run script" task, lets call it "job 1", and save it
2. I want to create a "parent" client job that will in essence "chain" all the other jobs I have created after an image deployment. I add a few other existing jobs to it without issues. I then add "job 1" to the "parent" job and the console freezes on me.
3. I go back to the console to find that the "parent" job is empty, which is fine, because I was never able to press "save"
4. I return to "job 1" and it wont let me access it. It prompts me for credentials, I enter the domain admin account credentials, and its a no go.
I can access a number of other jobs I have created, except for "job 1", it continually asks for credentials which it doesnt accept. If I attempt to delete the now apparently corrupt "job 1" it tells me its "being referenced by one or more items", which it's not. Even if I delete the "parent" job that I initially attempted to make it a part of, it doesn't allow me to delete it. I was wondering if anyone has run into this issue, and if there is any way of removing this corrupt job?