"Your upgrade is blocked"

I am getting the following error message when I tried installing the 2005 Developer Edition from the MSDN kit. I previously installed the 2005 Express Edition, and it worked just fine, so I thought that the install failed as it was at a lower version than the Express Edition. I uninstalled the SQLExpress Edition, however, when I try to install SQL Server 2005 again, I get the following message:

Name: Microsoft SQL Server 2005 Tools

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:

Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

Name: Microsoft SQL Server 2005 Tools

Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:

Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

I have also installed Visual Studio NET, and I wonder if some component in the Studio app is holding back the SQL Server install. I have uninstalled all SQL components several times already, and I keep on getting this message.

Gregory

Gregory

Gregory, when you go to Add/Remove Programs, do you see any SQL 2005 installation info there? If so, what versions does the report say?

Also, what version of SQL Server Express did you install? RTM or SP1?

Thanks,
Samuel Lester (MSFT)

sql

"where" in DTS

i try use "where" to filter record for result but when i run , there is a message error task.

select flattened

(select * from predict ([model name].[table name], include_statistic) where [$support] >0 ) as ph

from

[model name]

prediction join

.....

can onebody help me?

What is the error?|||It could be that you need to say "INCLUDE_STATISTICS" rather than "INCLUDE_STATISTIC"|||

error that it messesage: " there an error occur in task". no more information to know what error and where error in query.

what's different between INCLUDE_STATSTICS and INCLUDE_STATSTIC?

|||

The difference is one is a keyword, and the other is an error.

You can try to execute your query in SQL Management Studio to see the full error message, although it should be available from SSIS as well.

If you are doing this on the pipeline and you want to validate your DMX syntax simply eliminate the PREDICTION JOIN clause,

e.g.

select flattened

(select * from predict ([model name].[table name], include_statisticS) where [$support] >0 ) as ph

from

[model name]

|||

sory, but first, i writed like that but still have error. and it didn't message with an clear error to know what error. how can i do now?

i try a model to show other products when someone choose a product. my result have many record that same.

e.g:

productid otherProductid

1 34

1 74

1 89

2 34

2 74

2 89

3 34

3 74

3 89

4 56

4 101

4 73

....

what wrong with my model and how i should do to my event?

thanks

|||

This is not an error, rather a feature. This occurs when your model doesn't contain rules for the data in your input. The system is designed that if you ask for 5 recommendations, you will get 5 recommendations. If the input you provide doesn't resolve into any rules (or enough rules) you will get the most popular results. I.e. it looks like item 34 is the most popular in your training set.

There are a few ways to alleviate this issue. One is to change the minimum_support and minimum_probabilty such that you generate more rules. Another is to filter results that are not based on rules. A description on how to do this is at http://blogs.msdn.com/jamiemac/archive/2006/04/19/579409.aspx

Thanks

"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

"visual studio is busy"

I keep getting this balloon message along with 'please contact microsoft if you continue to get this message' when using SSIS

Here's the news: I continually get the message so here I am 'contact MS'

There is no link in the balloon indicating quite how I should contact MS.

Any one else have this problem?Id be more than willing to help, but would need some more info. does this happen when you first open up the package? Sometimes this is caused by a long validation. If you can better explain the package this happens with/ when it happens maybe I can help|||

The package under development is very simple:

open an xls and put the data in a table

there are about 4 connection managers

that's it, the whole thing is only about 200k

|||Make sure that there isn't another window open that got sent to the background.

"visual studio is busy"

I keep getting this balloon message along with 'please contact microsoft if you continue to get this message' when using SSIS

Here's the news: I continually get the message so here I am 'contact MS'

There is no link in the balloon indicating quite how I should contact MS.

Any one else have this problem?Id be more than willing to help, but would need some more info. does this happen when you first open up the package? Sometimes this is caused by a long validation. If you can better explain the package this happens with/ when it happens maybe I can help|||

The package under development is very simple:

open an xls and put the data in a table

there are about 4 connection managers

that's it, the whole thing is only about 200k

|||Make sure that there isn't another window open that got sent to the background.

"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".

"Table '?' could not be loaded. Column '?' does not exist"

Hi,

I am getting message while modifying one table in SSMS like "Table '?' could not be loaded. Column '?' does not exist" . Howevery particular column exist in table and even i am able to modify it with T-SQL.

Any Idea?

Please post the error message, including the stack trace from the error window.

Jens K. Suessmeyer.

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

Jens,

Thanks for your reply. I got the work around. I created another table with same schema with different name and also created all FKs and constrains with different name and it worked.

"Table ''?'' could not be loaded. Column ''?'' does not exist"

Hi,

I am getting message while modifying one table in SSMS like "Table '?' could not be loaded. Column '?' does not exist" . Howevery particular column exist in table and even i am able to modify it with T-SQL.

Any Idea?

Please post the error message, including the stack trace from the error window.

Jens K. Suessmeyer.

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

Jens,

Thanks for your reply. I got the work around. I created another table with same schema with different name and also created all FKs and constrains with different name and it worked.

"Sometimes"- Error message

I've a SSIS Package, what executes a stored procedure, who calculates a lot of stuff with a recursive algorithm (TSQL). Sometimes the package aborts with this error message:

"Syntaxfehler, Berechtigungsversto? oder anderer allgemeiner Fehler". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The first few german words mean: "Syntax error, Security error or general error"...

If i restart the packages, the error usually does'nt appear again. All releated data are'nt changed in the meantime. I can not reproduce the the error and a think, it depends on the connection (but SSIS and SQL Server are running on the same virtual maschine). By the way, the executed stored procedure does not have any resultset what is given back...

Every idea is very welcome...

Torsten

Since you say there is a lot of complexity in the stored procedure and that it only happens sometimes, I wonder if it isn't something in the procedure causing the problem (a concurrency-induced deadlock, a random number causing a divide by zero, the recursion limit being reached, etc.)

I suggest you try running a profiler trace and see if any errors are getting thrown by the procedure which aren't being reported by SSIS.
|||

Thanks for your message!

Running the profiler reduces the performance in a way, that it would take a fews days...

When talking about recusion limit, what is ment by it? In my recursion i've an hirarchie with not more then 10 levels. the max-recursion option i've set to 500 and increased to 1000. Doesn't matter - i get the error sometimes like before... A division by zero is not possible, i'm only summerizing. A deadlock doesn't make sense, i'm not changing the data while running these process (and no other does).

But furthermore i get an other errormessage (sometimes), is it possible that they are combined in an unhappy way?

"The number of threads required for this pipeline is 107, which is more than the system limit of 64. The pipeline requires too many threads as configured. There are either too many asynchronous outputs, or EngineThreads property is set too high. Split the pipeline into multiple packages, or reduce the value of the EngineThreads property. "

Where is the place to increase the system limit of 64 threads? Sp_configure says following:

name min max config run_value

Ad Hoc Distributed Queries 0 1 0 0
affinity I/O mask -2147483648 2147483647 3 3
affinity mask -2147483648 2147483647 3 3
affinity64 I/O mask -2147483648 2147483647 0 0
affinity64 mask -2147483648 2147483647 0 0
Agent XPs 0 1 0 1
allow updates 0 1 0 0
awe enabled 0 1 1 0
blocked process threshold 0 86400 0 0
c2 audit mode 0 1 0 0
clr enabled 0 1 1 1
cost threshold for parallelism 0 32767 5 5
cross db ownership chaining 0 1 0 0
cursor threshold -1 2147483647 -1 -1
Database Mail XPs 0 1 0 0
default full-text language 0 2147483647 1031 1031
default language 0 9999 1 1
default trace enabled 0 1 1 1
disallow results from triggers 0 1 0 0
fill factor (%) 0 100 0 0
ft crawl bandwidth (max) 0 32767 100 100
ft crawl bandwidth (min) 0 32767 0 0
ft notify bandwidth (max) 0 32767 100 100
ft notify bandwidth (min) 0 32767 0 0
index create memory (KB) 704 2147483647 0 0
in-doubt xact resolution 0 2 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 64 0 0
max full-text crawl range 0 256 4 4
max server memory (MB) 16 2147483647 4000 2147483647
max text repl size (B) 0 2147483647 65536 65536
max worker threads 128 32767 128 0
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 0 16
nested triggers 0 1 1 1
network packet size (B) 512 32767 4096 4096
Ole Automation Procedures 0 1 0 0
open objects 0 2147483647 0 0
PH timeout (s) 1 3600 60 60
precompute rank 0 1 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote admin connections 0 1 0 0
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 600 600
Replication XPs 0 1 0 0
scan for startup procs 0 1 0 0
server trigger recursion 0 1 1 1
set working set size 0 1 0 0
show advanced options 0 1 1 1
SMO and DMO XPs 0 1 1 1
SQL Mail XPs 0 1 0 0
transform noise words 0 1 0 0
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 0 0
user options 0 32767 0 0
Web Assistant Procedures 0 1 0 0
xp_cmdshell 0 1 0 0

|||

Torsten_Katthoefer wrote:

But furthermore i get an other errormessage (sometimes), is it possible that they are combined in an unhappy way?

"The number of threads required for this pipeline is 107, which is more than the system limit of 64. The pipeline requires too many threads as configured. There are either too many asynchronous outputs, or EngineThreads property is set too high. Split the pipeline into multiple packages, or reduce the value of the EngineThreads property. "

Good grief! You must have a huge Data Flow. You need to break that up into multiple smaller data flows. Increasing the thread limit is not a good solution (even if it is possible). A raw file destination can be placed in a data flow to persist the pipeline to the disk, and then another data flow started with a raw file source to pick up where the other left off. I think you'll find your performance will be much better.
|||

Hmm, i don't think that this will help, because the package only starts a stored proc what makes all these calculations. The amount of data transported through the SSIS is not really much... So there is nothing to put into a raw file.

It would like to increase the thread limit, only to observe these process. Is it possoble to do this?

|||

Torsten_Katthoefer wrote:

Hmm, i don't think that this will help, because the package only starts a stored proc what makes all these calculations. The amount of data transported through the SSIS is not really much... So there is nothing to put into a raw file.

It would like to increase the thread limit, only to observe these process. Is it possoble to do this?

Well then something must be really messed up for SSIS to think it needs 107 threads. I don't know for sure, but I doubt you can raise that limit. If your package so simple, I would delete it and start over. Something in there is not right.

"Setup has detected one or more instances of SQL Server 2000..."

Tried to install the CTP and got a message stating that 2008 won't coexist with 2000. I had an instance of 2000 Developer Edition on here that I was testing some stuff with. I removed that, rebooted, and I still get the same message. Am I to assume that you can't even install 2008 if you've got the 2000 client tools installed, or am I missing something else?
Have a look at section 2.1.1 of the readme file, it states "To work around this issue, manually remove the registry key at HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80, and then re-run SQL Server "Katmai" June CTP Setup." Note that this will likely break the 2000 tools so uninstall them first or better yet use VPC/VMWare to create an isolated environment. CTP's often don't play well with other versions and can be difficult to uninstall cleanly.|||Ah ha, the actual CTP ISO has an outdated readme that doesn't mention that part. I bet that'll do the trick. Thanks.
|||

Hi,

I also got the same warning message about side by side running of SQL2k and Katmai June CTP. But I could not find any note about SQL 2000 in the readme documents of the installation.

|||Yeah, the readme file that's included with the installation is slightly out of date. I think this is the one you need: http://connect.microsoft.com/SQLServer/Downloads/DownloadDetails.aspx?DownloadID=6834

|||

Hi David,

Thanks for the link. Great help!

"Setup has detected one or more instances of SQL Server 2000..."

Tried to install the CTP and got a message stating that 2008 won't coexist with 2000. I had an instance of 2000 Developer Edition on here that I was testing some stuff with. I removed that, rebooted, and I still get the same message. Am I to assume that you can't even install 2008 if you've got the 2000 client tools installed, or am I missing something else?
Have a look at section 2.1.1 of the readme file, it states "To work around this issue, manually remove the registry key at HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80, and then re-run SQL Server "Katmai" June CTP Setup." Note that this will likely break the 2000 tools so uninstall them first or better yet use VPC/VMWare to create an isolated environment. CTP's often don't play well with other versions and can be difficult to uninstall cleanly.|||Ah ha, the actual CTP ISO has an outdated readme that doesn't mention that part. I bet that'll do the trick. Thanks.
|||

Hi,

I also got the same warning message about side by side running of SQL2k and Katmai June CTP. But I could not find any note about SQL 2000 in the readme documents of the installation.

|||Yeah, the readme file that's included with the installation is slightly out of date. I think this is the one you need: http://connect.microsoft.com/SQLServer/Downloads/DownloadDetails.aspx?DownloadID=6834

|||

Hi David,

Thanks for the link. Great help!

"service unavailable" error message

I recently changed the service account for the SSRS service, after which I restarted IIS & reporting services.

Now, I get an error message that says "Service Unavailable" whenever i try to load up http://localhost/Reports

Event viewer looks clean...what's wrong?After lots of playing around, I recreated the AppDomains for SSRS and it seemed to fix the problem..

"Provider Load Failure" in SSRS Configuration

I am receiving the "Provider Load Failure" message when I start the SSRS Configuration Tool on my report server.

As suggested on other threads, I have checked the reportingserviceswmi.dll and it is version 2005.90.1399.0 and the WMI service is running.

Any suggestions on what to do next?

I solved this myself by piecing together a couple of other posts.

I tried some of the remedies that basically entailed reregistering all of the wmi dll's and none of them worked but then I searched out "reportingserviceswmi.dll" and found that it wasn't in the c:\windows\system32\wbem folder. I tried reregistering it in the folder where it resided and it didn't fix the problem. Next I copied reportingserviceswmi.dll to the wbem folder and registered it there and the problem was resolved.

Example: c:\windows\system32\regsvr32 c:\windows\system32\wbem\reportingserviceswmi.dll

"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