SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


can not run SSIS package with script task when deployed to SQL Server under MSDB


can not run SSIS package with script task when deployed to SQL Server under MSDB

Author
Message
ForumUser3
ForumUser3
Old Hand
Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)

Group: General Forum Members
Points: 335 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 UserCool
ForumUser3
ForumUser3
Old Hand
Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)

Group: General Forum Members
Points: 335 Visits: 113
minor correction on the post.
The package has been created using Visual studio 2010 NOT Visual Studio 2012

Forum UserCool
twin.devil
twin.devil
SSCertifiable
SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)

Group: General Forum Members
Points: 5570 Visits: 2692
do check if SSIS components installed on Host.
ForumUser3
ForumUser3
Old Hand
Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)

Group: General Forum Members
Points: 335 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 UserCool
John Mitchell-245523
John Mitchell-245523
SSC-Dedicated
SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)

Group: General Forum Members
Points: 35938 Visits: 16699
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
ForumUser3
ForumUser3
Old Hand
Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)Old Hand (335 reputation)

Group: General Forum Members
Points: 335 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 UserCool
John Mitchell-245523
John Mitchell-245523
SSC-Dedicated
SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)

Group: General Forum Members
Points: 35938 Visits: 16699
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
twin.devil
twin.devil
SSCertifiable
SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)SSCertifiable (5.6K reputation)

Group: General Forum Members
Points: 5570 Visits: 2692
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.
dileepvarma80
dileepvarma80
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 18
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search