July 30, 2002 at 12:37 pm
The following message is captured in the log...
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: Drop table [MISData].[dbo].[bupcfile] Step
DTSRun OnError: Drop table [MISData].[dbo].[bupcfile] 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: 1100
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: 1100
Error: -2147217887 (80040E21); Provider Error: 0 (0)
Error string: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0
DTSRun OnFinish: Drop table [MISData].[dbo].[bupcfile] Step
DTSRun OnStart: Create Table [MISData].[dbo].[bupcfile] Step
DTSRun OnError: Create Table [MISData].[dbo].[bupcfile] 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: 1100
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: 1100
Error: -2147217887 (80040E21); Provider Error: 0 (0)
Error string: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0
DTSRun OnFinish: Create Table [MISData].[dbo].[bupcfile] Step
DTSRun: Package execution complete.
August 6, 2002 at 9:22 am
I believe this is an MDAC (MS Data Access Components) related problem. Check that you have the correct MDAC version installed for your version of SQL. There is a "component checker" utility that you can run which will identify which MDAC version you are running.
August 7, 2002 at 9:56 am
Excellent...I checked the version of MDAC that it was running and it was 2.1 !!!
I have now upgraded to MDAC 2.6 and it works fine ...thanks for the advice.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply