Hi,

I get the following error from the SSIS:
"The task ... cannot run on this edition of integration services. It
requires a higher level edition."

The package runs from my Visual Studio, but when
I deploy to the Integration Server which is not on my
PC it throws me this error.

I'll really appreciate any help.

Thank you very much in advance!

Hello Michael,

I understand that you get the error "cannot run on this edition of
integration services" when you deploy package to SSIS. If I'm off-base,
please let me know.

Before we go further, I'd like to confirm if you have full SSIS component
installed. What's the edition of SQL server you installed on the server?


Without SSIS install, with just Tools install, user can design and debug
packages, but can’t run packages stand-alone. Additionally some components
(like Fuzzy Lookup) require Enterprise license.

So the message is displayed in two situations:

SSIS was not installed, only Tools was installed on the machine.
User has Standard edition of SQL Server, and uses a component that requires
Enterprise edition.

related link:

http://forums.microsoft.com/MSDN/Sho...02141&SiteID=1

If you have any update, please feel free to let's know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Peter,

Thank you for the response.
My problem is that I can run/debug package in Visual Studio on my client PC,
but unfortunately it doesn't
run on the server which is not my workstation and I have Enterprise edition
installed on the server.

Best Regards,

Michael

"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Michael,

Thank you for your reply. I understand that you installed just Client Tools
on client machine, but did not install the SSIS in SQL setup on the client
machine. The Client Tools allow package to be designed and debugged, but
most tasks require installing SSIS. You may also want to install SSIS on
the client machine PC to test the situation.

IF the issue persists, you may try to create a new package with some simple
task to test the situatioin. Also, if you create package by using Business
Intelligence Developemnt studio on the server directly, does the issue
still occur?

Also, did you have SQL 2005 SP1 and latest cumulative hotfix package
installed on the server? If not, you may want to install SP1 and cumlate
package on both client/server to test.

918222 Cumulative hotfix package (build 2153) for SQL Server 2005 is
available
http://support.microsoft.com/default...b;EN-US;918222

919224 FIX: You may receive an error message when you install the
cumulative hotfix package (build 2153) for SQL Server 2005
http://support.microsoft.com/default...b;EN-US;919224

I look forward to your reply. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Hi,

Peter, thank you very much for your help.
After playing a little bit more with the issue I've found the solution and I
want to share it with community.
I was running the package by doing the following steps:
1) Connecting to Integration Services using Microsoft SQL Server Management
Studio.
2) Browsing to my stored packages.
3) Right clicking on the desired package and selecting Run Package. Here was
my mistake (and maybe others as well),
since the intuition says that by doing this procedure the package should run
on the server. However, this is not true
and it is also emphasized in the Execute Package Utility that the package
will run on the local PC (which in my case doesn't
have SSIS server installed on).

So, my suggestion is if you would like to run the package on the server,
then create a job in SQL Server Agent and run the package
using this job.

Best Regards


"Peter Yang [MSFT]" <petery (AT) online (DOT) microsoft.com> wrote

Hello Michael,

This has pretty much always been true. A lot os people get confused about
the difference between a storage location and an execution location.


Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Hello Michael,

Thank you for your sharing! This shall benefit the community. :-)

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====