"Warning: Document contains one or more extremely long lines ..."

Hi,

i created a large Integration Services Package. When I start now the Project an open the Package, I get a Message

"Document contains one or more long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

What does this Message mean for me? Which mistake did I?

Thanks a lot

What was a bug prior to SP1. It is just a warning, so for the time being you can just ignore it. That should disappear from new created packages after you apply the latest SP

Here is another discussion about it:

http://forums.microsoft.com/MSDN/Search/Search.aspx?words=Warning%3A+Document+contains++extremely+&searchKey=&lcid=1033&searchscope=forumscope&siteid=1&ForumID=80&ForumGroupID=-1

sql

"The package contains two objects with the duplicate name" - Package Created in UI - D

I've begun to get the above error from my package. The error message refers to two output columns.

Anyone know how this could happen from within the Visual Studio 2005 UI? I've seen the other posts on this subject, and they all seemed to be creating the packages in code.

Is there any way to see all of the columns in the data flow? Or is there any other way to find out which columns it's referring to?

Thanks!

I just can think about an ugly way; switch to the XML view (right click on the package name in the explorer) and do a 'find' within the code...

Perhaps you created some outpust by hand using the advanced editor of some components

|||

Well, next time it will be the XML editor. The problem went away "by itself".

"Report is being generated" but never does...

I have created a report and deployed it successfully to a seperate machine with SSRS on. Both my dev machine and the SSRS machine are in the same workgroup. I can then Browse to the Report Manager though IE and click & run the report (The connection is using integrated security). The report requires a single parameter to be entered which once done works successfully. The report has a single table, an inbedded image and a few static fields in the report header.

If I however add a report viewer control to an aspx test form all is not well. As soon as the page opens I am prompted to enter the parameter which is good news as it shows there has been some communication with the SSRS metabase. I then click the view report button. Using Profiler I have proved that the report Stored Proc. is running with the correct parameter value. The report viewer however seems to hang and only displays "Report is being generated" without displaying the results. It does this even with a timeout set of 1000ms.

I don't think this is a security issue as both the Report Manager works and the test form prompts me for the parameter and effectively runs the report SP. I can only assume it is a problem with returning the report to the browser.

Does anyone have any insight?

Regards

Anthony Kay

Hmmh, 1000ms ist just a second, thats not much. Try to have a look in the log information, it should present jyou more details about opening the report, querying the data, rendering the report. There you might see where the execution stops.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

Seem to have the same problem.

Anthony, did you find a solution for this already?

thanks in advance

Wouter van Dis

|||I found later that it was specific to my development machine as my colleagues still worked. I have found no explaination for this as yet.

"Report is being generated" but never does...

I have created a report and deployed it successfully to a seperate machine with SSRS on. Both my dev machine and the SSRS machine are in the same workgroup. I can then Browse to the Report Manager though IE and click & run the report (The connection is using integrated security). The report requires a single parameter to be entered which once done works successfully. The report has a single table, an inbedded image and a few static fields in the report header.

If I however add a report viewer control to an aspx test form all is not well. As soon as the page opens I am prompted to enter the parameter which is good news as it shows there has been some communication with the SSRS metabase. I then click the view report button. Using Profiler I have proved that the report Stored Proc. is running with the correct parameter value. The report viewer however seems to hang and only displays "Report is being generated" without displaying the results. It does this even with a timeout set of 1000ms.

I don't think this is a security issue as both the Report Manager works and the test form prompts me for the parameter and effectively runs the report SP. I can only assume it is a problem with returning the report to the browser.

Does anyone have any insight?

Regards

Anthony Kay

Hmmh, 1000ms ist just a second, thats not much. Try to have a look in the log information, it should present jyou more details about opening the report, querying the data, rendering the report. There you might see where the execution stops.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Seem to have the same problem.

Anthony, did you find a solution for this already?

thanks in advance

Wouter van Dis

|||I found later that it was specific to my development machine as my colleagues still worked. I have found no explaination for this as yet.

"Renaming package" dialog

I created a new SSIS solution, right-clicked the default name "Package.dtsx" (under SSIS Packages), then renamed it. A dialog appears asking "Do you want to rename the package object as well"?

What are they referring to and what are the consequences of doing/not doing so?

Barkingdog

In Visual Studio you rename a file - the *.dtsx file. However, the SSIS package is an object in the file. So if you don't rename the object you could have a package file called MySuperPackage.dtsx containing a package object called MyOldPackage. Try saying no to the dialog once and check the name property of the package in the properties window - select the package by clicking in the background of the object expolorer.

Analysis Services has the same issue with cubes and other objects. The objects are defined in XML and have a name property - which can be different from the filename of the xml.

For this reason, when renaming packages, you should use the designer - do not just rename them in the file system.

Donald

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)
Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"product level is insufficient" message during flat file import

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

CJ

"Pending" status for Data-driven Subscription

An issue with the 'Status' column of the 'Subscription' tab in the Report Manager.
I created Data-driven Subscriptions for some of the reports, and I scheduled the reports using shared schedule. The scheduling is working fine and all the reports are getting generated daily.
The issue is with the status of the report subscriptions under subscription tab, it shows as PENDING even after the report is generated.
I restarted the ReportServer database, it didn't served my purpose. The status never changes .

When do the subscription status changes to PENDING?
What needs to be done to change the PENDING status?
Is this the bug with the Report Manager?

Appreciate your timely help. TIA
Did you find a solution for this? I'm having the same issue.|||I didn't find any solution yet. If you find any, do share the same .
|||

There seems to be a SOAP Solution, But I've never used SOAP (Except in the Shower..LOL..sorry lame joke) , I'm having a hard time getting the MSDN Example to work. I can't get vb to recognize the ReportingService2005 class. heres the link if you want to take a look. http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsmanagementservice2005.reportingservice2005.listsubscriptions(SQL.90).aspx

Code Snippet

Dim rs As New ReportingService2005()
rs.Credentials = System.Net.CredentialCache.DefaultCredentials

Dim extSettings As ExtensionSettings
Dim desc As String
Dim active As ActiveState
Dim status As String
Dim eventType As String
Dim matchData As String
Dim values As ParameterValue() = Nothing
Dim subscriptions As Subscription() = Nothing
Dim extensionParams As ParameterValueOrFieldReference() = Nothing

Try
subscriptions = rs.ListSubscriptions("/SampleReports/Employee Sales Summary", "myDomain\myUserName")

If Not (subscriptions Is Nothing) Then
' Retrieve properties for the first subscription in the list.
rs.GetSubscriptionProperties(subscriptions(0).SubscriptionID, extSettings, desc, active, status, eventType, matchData, values)

Console.WriteLine("Description: {0}", desc)
Console.WriteLine("Status: {0}", status)
Console.WriteLine("EventType: {0}", eventType)
Console.WriteLine("matchData: {0}", matchData)
Console.WriteLine("Extension: {0}", extSettings.Extension)

extensionParams = extSettings.ParameterValues

If Not (extensionParams Is Nothing) Then
Dim extensionParam As ParameterValueOrFieldReference
For Each extensionParam In extensionParams
Console.WriteLine((CType(extensionParam, ParameterValue).Name + ": " + CType(extensionParam, ParameterValue).Value))
Next extensionParam
End If

If Not (values Is Nothing) Then
Dim pv As ParameterValue
For Each pv In values
Console.WriteLine("Name: {0}", pv.Name)
Console.WriteLine("Value: {0}", pv.Value)
Next pv
End If
End If

Catch e As SoapException
Console.WriteLine(e.Detail.OuterXml)
End Try

|||

Any help on this issue?

|||

Are you sure that this isn't a client-side caching issue in your browser? That would potentially out-last restarting the reportserver database.

IAC if you are seeing "Pending" In your browser, whether it is browser-cached or webapp-cached this would not have much to do with restarting the database. Even server-side it could be the ReportManager webapp that is caching the value. IOW, if it is a server-side cache, and if you restart the RS instance (rather than the database) you would see the change.

>L<

"Pending" status for Data-driven Subscription

An issue with the 'Status' column of the 'Subscription' tab in the Report Manager.
I created Data-driven Subscriptions for some of the reports, and I scheduled the reports using shared schedule. The scheduling is working fine and all the reports are getting generated daily.
The issue is with the status of the report subscriptions under subscription tab, it shows as PENDING even after the report is generated.
I restarted the ReportServer database, it didn't served my purpose. The status never changes .

When do the subscription status changes to PENDING?
What needs to be done to change the PENDING status?
Is this the bug with the Report Manager?

Appreciate your timely help. TIA
Did you find a solution for this? I'm having the same issue.|||I didn't find any solution yet. If you find any, do share the same .
|||

There seems to be a SOAP Solution, But I've never used SOAP (Except in the Shower..LOL..sorry lame joke) , I'm having a hard time getting the MSDN Example to work. I can't get vb to recognize the ReportingService2005 class. heres the link if you want to take a look. http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsmanagementservice2005.reportingservice2005.listsubscriptions(SQL.90).aspx

Code Snippet

Dim rs As New ReportingService2005()
rs.Credentials = System.Net.CredentialCache.DefaultCredentials

Dim extSettings As ExtensionSettings
Dim desc As String
Dim active As ActiveState
Dim status As String
Dim eventType As String
Dim matchData As String
Dim values As ParameterValue() = Nothing
Dim subscriptions As Subscription() = Nothing
Dim extensionParams As ParameterValueOrFieldReference() = Nothing

Try
subscriptions = rs.ListSubscriptions("/SampleReports/Employee Sales Summary", "myDomain\myUserName")

If Not (subscriptions Is Nothing) Then
' Retrieve properties for the first subscription in the list.
rs.GetSubscriptionProperties(subscriptions(0).SubscriptionID, extSettings, desc, active, status, eventType, matchData, values)

Console.WriteLine("Description: {0}", desc)
Console.WriteLine("Status: {0}", status)
Console.WriteLine("EventType: {0}", eventType)
Console.WriteLine("matchData: {0}", matchData)
Console.WriteLine("Extension: {0}", extSettings.Extension)

extensionParams = extSettings.ParameterValues

If Not (extensionParams Is Nothing) Then
Dim extensionParam As ParameterValueOrFieldReference
For Each extensionParam In extensionParams
Console.WriteLine((CType(extensionParam, ParameterValue).Name + ": " + CType(extensionParam, ParameterValue).Value))
Next extensionParam
End If

If Not (values Is Nothing) Then
Dim pv As ParameterValue
For Each pv In values
Console.WriteLine("Name: {0}", pv.Name)
Console.WriteLine("Value: {0}", pv.Value)
Next pv
End If
End If

Catch e As SoapException
Console.WriteLine(e.Detail.OuterXml)
End Try

|||

Any help on this issue?

|||

Are you sure that this isn't a client-side caching issue in your browser? That would potentially out-last restarting the reportserver database.

IAC if you are seeing "Pending" In your browser, whether it is browser-cached or webapp-cached this would not have much to do with restarting the database. Even server-side it could be the ReportManager webapp that is caching the value. IOW, if it is a server-side cache, and if you restart the RS instance (rather than the database) you would see the change.

>L<