Bill2, I did that, but no way. Then, on the Task Scheduler, I set the task to be run by the System because I think that would solve any permission problem, but it did no good either. the issue must be caused by something I wrote on the task, but as I can't read the notice, I don't know what it is.
Can you post the script here so that we can try to debug it?
maybe a new pair of eyes will spot something :)
Thank you all. I've found the issue. as expected, it was not on the batch file because I have been running it for ages by just double clicking directly on it. How could it be? The problem had to been something ridiculously silly, but that I could not see because I couldn't stop the message window to close to be able to read – It was like a flash. I couldn't stop it after all, but I tried many things. I fond out the problem was on the path: I had a & character on the path and it was not accepted. The path has always been like that, but as I used the batch file the way I said it did not make any difference. Probably reading the error message window I could have found this right at the first time, but I'm still unable to do that, and that is the only reason why we have lost so much time.
Thank you again for the good will trying to help.
Just for next time, add a PAUSE after all the commands that might me producing the error message.
pause will produce the message "Press any key to continue"
Batch.cmd
Run it and the window will pause and not close till you hit any key to continue.Code:@echo on call "I am a command, see me run" pause
Unless you have @echo Off, then you need to comment that out.
Quote