January 23, 2002 at 1:02 am
I get the following error from a DTS package running inside a scheduled job.
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: Copy Data from Activities to [Prospects1].[dbo].[Activities] Step
DTSRun OnError: Copy Data from Activities to [Prospects1].[dbo].[Activities] Step, Error = -2147217887 (80040E21)
Error string: The property 'Use Encryption for Data' is not supported.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 700
Error Detail Records:
Error: -2147217887 (80040E21); Provider Error: 0 (0)
Error string: The property 'Use Encryption for Data' is not supported.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 700
etc etc etc
The package takes data from access and puts it into sql server 7.o - created via DTS wizard.
I have searched for the cause of "Use Encryption for data not supported" and all I could find was at SQLDTS.com which said it had to do with MDac inconsistencies between machines. I recreated the package using the same level of Mdac on my box as on the server (2.5) and the error still occurs.
Incidently the package runs ok when called directly from VB, and from enterprise Manager. But when I schedule it in the agent, it screws up.
I also changed ownership of the package to sa but still it does not execute - without error that is from a job. For your info we are running SQL Server on windows 2000 SP2.
Does anyone know the problem - I am sure it is quite small.
Cheers and thanks for a response.
Jeremy Rathbun,
Mirvac Group,
Sydney
January 23, 2002 at 12:01 pm
Is this a copy objects task? If so, I've had numerous problems with those.
Steve Jones
January 23, 2002 at 3:31 pm
No I am just copying tables across from access to sql server. The tables already exist in sql server , all I am doing is importing data.
quote:
Is this a copy objects task? If so, I've had numerous problems with those.Steve Jones
February 5, 2002 at 4:59 pm
Try the most current MDAC on the server. Sometimes the MDAC can be corrupt, so even if you are runniong the same revision the server may have a flaw it a dll or other system file.
February 7, 2002 at 3:26 am
I spent quite a bit of time on this problem. The have only found 1 reliable solution.
You need to actually create the DTS package and schedule the job all on your server. It will then run fine.
For some reason SQL Server 7.0 has serious problems using the information you supply when creating the DTS from your machine. When you the job runs on the server it then does not seem to know what or where your "link" is.
Hope this helps.
Chuck Maracle
February 13, 2002 at 5:03 am
If you are running SQL on a NON Windows 2k box then you need to make sure you UN CHECK the box for SQL 2000 Encryption when building the package. It is displayed somewhere along the way when running throught the IMPORT wizard via Enterprise Manager. Simple enough... I forget a lot on one out Win NT 4.0 boxes.. Not sure why MS does not just realize it is RUNNING on NT 4.0. The issue is that it requires the server as well as the system doing DTS to be running Windows 2k.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply