July 25, 2012 at 7:15 am
Hi all
I've come across a problem while trying to execute an SSIS package. It runs fine when I execute it manually in BIDS on my PC, but I'm getting the "DTS_E_PRODUCTLEVELTOOLOW error when I try executing it from the MSDB package store.
Having read pevious threads I believe that this is something to do with the versions of the SSIS designer I'm using on my machine, and the version of SQL server running on the server. I've checked the server (using SELECT @@VERSION) and got:
Microsoft SQL Server 2005 - 9.00.5057.00 (Intel X86) Mar 25 2011 13:50:04 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
I then checked in the "About" box of Visual Studio 2005 on my PC and I have the following:
Microsoft Visual Studio 2005 Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework Version 2.0.50727 SP2
Microsoft SQL Server Integration Services Designer Version 9.00.4035.00
I developed the package on my PC and then deployed it to the server, where I'm trying to run it.
I don't understand enough about how the package is executed to know what's going on. Surely if the server version is higher than my local client copy off SSIS then it should run OK? I could understand it the other way round....
Would someone be able to explain to me what actually happens when I try to run a stored package, and if the solution is really just to upgrade my SSIS Designer to the same version as the server, then re-build the package?
Many thanks
Jules
July 25, 2012 at 8:00 am
Is the SSIS service installed on the server?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 25, 2012 at 8:14 am
Yes it is - if I check services I can see SQL Server Integration Services, and it's started, and running under NTAUTHORITY\Network Service (Windows Server 2003 R2 SP2)
July 25, 2012 at 8:17 am
What edition of SQL is on the server?
You've got developer on the desktop, is the server running Enterprise or standard?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 25, 2012 at 8:24 am
As mentioned in my first post, it looks like we're running a developer copy (this is a dev server, not production):
Microsoft SQL Server 2005 - 9.00.5057.00 (Intel X86) Mar 25 2011 13:50:04 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
July 25, 2012 at 10:17 am
Not sure then, the two reasons I know of are SSIS not installed on the server that's running the jobs or running standard edition and using enterprise features.
Can you google this? I recall there's lots and lots of forum threads (I had this error some time back), you may well find the solution in one of those.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 26, 2012 at 8:20 am
I have found the solution to the issue. I had previously done a Google search for this but didn't come up with any solutions. However, I've just run another search, and found this article:
In summary, when you connect to an SSIS instance on a server from your Management Studio client on your desktop, when you attempt to execute the package it actually runs locally on your desktop, not the server. So in order to get that to work you would need to install SSIS on your client, in addition to BIDS. I've just done that and the error has gone away. result!
Alternatively as the article suggests, set up an SQL Agent job to run the package; this ensures it runs on the server.
Hope this helps anyone else stuck in the same position.
Jules
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply