Solved

DTS not running in job - SQL 2008

Posted on 2010-08-24
2
998 Views
Last Modified: 2013-11-10
Hi,
After migrating server from SQL 2000 to SQL 2008 we also copied the DTS  packages and scheduled them in SQL agent job via DTSRUN.

one of the package fails which I cannot seem to get to work from SQL agent however if I execute it from command promt with the same DTSRUN cmd, it works. Here's the error from job:

Executed as user: SRVSQL\sqlaccservice. DTSRun:  Loading...   DTSRun:  Executing...   DTSRun OnStart:  DTSStep_DTSTransferObjectsTask_1   DTSRun OnProgress:  DTSStep_DTSTransferObjectsTask_1; Scripting objects for Transfer; PercentComplete = 0; ProgressCount = 0   DTSRun OnProgress:  DTSStep_DTSTransferObjectsTask_1; Scripting objects for Transfer; PercentComplete = 0; ProgressCount = 0   DTSRun OnError:  DTSStep_DTSTransferObjectsTask_1, Error = -2147221504 (80040000)      Error string:  Invalid OLEVERB structure         Error source:  Microsoft Data Transformation Services (DTS) Package      Help file:  sqldts80.hlp      Help context:  1100      Error Detail Records:      Error:  -2147221504 (80040000); Provider Error:  0 (0)      Error string:  Invalid OLEVERB structure         Error source:  Microsoft Data Transformation Services (DTS) Package      Help file:  sqldts80.hlp      Help context:  1100         Error:  -2147221504 (80040000); Provider Error:  0 (0)      Error string:  Invalid OLEVERB structure         Error source:  Microsoft Data Transformation Services (DTS) Package      Help file:  sqldts80.hlp      Help context:  5700         Error:  -2147467259 (80004005); Provider Error:  0 (0)      Error string:  [SQL-DMO]CreateFile error on 'destinationServer.database.LOG'.       Error source:  Microsoft SQL-DMO      Help file:  SQLDMO80.hlp      Help context:  1132      DTSRun OnFinish:  DTSStep_DTSTransferObjectsTask_1   DTSRun:  Package execution complete.  Process Exit Code 1.  The step failed.

Thanks in advance for your help!
0
Comment
Question by:Rainbow002
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 12

Accepted Solution

by:
mcv22 earned 500 total points
ID: 33509378
Might be related to permissions. Make sure that the SQL agent service account has appropriate permissions on the source and destination locations.
0
 

Author Closing Comment

by:Rainbow002
ID: 33509411
I resolved it by giving modify permissions to SQL agent service account to c:\program files\microsoft sql server\80\tools\
0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question