Facts:
I have a Windows 2003 Standard server that has SQL 2000 Standard installed.
Both MSSQL and ServerAgent services are running under a windows user.

Issue:
I created a simple DTS package, and I want to be able to run it in a
scheduled job. I have created the scheduled job for the package, but it fails
with
------
Executed as user: COMPUTERNAME\USER. ... DTSStep_DTSTransferObjectsTask_1
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
... Process Exit Code 1. The step failed.
------

What I have done:
If I change the services to run as Local System, then the job runs without
problem. But when I put it back to run as the Windows user the job fails.
I have followed the procedure to run the services as a user(Making the
change thru Ent Manager)
I have also applied by hand all the permissions that Microsoft says that the
user should have to be able to run the services.

I think that there is something else permissions related with that user that
is not allowing the job to run.

Please if anyone has any ideas, please let me know.

Thanks

JFR

"Invalid OLEVERB structure" is new to me, but appears to be VSS related. Is
VSS installed on the server correctly if you are trying to use it, and do
you have permissions?

One simple test is to logon to the server as your service account user, and
run the package from there by hand. This simulates the location and security
context as used when scheduled. It is still probably permissions related,
but maybe this way you will see the problem.

--
Darren Green
http://www.sqldts.com
http://www.sqlis.com


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