Execute package via a web application failing
I have created a web interface for an ETL. The SSIS packages run via the GUI package utility and the command line; however, they fail miserably via the web application. The web app discovers the package without a problem, as I can view various properties of the package within the web app. However, when I call execute and step through the code a DtsError is returned referencing "System.__ComObject". Any ideas?string
pkgLocation;
Package pkg =newPackage();
Microsoft.SqlServer.Dts.Runtime.Application app =new Microsoft.SqlServer.Dts.Runtime.Application();
DTSExecResult pkgResults;
IDTSEvents dtsEvents =null;
pkgLocation = strPackagePath.ToString() + strPackage;
pkg = app.LoadPackage(pkgLocation, dtsEvents,
true);// set package variables
Variables vars = pkg.Variables;// set ImportFolderPath
pkg.VariableDispenser.LockOneForWrite("ImportFolderPath",ref vars);
vars["ImportFolderPath"].Value = @"c:\etlpackages\mySample.dtsx";
vars.Unlock();// execute package
pkgResults = pkg.Execute();
[2317 byte] By [
CBenoit] at [2007-12-17]
The most important difference when you run the
package under IIS is user identity - the package
is run under identity of user used to run the ASP.NET,
so make sure this user has access to all the external
data sources and files.
To get more information about the error and see
why the package is failing, configure SSIS logging
for this package and inspect the logs.
Thanks for the info. The logging feature helped me narrow it down. Although I still don't understand this error:
The product level is insufficient for component "SFFL Answers"
The error indicates the SSIS product level (standard/developer/workstation/etc) is not high enough for this component (by the way what component type is "SFFL Answers"?). The product level is ignored when run from designer, but is checked when run using DTEXEC or using object model. Please check if the package runs OK in DTEXEC.
To fix this, you need to install the SSIS (not just Workstation Components) on this machine.
I attempted to r un it with DTEXEC and got the same error in the log file. SFFL Answers is a Flat File Source component.
I am running these locally on my machine. What is the difference between SSIS and the Workstation Components? Does this ship differently from SQL2005? I'm confused.
SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.
Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.
That did it! Thank you so much for your help.
Clay
I tried this solution and was not able to see the SSIS option in the install. We have the SQL Server 2005 Standard edition. Is the SSIS available for the Standard or only for Enterprise or am I just missing something here?
Thanks for any assistance. ;)
Hello everybody.
We have same problem, but we don't understand in your solution how to install SSIS.
In a workstation, Sql Setup doesn't let you to check other option than Workstation components.
Bye, Juan
 Aaeryn wrote: |
| I tried this solution and was not able to see the SSIS option in the install. We have the SQL Server 2005 Standard edition. Is the SSIS available for the Standard or only for Enterprise or am I just missing something here? Thanks for any assistance. ;) |
|
Standard Edition does include SSIS. You have two disks - Servers and Tools, SSIS can be installed from Servers disk.
| JuanSa wrote: |
| Hello everybody. We have same problem, but we don't understand in your solution how to install SSIS. In a workstation, Sql Setup doesn't let you to check other option than Workstation components. Bye, Juan |
|
Are you trying to install Enterprise Edition on Windows XP? Enterprise Edition requires Server OS (Windows 2000 or 2003 Server) - either switch to server OS, or use Standard or Developer Edition on XP.
Hi all,
I have the same probleme. I use sql2005 (SQL Server 9.00.2047.00 - SP1 (Enterprise Edition)).
When i execute the package on the server and in the develloppement tools, the package is working.
When I execute the package on my computer (Windows XP), the package is not working (I try to execute it in "sq server management studio" and in "Execute package utility"), the package don't working.
In my computer i install sql server 2005.
You say, that I must install standard or developer edition of sql server on my computer. Is they have an other solution?
I don't understand, if I create a C# application to execute ssis package, All the computer must have integration services on the computer?
Thank.
PS : I'm french person, my english is not very good.
As Michael Entin stated above, SQL 2005 Enterprise Edition is only supported in a server OS environment (which is why your package fails to execute on your Windows XP OS). Perhaps a duel-boot install of Windows Server 2003 could solve your problem. Otherwise, just install the Standard or Developer version of SQL 2005.
If you don't have access to the Standard or Developer versions, another option is to use a virtual machine emulating Windows Server 2003 - although not ideal, I have successfully attempted this with satisfactory results. Hope that helps...
Cheers,
-joviyan I have the same issue with a deployment package. I want to be able to programmatically determine if Integration Services is installed before I even attempt to install my package. Can you point me to any resources that would help me to do this?
it appears that all of the utilities (DT*) are there, so that does not appear to help.
also, is there a best practice for installation to the file system vs installation to SQL Server. I like installing to SQL Server, but the drawback is I can't open the package once it is there. I have to open a copy, then reinstall to incorporate any changes.
Thanks for any advice and direction.
Tom Gibson
