Calling an SSIS package from IIS

Posted on 2011-03-14
Last Modified: 2012-05-11
I have an intranet.. I am fine most times with the user being prompted to save their file. But I have one daily operation that in the currently run non project it  saved two files then the users saved a report (all to different locations).. With this would leave them to run and have to be prompted and to save 3 files to 3 different areas.. I got this working this way, but over the weekend thought about a possibility that I might be able to use a call to an SSIS package to move these files into the correct locations.

I was following the following tutorial..

Tried both suggestions : Using the package stored on the SQL Server.. Also using the package stored on the C: Drive Both work fine when run in test mode through the localhost.. But when I  put it to IIS, it give me the error seen in the jpg..
protected void btnTest1_Click(object sender, EventArgs e)
            Application app = new Application();
            // Load package from file system
            Package package = app.LoadPackage("C:\\SSISForIIS01\\QuickTest.dtsx", null);

            DTSExecResult result = package.Execute();

       protected void btnTest2_Click(object sender, EventArgs e)

            // Load package from SQL Server
            Package package2 = app.LoadFromSqlServer(
                "QuickTest", "SQL01", "usrID", "mypswd", null);


            DTSExecResult result2 = package2.Execute();

            Console.WriteLine("Package Execution results: {0}",

Open in new window

Question by:moosetracker
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
LVL 23

Expert Comment

by:Saqib Khan
ID: 35131197
> C:\\SSISForIIS01\\QuickTest.dtsx

to me it looks like a permission issue, did you try giving QuickTest Directory full permission for your IIS User?

Author Comment

ID: 35131385
I first took the package (which was created on a program server) and moved the QuickTest.dtsx up to my computer C: drive under a folder.. SSISForIIS01..  It worked.

I then created the same folder in the area that holds the IIS, and plopped the same QuickTest.dtsx into that. Into that..  I have a similar folder in the same area for creating temporary reports, XML, Txt files etc, and the IIS programs have no problem reaching this folder as it is a folder on it's own c drive.

The test to reach the SQL server, The C# has the username & password.. This is the same serve that all the projects are using for access to tables and stored procedure. Only of course this isn't  under the Database Engine area, but under the Integrations Services Area..

Those ClassID {...}  Seemed to be similar to what dogged us, when I created a package and my co-worker wanted to use it.. She Definately could not use my project.. Their was a time we got the error even if I uploaded it to the Server and she downloaded it from the server.. But, for some reason that went away and that is now how we mover between each others code..

Therefore I can see this error because I moved it from my users computer to the IIS computer for the attempt to use the package on the C: drive..  I am unsure about why this problem should occur for the one reading off the server..

Accepted Solution

moosetracker earned 0 total points
ID: 35182784
I figured out an answer myself..  You can set up a job in the SQL Server Job agent..

I do not know if there are other variations but to move the package to the Integrated Sevice area, I used under the "File" toolbar menu  "Save copy of pkgname.dtsx as..."
package location : Sql Server
Server : Name of server
Authentication type :  Sql Server Server Autentication:
Username: _____
password: _____
PackagePath: /QuickTest
ProtectionLevel: Rely on server storage and roles for access controls

Then I created a Job in the SQL Server Agent.. (some of our jobs need the owner to be a proxy, some don't the proxy is needed to move some of the files out to folders outside the server.)
Otherwise in the Job on the SSA under steps..
Type: "SQL Server Integration Services Package"
Package source :  SQL Server
Server : (servename)
Use SQL Server Authentication (username/password)
Browse for your package..

The windows Authentication with hardcoded username/password  is due to IIS does not like integration services..

My SSIS package name is "QuickTest"
My SSA package name is "RunQuickTest"
My stored procedure is "sp_QuickTest"

Now create a Stored procedure to kick off the SQL Server Job Agent..


Alter PROCEDURE sp_QuickTest            
  @SPMessage CHAR (100) OUTPUT,
  @JobName sysname
DECLARE @ReturnCode tinyint -- 0 (success) or 1 (failure)

set @SPMessage = 'Error'

EXEC @ReturnCode=msdb.dbo.sp_start_job @job_name=@JobName;

if @ReturnCode = 0
   set @SPMessage = 'Success'
   set @SPMessage = 'Error'

Return (@ReturnCode);


Now Create the C# Code to run the Stored procedure..

                string errMessage = "";
                string ConnectionString = connectionInfo;
                cnnct = new SqlConnection(ConnectionString);
                cmd = new SqlCommand("sp_QuickTest");
                cmd.CommandType = CommandType.StoredProcedure;

                cmd.CommandTimeout = 0;  // Gives you more time to process.. 0 indicates no limit.

                //if want to read output parm when return, make sure you intialize it in SP!
                //Then set the direction to output.
                //Info Make sure in SP.. you initialize this output field to = '' or it
                // will blow when trying to use.
                cmd.Parameters.Add("@SPMessage", SqlDbType.Char, 100);
                cmd.Parameters["@SPMessage"].Direction = ParameterDirection.Output;
                cmd.Parameters.AddWithValue("@JobName", "RunQuickTest");
                cmd.CommandType = CommandType.StoredProcedure;

                //Process Stored Procedure Query..
                cmd.Connection = cnnct;

                errMessage = (String)cmd.Parameters["@SPMessage"].Value;

                switch (errMessage.Trim())
                    case "Success":
                        lblStatus.Text = "SQL Server Agent job, RunQuickTest, started successfully.";
                        lblError.Text = "SQL Server Agent job, RunSISSPackage, failed to start.";

            catch (Exception exp)
                lblError.Text = exp.Message;
                if (cnnct.State == ConnectionState.Open)


Author Closing Comment

ID: 35221205
I came up with the solution on my own..

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Just a quick little trick I learned recently.  Now that I'm using jQuery with abandon in my applications, I have grown tired of the following syntax:      (CODE) I suppose it just offends my sense of decency to put inline VBScript on a…
It was really hard time for me to get the understanding of Delegates in C#. I went through many websites and articles but I found them very clumsy. After going through those sites, I noted down the points in a easy way so here I am sharing that unde…
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question