I am running a large amount of .cmd files in XP 1 at a time. Is there anyway to catch the error's and write them to an error.log? I only want to write if there was an error.
I guess what I'm asking for is something like
ECHO ------- %cmdcmdline% ------- >> error.log
if %errorlevel% GTR 0 Echo command that was executed >> error.log
At the end
ECHO -------//// %cmdcmdline% \\\\ ------- >> error.log
ECHO >> error.log [blank line]
I am running copy, del, findstr, move and writing to files by ECHO command.
Be nice If I could add this to top of .cmd file so I could just open them all and add it.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Any line you want to catch errors for, make sure it ends as:
2>> error.log
2 represents standard error (stderr).
In a command prompt, type try deleting a file that doesn't exist.
DEL NOEXIST.TXT 2>> ERR.LOG
You'll find the error info is put to the file ERR.LOG.
If you want to redirect BOTH error info and success info, do this:
>> error.log 2>>&1
This essentially says redirect standard out to a file, and send standard error to the same file.
Unfortunately, there is no general way to do this; this depends very strongly on the command to be executed.
There are programs that work as they should: Standard output is sent to stdout, error output to stderr; if the command executed with no errors, errorlevel is 0, other than zero otherwise.
Then there are programs that set the errorlevel correctly, but send all outpout to stdout.
Then there are programs that don't set an errorlevel if they encounter an error; those might or might not use stderr (but mostly they won't, if they don't even bother with the errorlevel).
Then there are programs that return a positive outcome by setting an errorlevel; depending on the (positive) result of the command, a different errorlevel might be set. Higher errorlevel might indicate an error.
Then it's very good practice in batch files to not use SomeCommand.exe >>error.log in a batch; makes later changes a lot easier. Instead, define the log file at the beginning as a variable, and use that; and use quotation marks.
set LogFile=S:\ome\Directory\e
SomeCommand.exe 2>>"%LogFile%"
As for the first category (the net ... command, for example), the handling is easiest: simply redirect the stderr output to your logfile:
SomeCommand 2>>"%LogFile%"
The second category needs a bit more attention; you can save the output in a temporary file, adding it to your error log if an error occured:
set TempFile=%Temp%\error.tmp
SomeCommand.exe >"%TempFile%"
if errorlevel 1 type "%TempFile%" >>"%LogFile%"
The third category can be handled like the second, with a "find" for a line indicating an error involved:
set TempFile=%Temp%\error.tmp
SomeCommand.exe >"%TempFile%"
find "An error occurred" "%TempFile%"
if not errorlevel 1 type "%TempFile%" >>"%LogFile%"
The fourth category can be handled like one of the other ones, depending on the program's behaviour.
I want to add that this is not a solution forcing accept on something just to make your number's look better. I was monitoring this to see if anything new was posted, but I was away for better than a week and come back to find this.
-= NOT SOLVED =-
Because it can't be, there is no good solution at present time.
Actually, I think I gave a pretty exhaustive explanation about how to handle the different possibilities a program can indicate an error.
Considering that there's no standard error handling, it's rather obvious that you can't just add the same few lines to your existing batch files to catch the error output of any program you're using.
Please be aware of the fact that "Sorry, this is not feasible.", even though it's probably not what you wanted to hear, can very well be a valid answer to a question.
oBdA
Then you know that there is actually not an exact answer to this. Surely you do because none of these method's return exactly what's needed because it's impossible at current time and date. There's like 256 error code's more or less from what i've read. I'm not an ameteur but asked this in frustration in a moment of time although I solved it via another method to suit my need's. That's the reason I was just monitoring for awhile.
You would have been the one I would have awarded points to eventually cause I was looking and thinking of a reply
but this force accept to make their number's look better is what i'm griping about. You can see I've answered ? here myself but just not lately since I'm working on too much right now. I'm not a point hound cause it's just the helping thing to me.
Business Accounts
Answer for Membership
by: VeegertxPosted on 2004-09-10 at 23:14:37ID: 12033228
If I could add this to top of .cmd file so I could just open them all and add it.
Double Points