Scheduled Tasks after Service Pack 4

[Guest]

I had a scheduled task setup to run a macro from Microsoft Access to update tables in a database. It used to work fine until I ran Windows update and installed Service Pack 4 on Windows 2000 Server
It does not matter what account I am logged in as. It just shows running but doesn't run. I used to be able to see it open up access and run the macro and then close. It also date stamps a table so I am certain it isn't running in the background either

The following is the command line info for the task

"C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE" "\\nt4\private\db\gslimport.mdb" /WRKGRP "\\nt4\private\DB\Secured.mdw" /user "update" /X impor

Starts in "C:\Program Files\Microsoft Office\Office11

Please help...

 

[Pegasus \(MVP\)]

I had a scheduled task setup to run a macro from Microsoft Access to

update tables in a database. It used to work fine until I ran Windows
update and installed Service Pack 4 on Windows 2000 Server.

It does not matter what account I am logged in as. It just shows running

but doesn't run. I used to be able to see it open up access and run the
macro and then close. It also date stamps a table so I am certain it isn't
running in the background either.

The following is the command line info for the task:

"C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE"

"\\nt4\private\db\gslimport.mdb" /WRKGRP "\\nt4\private\DB\Secured.mdw"
/user "update" /X import

Starts in "C:\Program Files\Microsoft Office\Office11"

Please help....

Modify your batch file like so, then examine the two log files:

@echo off
echo %date% %time% Start of job > c:\test.txt
echo User=%Username%, path=%path% >> c:\test.txt
"C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE"
"\\nt4\private\db\gslimport.mdb" /WRKGRP
"\\nt4\private\DB\Secured.mdw" /user "update"
/X import 1>>c:\test.txt 2>>c:\test.err
echo %date% %time% End of job >> c:\test.txt

 

[Ricardo M. Urbano - W2K/NT4 MVP]

I had a scheduled task setup to run a macro from Microsoft Access to update tables in a database. It used to work fine until I ran Windows update and installed Service Pack 4 on Windows 2000 Server.
It does not matter what account I am logged in as. It just shows running but doesn't run. I used to be able to see it open up access and run the macro and then close. It also date stamps a table so I am certain it isn't running in the background either.

The following is the command line info for the task:

"C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE" "\\nt4\private\db\gslimport.mdb" /WRKGRP "\\nt4\private\DB\Secured.mdw" /user "update" /X import

Starts in "C:\Program Files\Microsoft Office\Office11"

Please help....

Shannon, I had issues w/ SP4 wiping out the credentials entered for
scheduled tasks. Just modify the properties of the task and reenter the
username and password for the task and see if that rectifies the
problem.

hth

 

[Guest]

I have been using scheduled tasks to launch the batch file successfully for over a month. Now it launches the task but never finishes the macro in access. MSACCESS.exe is running as a process and I have to manually end it. If I manually run the batch file it works fine. If scheduled tasks launches the job it hangs.