CJayM


Hi.

I have an SSIS package which is used to import various different files.

When I run the package directly through the Visual Studio, it works fine, with no problems.

However, when I call the package through within a Visual Basic application, it returns "success" but when I check the database, nothing has been imported!!

The VB code I use to execute the package is:

pkgLocation = ConfigurationManager.AppSettings.Item("ImportSenseSSIS").ToString.ToUpper.Trim

pkg = app.LoadPackage(pkgLocation, Nothing)

pkg.Variables("bError").Value = False

pkg.Variables("SenseFileName").Value = strFile ' e.g. ksf_booking_20070608.1.csv

pkg.Variables("SenseImportPath").Value = path ' e,g, \\SandPiper\Data\Sense Downloads\

pkgResults = pkg.Execute()

The App Setting "ImportSenseSSIS" is set to:

<add key="ImportSenseSSIS" value="C:\devt\Travelodge Pegasus Import\SenseImport\ImportSense.dtsx"/>

(which does exist)

I have another package which runs perfectly in both the Visual Studio IDE, and the VB application.

I hope someone can help!!





Re: SSIS Execution problems

jwelch


Are you sure that the flat file path you are creating is correct





Re: SSIS Execution problems

CJayM

Hi.

Yes, the file path is correct.







Re: SSIS Execution problems

Phil Brammer

Try adding the following line after your pkgResults line:

pkg.Dispose()





Re: SSIS Execution problems

CJayM

Hi.

I do already have that line after the pkgResults line.

Christian






Re: SSIS Execution problems

Bob Bojanic - MSFT

Could you turn on logging and try to see if you can get any information about what is happening in the runtime

Thanks,

Bob






Re: SSIS Execution problems

CJayM

Here is the last part of the log

UserBig Smileiagnostic,WR203257,WILLIAM-REED\christian.mead,SANDPIPER.TravelodgeImport,{489E5C92-F1A5-41F0-A62E-DFD6A06F58ED},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:26:59,06/07/2007 10:26:59,0,0x,ExternalRequest_post: 'ITransactionJoin::JoinTransaction succeeded'. The external request has completed.
OnPostExecute,WR203257,WILLIAM-REED\christian.mead,Check Import Status,{66DA2847-9B4A-4DED-B305-B9F069B07875},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:26:59,06/07/2007 10:26:59,0,0x,(null)
OnPreExecute,WR203257,WILLIAM-REED\christian.mead,Configure Package,{15FC4A77-36B6-42AA-AB14-5A23DC781D5F},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:26:59,06/07/2007 10:26:59,0,0x,(null)
OnPreValidate,WR203257,WILLIAM-REED\christian.mead,Configure Package,{15FC4A77-36B6-42AA-AB14-5A23DC781D5F},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:26:59,06/07/2007 10:26:59,0,0x,(null)
OnPostValidate,WR203257,WILLIAM-REED\christian.mead,Configure Package,{15FC4A77-36B6-42AA-AB14-5A23DC781D5F},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:26:59,06/07/2007 10:26:59,0,0x,(null)
OnPostExecute,WR203257,WILLIAM-REED\christian.mead,Configure Package,{15FC4A77-36B6-42AA-AB14-5A23DC781D5F},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:27:01,06/07/2007 10:27:01,0,0x,(null)
OnPreExecute,WR203257,WILLIAM-REED\christian.mead,Import Booking Feed,{52A9CD59-BA32-4557-8090-3BDAAFA67833},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:27:01,06/07/2007 10:27:01,0,0x,(null)
OnPostExecute,WR203257,WILLIAM-REED\christian.mead,Import Booking Feed,{52A9CD59-BA32-4557-8090-3BDAAFA67833},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:27:01,06/07/2007 10:27:01,0,0x,(null)
OnPostExecute,WR203257,WILLIAM-REED\christian.mead,ImportSense,{5DEA2CC3-98F1-4211-9969-72049DD28BBA},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:27:01,06/07/2007 10:27:01,0,0x,(null)
PackageEnd,WR203257,WILLIAM-REED\christian.mead,ImportSense,{5DEA2CC3-98F1-4211-9969-72049DD28BBA},{003179F4-09E7-4E72-885A-1DDCCD3B7A25},06/07/2007 10:27:01,06/07/2007 10:27:01,0,0x,End of package execution.






Re: SSIS Execution problems

Bob Bojanic - MSFT

This logging information does not tell us much...

Could you provide some additional information about your package Is it just a single data flow, what components it contains

Also, could you try to run this package using dtexec on the same machine you were able to run it in the designer

Thanks,

Bob