DTS Job fails when scheduled as Job (NOT a 269074 issue!)

#1

Please don't redirect me to KB269074. I've read it and either I am missing
something vital, or my problem really isn't covered by it!

I have a simple DTS package: a single execute process command that tries to
launch MS Access.Exe so that it can in-turn open a DB automatically, run some
code then shut itself down.

The DTS command is:
Win32 Process: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE
Parameters: c:\test.mdb

This works great when run manually.

If I try to schedule it, it fails.
I have tried changing the Scheduled Job Owner.

I am running a stand-alone laptop with Windows XP Home Edition and a
Developers Edition of SQL Server 2000 with SP3.

Why won't it run as scheduled? It starts and then just waits saying it is
executing step 1, but nothing actually happens. I can cancel the job, and in
either case no error messages are output anywhere. I have tried letting it
run automatically via a schedule and have triggered it manually from
Enterprise Manager.

Help!

#2

Andy,

The issue here may be application start directory. It would be different
when running DTS manually and from a job. To test that create a batch file:

cd\
C:
cd "Program Files\Microsoft Office\OFFICE11"
MSACCESS.EXE c:\test.mdb

Run this batch file from execute process task.

Ilya

"Andy A38a" <Andy A38a (AT) discussions (DOT) microsoft.com> wrote

Quote:

Please don't redirect me to KB269074. I've read it and either I am missing
something vital, or my problem really isn't covered by it!

I have a simple DTS package: a single execute process command that tries
to
launch MS Access.Exe so that it can in-turn open a DB automatically, run
some
code then shut itself down.

The DTS command is:
Win32 Process: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE
Parameters: c:\test.mdb

This works great when run manually.

If I try to schedule it, it fails.
I have tried changing the Scheduled Job Owner.

I am running a stand-alone laptop with Windows XP Home Edition and a
Developers Edition of SQL Server 2000 with SP3.

Why won't it run as scheduled? It starts and then just waits saying it is
executing step 1, but nothing actually happens. I can cancel the job, and
in
either case no error messages are output anywhere. I have tried letting it
run automatically via a schedule and have triggered it manually from
Enterprise Manager.

Help!

#3

The fact that it hangs makes me think it is waiting for user input. SQL
Agent does not support applications that have a UI. Try setting the SQL
Agent service to allow interaction with the desktop. I would expect you to
see some UI or error dialog. Any application that raises a UI for errors is
"not supported", as it will cause a hang scenario in the case of a problem.

Darren

"Andy A38a" <Andy A38a (AT) discussions (DOT) microsoft.com> wrote

Quote:

Please don't redirect me to KB269074. I've read it and either I am missing
something vital, or my problem really isn't covered by it!

I have a simple DTS package: a single execute process command that tries
to
launch MS Access.Exe so that it can in-turn open a DB automatically, run
some
code then shut itself down.

The DTS command is:
Win32 Process: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE
Parameters: c:\test.mdb

This works great when run manually.

If I try to schedule it, it fails.
I have tried changing the Scheduled Job Owner.

I am running a stand-alone laptop with Windows XP Home Edition and a
Developers Edition of SQL Server 2000 with SP3.

Why won't it run as scheduled? It starts and then just waits saying it is
executing step 1, but nothing actually happens. I can cancel the job, and
in
either case no error messages are output anywhere. I have tried letting it
run automatically via a schedule and have triggered it manually from
Enterprise Manager.

Help!

#4

Thanks Darren: setting the service to allow interacton with the desktop (via
Windows Service Manager) did the trick.

Much obliged.

"Darren Green" wrote:

Quote:

The fact that it hangs makes me think it is waiting for user input. SQL
Agent does not support applications that have a UI. Try setting the SQL
Agent service to allow interaction with the desktop. I would expect you to
see some UI or error dialog. Any application that raises a UI for errors is
"not supported", as it will cause a hang scenario in the case of a problem.

Darren

"Andy A38a" <Andy A38a (AT) discussions (DOT) microsoft.com> wrote in message
news:3517265C-028B-4CE1-99CE-789F223F9846 (AT) microsoft (DOT) com...
Please don't redirect me to KB269074. I've read it and either I am missing
something vital, or my problem really isn't covered by it!

I have a simple DTS package: a single execute process command that tries
to
launch MS Access.Exe so that it can in-turn open a DB automatically, run
some
code then shut itself down.

The DTS command is:
Win32 Process: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE
Parameters: c:\test.mdb

This works great when run manually.

If I try to schedule it, it fails.
I have tried changing the Scheduled Job Owner.

I am running a stand-alone laptop with Windows XP Home Edition and a
Developers Edition of SQL Server 2000 with SP3.

Why won't it run as scheduled? It starts and then just waits saying it is
executing step 1, but nothing actually happens. I can cancel the job, and
in
either case no error messages are output anywhere. I have tried letting it
run automatically via a schedule and have triggered it manually from
Enterprise Manager.

Help!

#5

There is always something to learn...

"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

Quote:

The fact that it hangs makes me think it is waiting for user input. SQL
Agent does not support applications that have a UI. Try setting the SQL
Agent service to allow interaction with the desktop. I would expect you to
see some UI or error dialog. Any application that raises a UI for errors
is
"not supported", as it will cause a hang scenario in the case of a
problem.

Darren

"Andy A38a" <Andy A38a (AT) discussions (DOT) microsoft.com> wrote in message
news:3517265C-028B-4CE1-99CE-789F223F9846 (AT) microsoft (DOT) com...
Please don't redirect me to KB269074. I've read it and either I am
missing
something vital, or my problem really isn't covered by it!

I have a simple DTS package: a single execute process command that tries
to
launch MS Access.Exe so that it can in-turn open a DB automatically, run
some
code then shut itself down.

The DTS command is:
Win32 Process: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE
Parameters: c:\test.mdb

This works great when run manually.

If I try to schedule it, it fails.
I have tried changing the Scheduled Job Owner.

I am running a stand-alone laptop with Windows XP Home Edition and a
Developers Edition of SQL Server 2000 with SP3.

Why won't it run as scheduled? It starts and then just waits saying it
is
executing step 1, but nothing actually happens. I can cancel the job,
and
in
either case no error messages are output anywhere. I have tried letting
it
run automatically via a schedule and have triggered it manually from
Enterprise Manager.

Help!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

DTS Job fails when scheduled as Job (NOT a 269074 issue!)

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

DTS Job fails when scheduled as Job (NOT a 269074 issue!) - 06-16-2005 , 05:34 PM

Re: DTS Job fails when scheduled as Job (NOT a 269074 issue!) - 06-17-2005 , 07:51 AM

Re: DTS Job fails when scheduled as Job (NOT a 269074 issue!) - 06-17-2005 , 09:38 AM

Re: DTS Job fails when scheduled as Job (NOT a 269074 issue!) - 06-20-2005 , 06:52 AM

Re: DTS Job fails when scheduled as Job (NOT a 269074 issue!) - 06-21-2005 , 08:32 AM