Approved: Fortect
If you notice the description, the ssis error code dts_e_productleveltolow. If the product is level i, the following operating instructions may help.
First published on MSDN December 10, 2009
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
Refusal:
“Product level is insufficient”
“Task …… Do not start Integration Services in this release. This requires a higher level of editing. ”
Symbolic name: DTS_E_PRODUCTLEVELTOLOW
Hexadecimalnca for this error number = 0xC00470FE.
Root Cause:
Permission:
So, to fix the problem, you need to either install SSIS in the package of a working production computer, or move the working package to a computer that already has the final version of SSIS installed.
FAQ:
Q: How can I make sure SSIS is installed?
A: One of the special features installed with full SSIS, but far from included in the configuration of the workstation components, might be SSIS. So, there are two easy ways to check that SSIS is installed and that SSIS is recognized.
1. Open Computer Management or SQL Server Configuration Management, open SQL Server 2005 Host Services. If you have SSIS installed, there must be another service called SQL Server Integration Services. If this service is not present, SSIS may not be installed on this computer.
2. Select Start Meal> Run> Services.msc and find “SQL for Server Integration Services 10.0” for SQL 2008and “SQL Server Integration Services” for SQL 2005. create
Q: I want to run SSIS on a client machine without paying / obtaining a full SQL Server license, just to run the SSIS product (outside of the debugger).
A: In SQL 2005 and SQL 09, the license prohibits running the DTExec or SSIS APIs on a client computer without substantially installed licensed copies of SSIS, as described above. You can start jobs remotely with sp_startjob ‘jobname’ etc. and host them in a real web service (there are security concerns with this), but you cannot ‘start’ the container remotely or host it on a proprietary machine without a licensed copies of SSIS.
Ways to run SSIS packages from a good remote location: