Integration service package :- Production Level Too Low Error

1 view
Skip to first unread message

crazy

unread,
Dec 30, 2009, 1:45:16 AM12/30/09
to DotNetDe...@googlegroups.com
Hi All,
Gud morning!!

Using  integration service package , I have cretaed one package .
when I run this package from developement environmet(visual studio 2005) its working fine( job like reading  data from a file and importing to database. )
 
When I try to execute the package from the Bin folder (double  click on the .dtsx file) it is showing some error like
 
"SSIS Error code :DTS_E_PRODUCTION LEVELTOO LOW .The production level is insufficient for component Flat File Destination ".
"SSIS Error code :DTS_E_PRODUCTION LEVELTOO LOW .The production level is insufficient for component Merge Join ".
 .........................................................................................
............................................................................................
 
From the same machine, from  visual studio 2005 I can able  run the same package and do the import job.
How can i solve this issue?
Thanks in advance..

--
"People who never make mistakes, never do anything."

Crazy

Peter Smith

unread,
Dec 30, 2009, 9:27:34 AM12/30/09
to dotnetde...@googlegroups.com
Wow, something that actually took a little bit of searching to find info out about.

After a few attempts, simply using "The production level is insufficient" as my search phrase gave me successful hits.

http://blogs.msdn.com/michen/archive/2006/11/11/ssis-product-level-is-insufficient.aspx seems fairly canonical. Here's the excerpt:

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.

Bold underlined italics added.

Back to waiting for the DB guy to switch over our packages to SSIS. :)
Reply all
Reply to author
Forward
0 new messages