Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

can not run SSIS package with script task when deployed to SQL Server under MSDB Expand / Collapse
Author
Message
Posted Tuesday, October 29, 2013 6:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, July 4, 2014 12:04 PM
Points: 33, Visits: 113
I created an SSIS package using visual studio 2012 and tested on my local machine. It worked as expected.

Then I deployed this package on Integration services under MSDB. When I execute the package under MSDB it gives me error on the script task. It works fine if I remove the script task, it has two sql tasks that run fine using oledb connection.

Error: To run SSIS package outside of data tool you must install <script task name> of Integration services or higher.

What am I missing?

Thank you for your help.


Forum User
Post #1509333
Posted Tuesday, October 29, 2013 7:18 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, July 4, 2014 12:04 PM
Points: 33, Visits: 113
minor correction on the post.
The package has been created using Visual studio 2010 NOT Visual Studio 2012


Forum User
Post #1509340
Posted Tuesday, October 29, 2013 7:31 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 5:03 AM
Points: 701, Visits: 1,260
do check if SSIS components installed on Host.
Post #1509347
Posted Tuesday, October 29, 2013 7:43 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, July 4, 2014 12:04 PM
Points: 33, Visits: 113
twin.devil (10/29/2013)
do check if SSIS components installed on Host.


How do I check it?

One more thing I just found out is that, If I remote into the machine where Sql Server is installed and open SSMS on the remote machine. I execute the same SSIS package by right click ->Run package, and it runs without error .

What am I missing? What do need to do so the script task runs from remote machine.


Forum User
Post #1509354
Posted Tuesday, October 29, 2013 9:26 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:06 AM
Points: 5,318, Visits: 9,761
Please go on to the server with the msdb database on it and check whether there's a service called SQL Server Integration Services xx.x (where xx.x is the version), and that the service is running. If there is and it is, please post the contents of your MsDtsSrvr.ini.xml file. On my computer it's in \Program Files\Microsoft SQL Server\100\DTS\Binn.

John
Post #1509421
Posted Tuesday, October 29, 2013 10:33 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, July 4, 2014 12:04 PM
Points: 33, Visits: 113
Here are the contents of MsDtsSrvr.ini
I found it under E:\Program Files\Microsoft SQL Server\110\DTS\Binn
<?xml version="1.0" encoding="utf-8"?>
<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>.</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>

I also saw this in the services window:
SQL Server Integration Services 11.0 started automatic
Microsoft .NET Framework NGEN v2.0.50727_X64 Disabled
Microsoft .NET Framework NGEN v2.0.50727_X86 Disabled
Microsoft .NET Framework NGEN v4.0.30319_X64 Delayed start with no status
Microsoft .NET Framework NGEN v4.0.30319_X86 Delayed start with no status

Would .net service have anything to do with this error.
I can run the package without error if I remove the script task.
I am using C# in the script task to assign value to a variable.

Thanks for your help.


Forum User
Post #1509461
Posted Tuesday, October 29, 2013 10:37 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:06 AM
Points: 5,318, Visits: 9,761
It could well be something to do with the .Net Framwework service, since it's only the script task that appears to be causing you problems. However, I'm afraid we've strayed beyond my area of expertise now!

John
Post #1509463
Posted Tuesday, October 29, 2013 11:39 PM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 5:03 AM
Points: 701, Visits: 1,260
let me put it this way:

Scenario:

Host 1 - SQL Server 2012 DB Engine and Agent.
Host 2 - SSIS 2012

Package would execute successfully if executed from Host 2. If executed from Host 1 (where the Agent resides, with the ultimate intention of running as a job), it produces the error

To fix, SSIS 2012 components had to be installed on Host 1.
Post #1509655
Posted Thursday, January 30, 2014 12:45 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, March 19, 2014 1:41 PM
Points: 1, Visits: 16
Hi,

I am getting the following Error.

Error: To run a SSIS package outside of SQL Server Data Tools you must install Sort of Integration Services or higher.

I Created package1 with Execute Package Task and Another Package2 with Data flow Task and Sort Task in it.
The Execute Package task calls Packge2.
I ran into above error. If I execute Package2, then its works fine. But when i execute package1 it gives above error.

Solution: In Execute Package Task, in package window, ExecuteOutOfProcess should be false. if i make it true then i get the error.

Not Sure if this is going to help, but just wanted to share if it helps.

Thanks
Post #1536516
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse