Reputation: 3070
My web app pass a parameter to the SSIS package and executes it. Everything runs smooth on the development machine. But when i deploy the app to production server, the execution fails.
Error is "Failed to connect to server ."
It fails at the second line
var ssisCon = new SqlConnection(connectString);
var integrationSvc = new IntegrationServices(ssisCon);
Here is my connection string:
<connectionStrings>
<add name="SSISHOST" connectionString="Data Source=TESTSERVER\SQL2012;Initial Catalog=master;Integrated Security=SSPI;" />
</connectionStrings>
Application on IIS runs under application pool using my credentials, so it can't be a permission issue, so if everything runs fine on my machine, how does it get broken after publishing.
I can't seem to figure out what is breaking the app, Is it the connection string? I can provide more information if someone needs.
Upvotes: 1
Views: 2123
Reputation: 3070
So the answer is: it is not possible, yet.
You cannot run packages outside SQL Server Data Tools on a client computer that does not have Integration Services installed, and the terms of your SQL Server licensing might not let you install Integration Services on additional computers. Integration Services is a server component and is not redistributable to client computers.
My machine has Integration Services Installed but the production server doesn't have them. Hence i am able to run the app successfully on my machine. So crux is Integration Services and IIS needs to be on the same machine or both servers needs to have both the services.
Very Helpful: http://technet.microsoft.com/en-us/library/ms403355.aspx
Upvotes: 2