All,
Using the Business Intelligence Development Studio, I migrated a
DTS package from SQL Server 2000. When I run the packaged from BIDS,
it worked beautifully.

In Management Studio, I created a new job so that this SSIS
package can run weekly. After setting up the job and ran it, I
received an error.

So, I thought I'd try executing the package from the command line
using DTEXEC. Got the same error. The error is below

for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights
reserved. Started: 11:26:46 AM Error: 2008-04-18 11:26:47.98
Code: 0xC004706C Source: Copy Data from Results to Results Task
DTS.Pipeline Description: Component "component "Data Conversion
1" (68)" could not be created and returned error code 0x80070005. Make
sure that the component is registered correctly. End Error Error:
2008-04-18 11:26:48.62 Code: 0xC0048021 Source: Copy Data from
Results to Results Task Data Conversion 1 [68] Description: The
component is missing<c/> not registered<c/> not upgradeable<c/> or
missing required interfaces. The contact information for this
component is "Data Conversion;Microsoft Corporation;Microsoft
SqlServer v9;

Please help!

Thanks,
Jeremy

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

I have seen this occur when SSIS was not installed on the server.

What type of task are you running in the jobstep? When you run the dtexec
is it on the server? In a jobstep?

"cappjr (AT) gmail (DOT) com" wrote:

On Apr 18, 9:01*pm, SusanMSDN <SusanM... (AT) discussions (DOT) microsoft.com>
wrote:
I do know that SSIS is installed.

You'll have to forgive my ignorance here on SSIS. Having been a DTS
user for so long, SSIS seems Greek to me. All I did was migrate the
DTS package over from 2000 into 2005. I'm not sure what you mean by
"jobstep". When I ran dtexec, I did do it from the server.

Since I'm not sure what you mean by "jobstep", I'll just tell you what
the Control Flow and Data Flow are doing.

Control Flow: The first step is doing an OLEDB connection to an Excel
file that is on the server and creates the table in excel. Then the
last step connects to the SQL database and imports the selected
columns into excel. Like I said, this runs fine when I run it from BI
Dev Studio.