June 5, 2014 at 9:32 am
Migrating from SQL 2008 to SQL 2012 on Win 2012. 20+ packages run as scheduled jobs. So far, packages that use script task won't execute. Run locally fine. Push to dev server - receive "To run a SSIS package outside of SQL Server Data Tools you must install <task name> of Integration Services or higher". Uninstalled SQL 2012 and reinstalled, rebooted, installed SQL Data Tools, Complete Management Tools, and Client Tools SDK, rebooted. Execute using Package Execution Utility. Execute as SysAdmin - still the same error message.
What'd I do wrong? Thanks in advance for your help.
.
June 5, 2014 at 9:39 am
Is Integration Services installed on the server?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
June 5, 2014 at 10:21 am
Yes - Integration Services, Data Tools, complete Management Tools, and the Client Tools SDK also. I have at least a dozen other packages that are running on the server. The only ones that have a problem (it seems) are the ones using the Script Task.
June 5, 2014 at 10:33 am
PurpleLady (6/5/2014)
Yes - Integration Services, Data Tools, complete Management Tools, and the Client Tools SDK also. I have at least a dozen other packages that are running on the server. The only ones that have a problem (it seems) are the ones using the Script Task.
This is one of those 'I think I've seen this before. Can I remember the solution? Not a chance!' problems.
As you have everything installed on the server, can you try developing a simple package on the server with a 'Hello world' (or whatever) Script Task and then running it? This rules out any chance that the problem is somehow related to package migration.
The next thing I would look at is whether there is any other software installed on the server that may be causing some sort of conflict. SQL Server Express, perhaps.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
June 5, 2014 at 10:35 am
Will do - thanks.
June 5, 2014 at 1:04 pm
Logged onto dev server, created new package with script task - very simple "Hello World", runs in Debug. Will not run using Execute Package Utility. Changed package type from DTSDesigner100 to DTSDesigner with the same results. Running Execute Package Utility v11.0.2100.60 (64-bit).
March 27, 2015 at 11:39 am
I am seeing the exact same issue. I can run the package with the script component in debug mode. When I use the Execute Package Utility I get the "Error: To run a SSIS package outside of SQL Server Data Tools you must install <Name of Script Task that fails> of Integration Services or higher."
Packages without the script component work fine. I also have checked to make sure all the SQL Tools were installed and I am able to run packages without script components.
Thank you for any help you can provide.
Sam
November 14, 2016 at 3:52 am
A bit late perhaps. I had this issues trying to run a child package (Execute package task). I switched ExecuteOutOfprocess to false.
In sql 2012 there is the difference between Project Reference and External reference in Execute package task. If a package has child packages than in the execute package task editor at the package form, you can change executeOutofProcess to false.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply