Export Wizard Error

I am trying to use the Export Wizard to copy data from a SQL2k server
database to a SQL2005 database. My source and destination is SQL Native
Client and I am only interested in one table. Everything appears to be read
y
when I start the process.
However, when validating I keep getting the following error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: etc,etc.
Talks about retrieving the COM class factory and CLSID and the "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
What else do I need to check?Hi Roger
Have you saved this as a package? The exact text of your error is important.
I would guess there is possibly a datatype issue.
You could also try using oledb connection.
John
"Roger Denison" wrote:

> I am trying to use the Export Wizard to copy data from a SQL2k server
> database to a SQL2005 database. My source and destination is SQL Native
> Client and I am only interested in one table. Everything appears to be re
ady
> when I start the process.
> However, when validating I keep getting the following error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: etc,etc.
> Talks about retrieving the COM class factory and CLSID and the "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> What else do I need to check?|||John,
I tried using the OLEDB connection and still got the same error. Here is
the text of the error:
Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
the following error: "Retrieving the COM class factory for component with
CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the followin
g
error: 80040154.". Possible failure reasons: Problems with the query,
"ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.
It looks as if it is trying to execute a nameless query.
Any ideas?
tfyh
Roger.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Roger
> Have you saved this as a package? The exact text of your error is importan
t.
> I would guess there is possibly a datatype issue.
> You could also try using oledb connection.
> John
> "Roger Denison" wrote:
>|||Hi Roger
Error 80040154 is usally an issue with the COM component not being
installed, therefore you could try doing this on a different machine to prov
e
it is the local installation. You don't say which version you are running,
you may want to check if there is a service pack that could be installed if
you are not running on the latest.
John
"Roger Denison" wrote:
[vbcol=seagreen]
> John,
> I tried using the OLEDB connection and still got the same error. Here is
> the text of the error:
> Error 0xc002f210: Preparation SQL Task: Executing the query "" failed with
> the following error: "Retrieving the COM class factory for component with
> CLSID {7816B7A3-CD60-4539-BD38-C35AFC61F200} failed due to the follow
ing
> error: 80040154.". Possible failure reasons: Problems with the query,
> "ResultSet" property not set correctly, parameters not set correctly, or
> connection not established correctly.
> It looks as if it is trying to execute a nameless query.
> Any ideas?
> tfyh
> Roger.
> "John Bell" wrote:
>|||John,
I checked versions (9.0.1399) and everything seems to be in order. And
then, duh!, I noticed the SQL Server Agent on the destination wasn't running
.
tfyh
Roger.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Roger
> Error 80040154 is usally an issue with the COM component not being
> installed, therefore you could try doing this on a different machine to pr
ove
> it is the local installation. You don't say which version you are running,
> you may want to check if there is a service pack that could be installed i
f
> you are not running on the latest.
> John
> "Roger Denison" wrote:
>|||Hi
9.0.1399 is RTM there is currently SP2 and psot SP2 hotfixes which you
should consider deploying.
SQLAgent should not affect the migration wizard unless you are running as a
package as a job.
John
"Roger Denison" wrote:
[vbcol=seagreen]
> John,
> I checked versions (9.0.1399) and everything seems to be in order. And
> then, duh!, I noticed the SQL Server Agent on the destination wasn't runni
ng.
> tfyh
> Roger.
> "John Bell" wrote:
>