“Product level is insufficient”
“The task ……cannot run on this edition of Integration Services. It requires a higher level edition.”
Symbolic Name: DTS_E_PRODUCTLEVELTOLOW
The hexadecimal value for this error number = 0xC00470FE.
The error tells you that you have not installed SSIS on the machine where the package is running, probably you’ve only installed SQL Server and Workstation Components. Another possible reason is that the package uses components that require higher edition of SQL Server – e.g. Fuzzy and Data Mining transforms require Enterprise or Developer edition.
If you have installed Workstation Components, you can create, edit and debug packages in Business Intelligence Development Studio (BIDS). You can also run Import/Export Data Wizard and execute the resulting package inside the wizard. Other uses of SSIS (i.e. running with DTEXEC, inside Agent or custom tools) require full SSIS installation.
So to correct the problem, you either need to install SSIS on the production machine where package runs, or move the package execution to the machine where the full SSIS version is already installed.
Q: How do I check if I’ve installed SSIS?
A: One of the features installed with full SSIS, but not included in the Workstation Components setup is SSIS Service. So there are two simple ways to check if you’ve installed SSIS and if the SSIS service is present.
1. Open Computer Management or SQL Server Configuration Management, open SQL Server 2005 Services node. If you’ve installed SSIS, there should be a service called SQL Server Integration Services. If this service is missing, SSIS is not installed on this machine.
2. Go to Start menu > Run > Services.msc and look for “SQL Server Integration Services 10.0” for SQL 2008 and “SQL Server Integration Services” for SQL 2005
Q: But I can run the package inside Business Intelligence Development Studio – this means I have the SSIS installed, right?
A: Not really. When you install Workstation Components (including BIDS) you get a subset of SSIS that allows you to design and debug packages in BIDS. To run the package standalone (DTEXEC, as Agent Job, etc), you need the full SSIS installation.
Q: I’ve installed SQL Server Enterprise/Developer edition, including SSIS. Why I’m still getting this error?
A: Most likely, you try to run the package on a different machine (e.g. SSIS is installed on a server, and you try to run the package on a workstation, usually using SSMS). When you run DTExec.exe or DTExecUi.exe (right clicking on a package to run it via Object Explorer) the packages runs on the machine where you start it. Starting a package in Object Explorer does not run the package on a different server machine – it runs it locally.
You either need to install SSIS on the machine where you are trying to run the package from, or run the package on the server machine.
Q: In SQLServer 2005, I run Import/Export Data Wizard and select Execute the Package Immediately option, but execution fails with error “product level is insufficient…” What should I do?
A: Install service pack 2 or higher.
Q: I want to run SSIS on a client machine, without having to pay for/get a full SQL Server license just to run SSIS packages (outside the debugger).
A: In SQL 2005 and SQL 2008 licensing prohibits running DTExec or SSIS API’s on a client machine without having a licensed copy of SSIS installed as explained above. You can start jobs remotely using sp_startjob ‘jobname’ etc, and host in a webservice (there are security challenges with doing so) but you cannot “start” a package remotely or host it on a client machine without a licensed copy of SSIS installed.
The ways to start SSIS packages from a remote location are:
1. Could use SQL Agent jobs to run SSIS packages, and start the jobs via a query to
that SQL Server calling sp_start_job.
2. Could use a webservice to communicate with the SSIS server and remotely trigger
the package to run over there on the server.
The following blog also talks about similar issue and is worth having a look
Author : Debarchan (MSFT) , SQL Developer Engineer , Microsoft
Reviewed by : Jason (MSFT) , SQL Escalation Services, Microsoft