Re: Problem with locked log file produced by batch file
- From: "dbareis [Windows Installer MVP]" <dbareis@xxxxxxxxx>
- Date: 5 Dec 2006 12:45:47 -0800
Hi,
My guess for the day is that your previous schedule is still running
(and perhaps you don't auto terminate it if required). "Process
Explorer" might be quite useful to examine the running processes.
Bye,
Dennis
Ragnar Midtskogen wrote:
Hi,
I have set up backups on all of our servers, running batch files by using
Windows Scheduled Tasks.
I redirect the output from the batch file to a log file.
A couple of times recently I have found that the Scheduled Task ran but the
batch file didn't. The log file was not even opened.
I have no idea what caused the log file to be left in a state like that, but
the last thing the batch file does is to FTP the backup file to another
server, so my guess is that it could be a dropped FTP connection. I have no
error handling for the FTP code.
I finally found that the log file was locked. I tried to delete it but got
the message that the file was in use.
BTW, The ST runs the batch file as the same user as I log on to the server
with (Through Terminal Server client).
Is there a way to free the file, short of rebooting the server?
Any help would be appreciated.
Ragnar
.
- Follow-Ups:
- Re: Problem with locked log file produced by batch file
- From: Ragnar Midtskogen
- Re: Problem with locked log file produced by batch file
- References:
- Problem with locked log file produced by batch file
- From: Ragnar Midtskogen
- Problem with locked log file produced by batch file
- Prev by Date: Re: Problem with locked log file produced by batch file
- Next by Date: Re: Problem with locked log file produced by batch file
- Previous by thread: Re: Problem with locked log file produced by batch file
- Next by thread: Re: Problem with locked log file produced by batch file
- Index(es):
Relevant Pages
|
|