Product Level Is Insufficient Error Message On Deployment Machine
Oct 10, 2006
Hi,
I have a SSIS package which I had created on my machine, running Windows XP with SQL2K5 Development Edition. If I run the package through the BI studio or by clicking the dtsx file, it runs without any issues.
When the same package is deployed onto another machine (SBS 2003 with SQL2K5 Workgroup Edition), the package errors with the above message when the dtsx file is clicked and run. However, if the source files are opened up and ran from within the BI studio, it all runs OK.
I've ran through the SQL setup file (through Add/Remove Programs) and Integration Services is installed, however the SSIS service is not on the machine. I've read however that the service is not required to run the package, so what gives? Plus, this doesn't explain why running it through BI studio is fine but not when run by itself.
The data flow task that the package fails on contains 2 SQL sources, 1 SQL destination, 3 sorts, 1 multicast and a couple of merge joins. Are some of these pieces not available in the Workgroup Edition? This would still not explain why it can run in the BI studio on that machine...
This thing is driving me crazy. I have a simple flat .txt file I'm trying to import into a DB, and this USED to work perfectly with SQL Server 2000. With 2005, I get "product level insufficient."
I've read that and I've looked around. It seems like the solution is to actually connect to the Windows box that the server itself is running on (where SSIS is installed) and import there?? But that's a pain.. that means I'd have to Remote Desktop into the server EVERY time I want to import a text file. Surely there's some other way to do this??
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:
I have read previous threads on this, still not working.
New installation of SQL Server 2005 on a Windows Server 2003 box. I have installed SP1 on both the server & the client, do I have to re-create the package?
Configuration: Windows XP Pro with SQL 2005 Workgroup Sp2
Hi, we have a package that runs fine in BI Studio but fails with the following error when executing it using DTExec.
Code: 0xC00470FE Source: Data Flow Task DTS.Pipeline Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Derived Column" (10660).
The package imports a CSV into a table mapping some columns. The MSDN article at http://msdn2.microsoft.com/en-us/library/ms143761.aspx describes features supported by different versions.
The article says OLE DB source/destination adapters are supported in WG edition but a couple of lines later seems to imply that all source/destination adapters are not supported in WG.
Could you clarify whether stuff like import of a csv into a table with some column mappings should work in WG edition? Also if we have a legacy SQL 2K package doing the same thing, will that work in WG edition? Thx.
Features/Integration Services Enhancements EE (32-bit) DE (32-bit) EE (64-bit) DE (64-bit) SE (32-bit) WG (32-bit) SSE (32-bit) SSEA (32-bit) SE (64-bit)
SQL Server Import and Export Wizard and supporting connections, source and destination adapters, and tasks
Yes
Yes
Yes
No
Yes
Execute SQL Task
Yes
Yes
Yes
No
Yes
OLE DB Source and Destination Adapters
Yes
Yes
Yes
No
Yes
SSIS command prompt tools
Yes
Yes
Yes
No
Yes
SSIS Package Designer
Yes
Yes
Yes
No
Yes
Legacy support for DTS packages
Yes
Yes
Yes
Yes
Yes
SSIS Service
Yes
Yes
No
No
Yes
All other source and destination adapters, tasks, and transformations, except for those listed below
How do i see what SSIS i have? Threads seem to point that SSIS needs to be installed to fix the following error:
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 "Destination - DataID" (34). (SQL Server Import and Export Wizard)
Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (55). (SQL Server Import and Export Wizard)
- Prepare for Execute (Stopped)
- Pre-execute (Stopped)
- Executing (Success)
- Copying to `DataID` (Stopped)
- Post-execute (Stopped)
- Cleanup (Stopped)
But when i choose Help-> About i get Microsoft SQL Server Management Studio 9.00.1399.00 Microsoft Analysis Services Client Tools 2005.090.1399.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.832 Operating System 5.1.2600
while executing the package following error message is received as :
Error: 2006-07-28 15:12:36.60 Code: 0xC00470FE Source: Data Flow Task DTS.Pipeline Description: The product level is insufficient for component "Data Conversion" (202). End Error
and at the end as :
DTExec: The package execution returned DTSER_FAILURE (1).
Same error appers while executed from Integration Services - ->stored packages - - >name of the package -> mouse right button, run package.
But the same executes perfectly from visual studio, where it is developed.
Running eval. edition of Sql Server Standard 2005. "Insufficient product level" error is thrown during validation phase of an OleDBCommand data flow task. This task type is not licensed in Sql Server 2005 standard? The component runs a very simple sql update statement against a one row table in Sql Server 2005.
If it works from BIDS, should it not work from dtexec.exe on the same box?
Does dtexec run under the security context of the logged in user?
I am receiving the following error when I try to execute an SSIS package that is saved to a structured file. I am using DTExec to execute the package.
Description: The task "Initialize Variables" cannot run on this edition of Integration Services. It requires a higher level edition.
After some research, I was able to find a supporting article in SQL Server 2005 BOL at http://msdn2.microsoft.com/en-us/library/aa337371.aspx
The issue was resolved by installing the Enterprise Edition of SQL Server Integration Services (Windows Service) on the local server (server where the package is saved and executed from). However, this goes against my original anticipation that the SSIS Windows Service would only need to be installed on a machine where I needed to store packages and/or monitor package execution. Not if I wanted to execute packages.
Unfortunately, my package is using advanced options (as identified in the BOL article previously referenced).
I am trying to run dtexec on some DTSC packages I created using SSIS. I keep getting the error "The product level is insufficient for the component". Anybody know what this means?
I´m having this trouble (The product level is insufficient for component "flat file.txt") executing a ssis package using dtexec from a store procedure.
The database is SQL Server 2005 Express Edition with Advanced Services SP1 and Microsoft SQL Server 2005 Express Edition Toolkit SP1.
If anyone knows how to solve this problem i would be very thankful
We are trying to run SSIS DTSX packages from a VB.Net 2005 application and we get this error : The product level is insufficient for component.
The server is SQL 2005, the clients (for which the VB application is run from) have SQL 2005 Client tools (since there are running XP).
I know this is a known issue, as SP1 corrected the import/export problem in Management Studio, can we expect a similar fix when using SSIS locally on a client's machine via a VB.Net application and SQLServer 2005 assemblies ?
We are currently in the process of migrating our VB.Net 2003/ SQL2000 applications to VB.Net 2005/ SQL2005 and do not want to change the way we process our data, as we expected 2005 version to have the same functionality as 2003.
Hi. I'm using SQL Server 2005 Management Studio to try and run an SSIS package. One step blows up with this error: "The product level is insufficient for component "data conversion 1"". I checked out the thread here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=112469&SiteID=1&PageID=0
However, after installing SP1, the program is still giving me the error. I'm running the package from my WinXP Pro SP2 workstation. What am I missing? Thanks.
I developed some packages using BIDS. I only have the Workstation Components installed on my PC, SQL Server 2005 Enterprise Edition, SSIS, SSAS, etc.. are all installed on the server.
I can run all the packages fine, if I run from my own PC.
I deployed the packages to the server, but when I try to run the packages using SQL Server Management Studio, they don't work.
I'm getting an error message "The Product level is insufficient for component "xxxxx". I get this error for each component created in my package.
All the data files are on the server, even when I run using my own PC.
I am very new to SSIS. I have created a small application in which the data flow task contains OLEDB source, derived column and datareaderdest.When i run dtexecui.exe and execute the package i am getting these errors
The product level is insufficient for component "Derived Column"
The product level is insufficient for component "DataReaderDest"
But i am not geeting any warning or error when i debug the solution.
I developed a package in BIDS which simply runs a query, does a data conversion on one field, then exports to Excel. This works fine in BIDS. When I import the package to the server, I receive the Product Level is Insufficient error for both the data conversion component and the excel destination.
I have verified that SSIS is installed and the service is running. I have verified that SP1 is installed.
Some other things about the environment: - Running x64 versions of Windows and SQL 2005 - Did not install the workstation tools on the server
I read other threads with this problem and one solution was to install SP1 on the workstation. Our server is running 9.00.2047(SP1) and my workstation SSMS version is 9.0.2047.00 so I'm assuming it's SP1 and I am still getting this error.
To make matters worse, I have jobs set up to run these packages ON the server, but they aren't working either because I have '...error authenticating proxy...Logon failure unknown user name or bad password'. I'm trying to use my Windows login because it has sysadmin rights; I created credentials, assigned them to a proxy under SSIS Package Execution; in the SQL Agent log I get the error '...SQLServer Error: 22046, Encryption error using CryptProtectData.'.
I have created an SSIS On my PC, That extracts data out of Lotusnotes. When I run it manaully from Visual studion-execute package, it works just fine. However, when I go tO Management studio, chose the servername, then go to Stored Package-MSDB- And chose Packagename, and hit Run PKG from there, it gives me the error below. Server has 2005 AND IS WINDOWS 2003 OS.
The product level is insufficient for component "datareader source"
Can you tell me why the same pkg will work fine when executed from Visual studio-But when I go the run it from Storedpackages-MSDB-it fails.
I have created a dts (.dtsx file). which gets the data from my log file and insert into my sql 2005 table. In dts i am using 'Flat File Source' and 'OLE DB Destination' (becoz i need to acess my db remotely). When i execute this through 'SQL Server Business Intelligence Development Studio' it's working fine but when i execute this through my c# code, it throws me an error 'The product level is insufficient for component Flat File Source (1)'.
I have created a Integration Services package that takes a table in a database, and transfers it to a flat file. This package has successfully run through visual studio 2005 as a .dtsx package, and given the output that I expected.
However, now, I am trying to excecute the package (as xml) using C#, and I am receving this error:
Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/DTS.Pipeline : The product level is insufficient for component "Flat File Destination" (31).
I do not understand how a working package would have this kind of error.
Considering that it runs when I do not use C# code to execute the package means that I have SSIS properly installed, and I have the proper versions (or it should not execute ever). I have SP1 for both SQL Server 2005, and Visual Studio 2005 installed.
Other packages that I have created using C# code also have the same problem.
I have a production machine and a developer machine with Ms SQL Server Management Studio I connected remotly to the integration services hosted in the production machine. Then I exported a package and then, when it was executed, I had the following error:
"the product level is insufficient for component excel source"
So I thought that it was because the excel file that I was trying to upload was in the developer machine, so I pointed the Excel Data Source to a shared folder but I still having the same error.
I have read another posts but I'm afraid because the conclusion is that I have to install the SSIS in the developer machine, I hope I misunderstood the solutions!!!
I am using MS Access 2003 SP2 to maintain some data tables. I use SSIS to transfer them to SQL Server 2005, Enterprise Edition.
When I run the SSIS package from within Visual Studio 2005, the package runs without error.
When I try to run the same SSIS package by double-clicking on it in my File System (which invokes the Execute Package Utility, Version: 1.0) none of the tables get copied. Instead all I receive is a message for each table,
Error: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Data Conversion 1" (49).
The only data conversion I perform is double-byte characters to single-byte characters.
Bob Bojanic, MSFT, made a few suggestions about this in another thread -- but I have created this new thread to help focus on this specific issue. In particular, he asked if we have installed the complete SSIS support for SQL Server 2005, Enterprise Edition, and my network support and database support staff assure me that such complete SSIS support was installed.
Are others having this problem?
Dan
(I just took a look at some of the transformations in the Data Conversion task, and many of them are using an Output Alias identical to the Input Column name. Might that be causing the problem? I will try changing the Output Alias for some tables and see if they then transfer correctly. The "identical name" Output Alias values were created by the Migration Wizard for a DTS 2000 package.)
While I am trying to install SQL server 2005 I get the following message - "Machine does not have a product that matches the installation package". The installation does not occur.
I am using Windows 2000 Professional SP4 and using 32 bit installer - SQLServer2005SP2-KB921896-x86-ENU.exe
hi we have a link server....andthe user credentials are not being trasfered to link server.....anythoughts??we get the following error messageServer message 18542 level 16 state 1--Posted using the http://www.dbforumz.com interface, at author's requestArticles individually checked for conformance to usenet standardsTopic URL: http://www.dbforumz.com/error-messa...pict266240.htmlVisit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=915273
All of a sudden our reports stopped working today giving this error:
Server Error in '/Reports' Application.
Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Security level already defined for 'RosettaMgr'.
Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407
If I comment out the lines 22 - 25 in the web.config file the reports start to work again, but I am reluctant to do this as I'm not sure what the implications would be if left..
I have the developer edition of MS SQL and applied SP4 to it. Here's what I get when I execute SELECT @@Version:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2) According to the readme, here are the version numbers for each service pack:
SQL Server 2000 Version and Level @@VERSION Product Level
SQL Server 2000 Original Release 8.00.194 RTM
Database Components SP1 8.00.384 SP1
Database Components SP2 8.00.534 SP2
Database Components SP3, SP3a or MSDE 2000 Release A. 8.00.760 SP3
Database Components SP4 8.00.2039 SP4 Do I trust the Version Number or the Product Level? Anyone know what the story is? TIA.
Hi All, I am trying to restore a DB from my production to Standby server..it gives me a mesage "Msg 3105, Level 16, State 1 Data on dump will not fit into current database. Need 6500 Mbyte database."
The production server DB size is 5000MB and I have increased the size of standby DB to 6500MB but still the same message...
I have a problem while trying to deploy my packages that are configured in ProtectionLevel=EncryptSensitiveWithUserPassword
I use the Deployment Utility to deploy my packages. I set the password when deploying and the deplyment works fine. But I run the packages I have the following error : " Failed to decrypt an encrypted XML node because the password was not specified or not correct."
Hiya! I have a static, optimistic ADO recordset in VB6 selecting rows from a view definition which selects fields (includes all primary keys!) from two tables using a right join on the table whose fields I absolutely need. My update affects only one table (the right one), yet I am getting an error "Insufficient key column info for updating or refreshing", NativeError is 1007, which does not match any SQL error in BOL, and source gives me Microsoft Cursor Engine, although my cursor type is fine for updating. Any clues?
My company has a database that is throwing a weird error. We've tried reinstalling both the OS and the SQL instance, and the error still persists. We think this error might have to do with some .NET code we've written to run on the box, but I cannot find anything out on the internet about it. Here is the Enterprise Manager Error Log:
Insufficient memory available.. Error: 17803, Severity: 20, State: 4 Query Memory Manager: Grants=0 Waiting=0 Maximum=97638 Available=97638 Global Memory Objects: Resource=912 Locks=42 SQLCache=67 Replication=2 LockBytes=2 ServerGlobal=20 Xact=12 Dynamic Memory Manager: Stolen=2138 OS Reserved=1048 OS Committed=1026 OS In Use=1022 Query Plan=1777 Optimizer=0 General=1066 Utilities=12 Connection=262 Procedure Cache: TotalProcs=488 TotalPages=1787 InUsePages=542 Buffer Counts: Commited=5168 Target=131072 Hashed=1917 InternalReservation=191 ExternalReservation=0 Min Free=128 Visible= 131072 Buffer Distribution: Stolen=351 Free=1113 Procedures=1787 Inram=0 Dirty=599 Kept=0 I/O=0, Latched=23, Other=1295 WARNING: Failed to reserve contiguous memory of Size= 65536.
I can find information if I do a Google search on "Error: 17803, Severity: 20" But as soon as I add "State: 4" to the query I get no results. Also, the articles that I have seen that give the same error messages (but different states) tend to deal with servers that have more than 4GB of memory. This server has ONLY 4GB of memory and in order to try and resolve this issue, we have limited the server to 1GB of physical memory to no avail.
