jchohio


Hi,

I am receiving the following error in Sql Job agent when I try to run an SSIS package : The task "Create Excel File" cannot run on this edition of Integration Services. It requires a higher level edition. It then goes on to tell me : The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. I have tried reseting the error count to allow for the "errors" , but it stills fails. The job suceeds in Visual Studio, but not when scheduled in Sql Management Studio. Any suggestions

Thanks,
J.



Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer


What SQL Server edition are you running on the server, and what edition are you running where you are executing/developing the packages

The Standard version won't work when uploading the packages to a developer or enterprise edition of SQL Server.






Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer

Please review this document as well:

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx





Re: SSIS Higher Level Edition error when run in a Sql Job

jchohio

Sql 2005 Enterprise Edition. The version of SQL/SSIS is 9.00.2176.00 (which I believe is the cumulative Post SP-1 hotfix). I am using an SSIS project via VS 2005, which is version 8.0.50727.42 to develop. I am scheduling the SQL Server job via Management Studio.




Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer

Have you installed SSIS from the Enterprise Edition CD on your workstation where you are developing the packages





Re: SSIS Higher Level Edition error when run in a Sql Job

jchohio

Yeah, that was installed during our Sql 2000 to Sql 2005 upgrade about two months ago. I personally installed those during this process. I am using RDC to connect to the Server in question, which is where I am developing the packages. Could the version of Visual Studio 2005 have any effect




Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer

jchohio wrote:
Yeah, that was installed during our Sql 2000 to Sql 2005 upgrade about two months ago. I personally installed those during this process. I am using RDC to connect to the Server in question, which is where I am developing the packages. Could the version of Visual Studio 2005 have any effect


And you installed specifically SSIS, right 'Cause Visual Studio will allow SSIS development and execution locally, but not when migrated to the server. That is, when I started development, I only had VS2005 installed. I could build all of my packages and execute them locally, but once I saved the package to the server and then tried to run it, I couldn't do it. To resolve that issue, I had to install SSIS from the Developer edition CD (I develop against that edition, and our DBAs move packages from there to the Enterprise edition production server). Once I installed the "full" client of SSIS from the developer edition CD, I was able to execute packages I had uploaded to the server. Running from Management Studio should work as long as you've got SSIS installed (dtexec.exe, for instance) on the machine that you are running it from.





Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer

Here are my versions locally:

VS2005 - 8.0.50727.42
SSIS - 9.00.2047.00


You can execute this SQL on your SQL server to ensure that you have matched everything up correctly:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')





Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer

Perhaps you need to apply the cumulative hotfix to your machine as well, not just the server Or vice-versa





Re: SSIS Higher Level Edition error when run in a Sql Job

Phil Brammer

Yet more information to explain what I'm typing: (Have you searched for this topic in this forum, by the way )

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=499864&SiteID=1





Re: SSIS Higher Level Edition error when run in a Sql Job

jchohio

SSIS - 9.00.2176.00
VS2005 - 8.0.50727.42

9.00.2176.00 SP1 Enterprise Edition is the output for the SQL 2005 version on the above Select statement. I've matched this to SSIS and they are correct. I don't use my local installs to Develop the SSIS packages, but instead do everything on the server. How our network is partitioned between Development and Production, I find this is much easier.




Re: SSIS Higher Level Edition error when run in a Sql Job

jchohio

I installed SSIS specifically on the server where the SSIS package development is occuring.
I also have a local install on my desktop of VS 2005 and SQL Server. However, when I run jobs or develop anything for SSIS I do it on the server itself. I'll check out reinstalling SSIS from the CD just to be safe. I've verified that SSIS is installed on the machine I am running it from.




Re: SSIS Higher Level Edition error when run in a Sql Job

jchohio

Yep, I've googled and checked the MSDN forums prior to posting. Anything, I've seen elsewhere wasn't satisfactory in finding a solution to this problem. In regards to the post quoted :
  1. SSIS Designer, this gives you SSIS Project inside VS, and lets you design and debug packages. During setup it is subset of the Tools group.
  2. SSIS itself - this gives you the service, and the ability to execute packages outside of the designer. To install, check SSIS checkbox during SQL setup.
I know #1 is definately insalled. However, #2 : I've verified this is installed, but as a sanity check, the existence of DTEXEC.exe confirms that SSIS is installed

This occurs for about 3 jobs that I currently have running. I used logging to diagnose the Higher Level Edition error. What's wierd is that they run fine in Visual Studio 2005 when I execute it, but fail when they are run from a job.





Re: SSIS Higher Level Edition error when run in a Sql Job


Re: SSIS Higher Level Edition error when run in a Sql Job

jchohio

In regards to the blog post, I believe that is the answer to the question. The SSIS service is not installed on our server. Two questions :

1) Do I have to install SSIS SP1 and then patch to the hotfix level (9.0.2176) or if i install the SSIS service to SP1 with that be okay
2) Even though the Sql Server 2005 Integration Service is not installed as a Service on the server, why do I get a Version back when I query for the version value in Management Studio