Re: DTS Packages fail when executed from Jobs
- From: v-sguo@xxxxxxxxxxxxxxxxxxxx (Sophie Guo [MSFT])
- Date: Tue, 17 May 2005 13:54:06 GMT
Hello,
Based on my research, there are several possible causes of this issue.
Please follow these steps to see if the issue can be resolved:
Action Plan 1 - Modify the path of Dtsrun.exe
1. Expand the server that is running SQL Server in SQL Server
Enterprise Manager.
2. Expand Management, expand SQL Server Agent, and then expand
Jobs.
3. Right-click the problematic Job, and then click Properties.
4. Click the Steps tab, and then click Edit.
5. Modify the run line to include the full path to DTSRun.exe. If
the path contains a space, you have to use quotes (" ") for the
path. For example:
"C:\PROGRAM FILES\MICROSOFT SQL SERVER\80\TOOLS\BINN\Dtsrun.exe"
/~E080989ED67CC54E9931C07DC3282FDA
Please search for the Dtsrun.exe file on your computer to
determine the correct path.
6. Run the job manually by right-clicking the job and then
clicking Start Job. Does it still fail?
Action Plan 2 - Run the DTS Package on the server rather than on
a client workstation.
Is the DTS Package run from a client workstation or directly on
the Server? When the package is run as a scheduled job, the
package is always run on the server. When you run the package
from the DTS Designer in SQL Enterprise Manager (SEM), the
package is running on the computer where you are seated.
To isolate this issue, we need to have the package run on the
server. Please logon the server from console as the SQL Server
service startup account and run the DTS package manually, thus
the package will be running on the server. Does it fail at this
point?
Action Plan 3 - Have a member of sysadmin own the job.
The security context in which the job is run is determined by the
owner of the job. To isolate any permission issues, please make
the necessary changes so that:
1. The SQL Server service startup account and the SQL Server
Agent service startup account are the same Windows account which
has local administrative privileges.
2. Logon the SQL Server box as the account mentioned above.
3. Create a scheduled job for the DTS package. Verify that the
owner of the job is the account mentioned above.
4. Run the package manually and run the job manually, what is the
result?
Action Plan 4 - Place all the data resources on the SQL Server
box.
If the database resides on another computer, please create
a new database and a new table on the SQL Server box,
create a new DTS package to import data from the newly created
table to a SQL table, run the package manually and then run it as
a job, what is the result?
Action Plan 5 - Apply the latest service pack of SQL Server 2000.
Please refer to this article to do this:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
http://support.microsoft.com/?id=290211
For additional information, please read the following articles:
318819 PRB: A DTS Package Raises Exceptions or Stops Responding
When You Run It
http://support.microsoft.com/?id=318819
290077 FIX: DTS Scheduled Job Does Not Complete After First Run
http://support.microsoft.com/?id=290077
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- References:
- DTS Packages fail when executed from Jobs
- From: Matt
- Re: DTS Packages fail when executed from Jobs
- From: Allan Mitchell
- Re: DTS Packages fail when executed from Jobs
- From: Matt
- DTS Packages fail when executed from Jobs
- Prev by Date: Analisis Services Processing Task not on 64-bit SQL Server
- Next by Date: DTS ERROR 8004206A
- Previous by thread: Re: DTS Packages fail when executed from Jobs
- Next by thread: Re: DTS Packages fail when executed from Jobs
- Index(es):
Relevant Pages
|
