Pkg Execution Works in VS but not in SQL

I'm able to execute a package in VS Pro on my machine. However when I upload it to the sql server and try to execute the package directly it fails with:

Error: The product level is insuficient for component "...." (3129)
Error: The product level is insuficient for component "...." (5411)

The first component is a DataReader Source which is consuming an ODBC (Noble Systems ATOMIX Driver) connection and the second component is a DataConversion object. Anyone know why this would work running it on my pc in VS but not when I execute it from SQL on the same machine?

This is a silly question but are SSIS components installed on your sql server?

The error message looks similar to an error message I had once. I was trying to execute maintenance plans (which uses SSIS) and I had not installed the components.

|||

Jason's suggeston is a good one. You only need to install client components off the CD in order to build packages. You need to install SSIS to execute them outside of BIDS/VS.

-Jamie

|||

Yes, SSIS is installed. I can log into the service and can successfully run and schedule 'hello world' packages. As a developer I'm locked out of this system but I am trying to get access to the app logs to see if they reveal something.

I'm really at a loss. Since I'm executing the package it should be using the odbc driver from my pc as well as the dsn config right? Based on my description of the objects that threw the error(s) am I trying to use a feature that is only available in the enterprise edition?

|||

How are you executing the package?

Donald

|||

from within SMS-->Stored Packages-->MSDB--><Subfolder>--><MyPackage>

I right click on package and select Run Package.

thanks,
Scott

|||All components work in VS reguardless of the version required to run those components. The version checks come in only when you run the package outside the VS environment. What version of SSIS is installed on the server?|||

v.9.0.1399 (pre SP1)

|||Sorry, what product level. Also, list all the types of components in the entire package.|||

Ah, sorry about that.

All of the following components are installed on a single Win3k server (flavor and sp level n/a but I can find out if necessary) Sql standard edition:

Database Engine
SSIS
SSRS

|||

One - I got this message when running the package on my local machine with Enterprise Manager connected to the server.To fix this, you need to install the SSIS Service on your local machine. When you installed SQL 2005, you only installed the workstation components and the workstation product level is missing some components. Installing the SSIS Service will include the components needed to run SSIS on your local machine.

Two - If you are remote in to your server and you are getting this message, then you might have a Fuzzy lookup task that only works with the Enterprise Edition.

Hope that help.

|||Does anyone know if this will be a licensing issue?|||

Installing the SSIS component locally on my machine resolved this issue. However, I'm concerned about this behavior (i.e. not being able to execute a package that is on a server from a remote machine via Mgt Studio).

Maybe someone at Microsoft can answer this:

If I have a full install of the client tools and even a full install of VS05 Pro, why do I need to explicity installl the SSIS server component on my local machine to run packages located on a remote server (sql 2005 standard w/out sp1)? I spent a lot of time troubleshooting this error (as did a number of members of this forum) and I can't help but think that this should have worked out of the box.