"Failed to deploy task" error when adding post-command
I have a backup task that has been running fine for years. I wanted to add a post-command to the task. Everything looks good until I OK out of the Options and I get this error whereby it fails to save the task.
I've checked out everything referenced as possible issues. The services are running fine. I've rebooted. Windows Defender A/V is showing no problems. I was able to create a new task with a post-command and that worked fine.
Any thoughts on what else to look for?


- Anmelden, um Kommentare verfassen zu können

The new task I created works with the same post-command, and I've tried it with both the .bat and .cmd extension. They both worked fine. And running the Test works well. I just won't save the task.
One difference is that the destination on the failing task is a NAS although I can't see how that would matter.
- Anmelden, um Kommentare verfassen zu können

Sounds like that particular backup task script file (.tib.tis) has an issue Bruno if all works correctly for another task!
- Anmelden, um Kommentare verfassen zu können

Upon further testing, the issue is that if I select Options for the task and then click OK, I get the error. All my other tasks work just fine.
I'm hesitant to manually add the post-command into the script.
I cloned the task into a new backup task, but the problem has been carried over into the new one too. I may need to start from scratch unless I can figure out the magic bullet.
- Anmelden, um Kommentare verfassen zu können

I have no idea what happened here, but there was no way I could change anything of the configuration of the backup task. I couldn't even change it to turn off scheduling.
So, I went into the Scheduler Manager to disable the task. So now the task is still there but not scheduled to run. I created a new task and ran that tonight and it looks OK.
Since the new task created a Full backup, I went to the old one to cleanup by deleting the oldest. That worked, but it then re-enabled the task so I had to disable it again in Scheduler Manager.
Eventually, I will just get rid of the task completely.
- Anmelden, um Kommentare verfassen zu können