July 10, 2006 at 8:07 am
After applying service pack4 on SQL2000 test server we experienced problem in running jobs through enterprise manager on the DTS step. The messsage received from DTS failure is:
1)Error: -2147220460 (80040414); Provider Error: 0 (0) Error string: Cannot find specified package in the storage location specified. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 713 OR
2)Error: -2147220455 (80040419); Provider Error: 0 (0) Error string: Access to package properties requires entry of package owner password. Error source: Microsoft Data Transformation Services (DTS) Package Help file: sqldts80.hlp Help context: 713
DTS step runs successfully if manually ran.
Has anyone else experienced this problem or have any suggestions?
Thanks
Ollie Steele
July 10, 2006 at 2:46 pm
A few ideas:
1. Are you executing the package from a structured storage file or is it saved in SQL? Sounds like it's a structured storage file. Try saving it in SQL and see if this makes a difference. Also try opening it in designer and resaving from an SP4 client to storage file. Can you provide the job step details?
2. Did you create the job by right clicking on the package and scheduling it? If so try recreating the job in ths fashion from an SP4 client?
3. Run DTS interactively on the machine instead of scheduling it as a job. This would rule out an identity issue with SQLAGENT.
4. Try running the DTS interactively from a remote workstations (DTS is really a client side process). Try running it from a SP4 client and SP3. This might rule out it being a server side issue.
July 11, 2006 at 7:31 am
Below are answers to your comments/questions. Thanks for responding.
1) Package saved in sql. Always has been.
2) Package is run as a step in a sql agent job. We issue an operating system command DTSRun . . .
3) We have run job interactively
4) We have run job interactively from both a remote client and the server itself. It runs fine on an SP3 client and fails on the SP4 client.
We believe the issue is that SP4 corrupted the environment. Has anyone experienced that? How plausible does it sound that we may have downloaded a bad SP4?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply