Last post Aug 24, 2017 04:52 PM by melkon
Sep 26, 2007 06:01 AM|Brammieman|LINK
I want to run a SSIS package, that reads from a flatfile and writes to a SQL2005 DB table, from a webpage created in VS2005.
Basically I keep running into the same error, no matter what settings I use in IIS or the web.config (impersonation on or off) for the specific webpage.
The package loads, get's some variables passed and executes. No DTS errors are triggered. I added an eventlistener to pick up events of the package itself.
"Microsoft.SqlServer.Dts.Runtime.PackageConnection manager "*******"SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user ''. The user is not associated with a trusted SQL Server connection.".
The webpage uses forms authentication and impersonates properly when told to do so in the web.config. (checked)
Somehow no security credentials seem to get passed to or through the ssis package when it's ran.
I've seen many posts on the subject but can't really find a solution to run an SSIS package from a webpage.
Is there any way of running an ssis package from a webpage hosted on a webserver running IIS (5.1)?
At the moment I'm not limited to any setup. I just want to have it working.
Code to load and execute the package:
pkgLocation = _
pkgResults = pkg.Execute(
The Eventlistener that captures the failure of the logon attempt of the connection manager inside the package:
Sep 27, 2007 05:35 AM|Brammieman|LINK
Issue resolved by adding an application pool in IIS, setting up it's Identity (tab) to Configurable, adding an account that has sufficient privileges to run dtexec properly. (ASP worker process is ran by this account if I'm correct, which in turn starts
The account used should also be part of the system's IIS_WPG group to be able to start the asp worker process.)
Found the solution eventually in a post here after some trying etc.
Aug 24, 2017 04:52 PM|melkon|LINK
Thank you Brammieman, it solved my issue.