Stop Command Line Window Message From Closing

[Neophile]

I have a problem running a task with Task Scheduler. The task doesn't run. I have to debug it. When I try to make it run from the app a message appears on a command line message, but it appears and disappears so quickly that I can't read it. To fix the problem I need to read it to know what is going on.

Can someone please tell me how to stop that command line window message from closing, please?

 

[Thorsen]

can you run the program from the command line?

open a new cmd window go to Run and type in cmd.exe

when it opens it should be in c:\windows

navigate to the folder, run the file

 

[Neophile]

Thanks Thorsen, but I do not want to run the command manually from the command prompt; that's is exactly what I want Task Scheduler to do for me. The commend is a batch file that I have been running manually for a few years now (so that it is thoroughly tested), but I want to do it automatically with the T.S. To make it run manually with T.S. to test the task you click on Run, on the right column, under Selected Item. That's where the Command line window appears with a message, and nothing happens.

I have also looked up on Event Viewer, but There is not an event failure code number, it just says the task failed to run, and the History tab is virgin, so it doesn't even start. Then I seasrched on MS Technet and found some explications, but not what I need to know: the text of the message that I cannot read because its four or five lines just blink on the screen.

How can I read this, please?

 

[gladson1976]

Try adding a PAUSE at the end of the batch script.

 

[Neophile]

Thanks gladson1976, I did that too, but with no result, and that is also why I know the batch file is not processed. It must be something on the task itself because, as I said, it is not started, so it does not start the batch file and the pause there is useless.

Is is very silly that I don't know how to stop these message windows to be able to read them. Any idea of how to?

 

[gladson1976]

What is the script for anyway ? What does it do ?
Can you post the script here ?

EDIT: I just tried adding a small batch script to TS and it worked perfectly and also PAUSE worked.

 

[Neophile]

Thanks gladson1976. I've running that batch file for more than six years to clean up some parts of the system, just changing the paths according to the OSs. The Windows disk clean-up is a real shit by itself. So the problem cannot be there. I also run other tasks I created with Task Manager without any problem. My real problem is that I do not have etime nough to read the notice, because if I do, I'm nearly sure I can fix it. How to just that simple thing?

 

[Bill2]

Setup the task under your administrator account. Then add the administrator permissions to full control for the batch file.

 

[Neophile]

Setup the task under your administrator account. Then add the administrator permissions to full control for the batch file.

I use that account to setup tasks, but how do I do I set the permissions for the batch bile if it is run by the task?

 

[Bill2]

Neophile,
I meant go to the folder where the batch file is located and give yourself full control over the file.

 

[Neophile]

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.

 

[gladson1976]

Can you post the script here so that we can try to debug it?
maybe a new pair of eyes will spot something

 

[Neophile]

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.

 

[flytomars]

Just for next time, add a PAUSE after all the commands that might me producing the error message.

 

[Tepid]

pause will produce the message "Press any key to continue"

Batch.cmd

@echo on
call "I am a command, see me run"

pause

Run it and the window will pause and not close till you hit any key to continue.

Unless you have @echo Off, then you need to comment that out.