|
Home > Archive > MS SQL Server DTS > September 2005 > DTS Package won't execute when Scheduled as a Job
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
DTS Package won't execute when Scheduled as a Job
|
|
| Jeff Booth via SQLMonster.com 2005-09-27, 8:24 pm |
| I have created a DTS package that is made up of one ActiveX script that opens
a .NET web page and generates a variety of reports, converts them to PDF and
copies them to certain locations in our network. If I execute this DTS
package manually everything works perfectly. Although when I go to schedule
this package to run on a daily basis the job will show that it executed and
completed successfully, but in actuality the DTS package never gets fired.
At first I thought this might be a permissions issue, but permissions seem to
be correct. Is there a limitation in SQL Server that does not allow for a
scheduled job to fire a DTS package with just an ActiveX script embedded?
| |
| Sue Hoegemeier 2005-09-27, 8:24 pm |
| The problem you describe is 99% of the time related to
permissions - or job ownership/agent service account which
effectively becomes permissions.
When you can run it from your PC manually, it means it
executes fine from your PC and under your security context.
When it runs as a job, it executes from the server and under
the security context of SQL Agent (if owned by a sysadmin)
or the proxy account. Take a look at the following Knowledge
Base article for more info:
INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
-Sue
On Tue, 27 Sep 2005 22:13:41 GMT, "Jeff Booth via
webservertalk.com" <u14351@uwe> wrote:
>I have created a DTS package that is made up of one ActiveX script that opens
>a .NET web page and generates a variety of reports, converts them to PDF and
>copies them to certain locations in our network. If I execute this DTS
>package manually everything works perfectly. Although when I go to schedule
>this package to run on a daily basis the job will show that it executed and
>completed successfully, but in actuality the DTS package never gets fired.
>At first I thought this might be a permissions issue, but permissions seem to
>be correct. Is there a limitation in SQL Server that does not allow for a
>scheduled job to fire a DTS package with just an ActiveX script embedded?
|
|
|
|
|