DTS not running in job - SQL 2008

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!
Rainbow002Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
mcv22Connect With a Mentor Commented:
Might be related to permissions. Make sure that the SQL agent service account has appropriate permissions on the source and destination locations.
0
 
Rainbow002Author Commented:
I resolved it by giving modify permissions to SQL agent service account to c:\program files\microsoft sql server\80\tools\
0
All Courses

From novice to tech pro — start learning today.