Command scheduler , batch files, and file piping.

I'm executing a batch file from the Command Scheduler (on server1) which executes ok until I add file piping. The batch file resides on server2, but it executes on server1.
The batch file maps a network drive and then sends ECHO command output to a file in the current directory. The commands used are:

net use y: \\my_server\share
cd folder1\folder2\folder3
ECHO ***** Start of TEST BATCH FILE Processing. ***** >test.log
ECHO | MORE | DATE | FIND "date is" >>test.log

Test.log is to be created in the \\my_server\share\folder1\folder2\folder3 directory. Everything was ok until I added the piping for logging purposes. Now I have a mapped network drive that I can't get rid of. It shows up in Explorer and at the command prompt. The drive letter is available both places, but I can't delete it from Explorer or at the command promt. NT says that the driver letter isn't available when I use 'net use y: /delete'.

My first question is "How can I get the piping in the batch file to work properly?"

And my second question is "How can I easily get rid of the 'phantom' driver mappings?" (I'd like to avoid rebooting as this is an in-use server.)
Who is Participating?
dragonfireConnect With a Mentor Commented:
I suspect that the problem with the share is that is is in use in a 'hidden' command prompt (One that was started by the scheduler). You can tell by making sure any command prompts are closed (And no scheduled processes are running) then running Task Manager and looking for CMD.EXE under processes - If you are sure nothing else is using it, kill it.

The reason why I think this happened (And your batch script doesn't work) is that the command line:
ECHO | MORE | DATE | FIND "date is" >>test.log
doesn't make sense without an interactive session, a simpler way is:
ECHO.| DATE | FIND "date is" >>test.log
(Don't miss the '.' )

I know this works in schedule scripts as I use it. (With some even more odd command structures using the FOR command to select just the date code).
I think the problem is that you are using a share with scheduler.
scheduler runs under system account and therefor cannot access shares.

I think your mapping doesn't work correctly during the running of the batch file on scheduler.

Try to add to your net use command /user:username password
net use y: \\server\share /user:username password

This should do it...
jpasAuthor Commented:
Sorry. I should have mentioned that the Schedule service is logging on as a user. The batch file executing works ok from the scheduler until I add the file piping to the batch file. Your previous suggestion of using a user logon for the schedule service (or mapping a driver using a user logon), both worked, so I think I'm past that problem.
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

1. I couldn't understand what is the problem with the test.log file. could you explain again ?
2. Try to add the net use y: /delete at the end of your script (after your next boot...)
jpasAuthor Commented:
1. I'm trying to pipe output from the batch file into the test.log logfile. I thought everything was working ok until I added the piping (>test.log) command to the end of the ECHO statements. These don't seem to be working and NT gets confused about whether the drive is mapped or not. Now I'm running into the message 'The process cannot access the file because it is being used by another process.'

I'll do some more testing to try to narrow the problem down.

2. The end of the batch file does release the driver mapping.
To pipe the date why not just use?

jpasAuthor Commented:
Using 'date /t' does look better and is easier to use. Thanks.

The problem with piping to a particular file seems to be caused by something else having the file open. Everytime the batch file tries to access it, a message displays that the file can't be accessed because it's being accessed by another process. That must be from an earlier attempt at logging. Checking Task Manager didn't reveal any hidden command sessions, and I didn't see anything in Server Manager indicating the file was open.

Using a different file name clears up the problem. So it is working now.
You could try putting a

NET USE \\my_server\IPC$ /DELETE

in your batch file before connecting the drive.  This should close any existing connections and give you a clean start.
jpasAuthor Commented:
The drive mappings still hang around even after using NET USE \\<my_server>\IPC$ /DELETE. I'm guessing they'll clear up the next time the machine is rebooted.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.