SSIS Package runs in BI but not VB.Net

Hot Topic

Partition Processing
Javascript Error When trying url access
How to make a diagram from data in a SQL Server table?
schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportservices
Running query in SQL 2005 stored procedure against table on SQL 2000
Query Analyzer to SQL Server 2005
Can we include User Defined Functions in the Report Model
Native XML vs relation data
Combining two Tables into one TempTable, with a condition.
Basic Mirroring Setup Help

SQL Server

deleting records
Add a DateLoaded column to input data
Doesn't like a particular namespace
multiple prediction targets
2005 SP1 install, another can't authenticate...
How to excute package in sequence
Company Logo in Header of Report Builder
For security reasons DTD is prohibited in this XML document
multiple joins on the same table
Where are the SSI files saved when saved to the server?

SSIS Package runs in BI but not VB.Net

I have a solution with 2 projects: Startup project is VB.net the other is a BI project with an SSIS package.  If I right click on the SSIS package in BI and choose execute the package works flawlessly.  No warnings, no errors, no nothing.  IF I try to execute the same package in VB.net using the following code:

Dim dtsPkg As New Package
Dim dtsApp As New Application
Dim events As IDTSEvents
Dim Res As DTSExecResult

dtsPkg = dtsApp.LoadPackage("C:\package.dtsx", events)
dtsPkg.InteractiveMode = True
dtsPkg.DebugMode = True
dtsPkg.LoggingMode = DTSLoggingMode.Enabled
Dim var1 As Microsoft.SqlServer.Dts.Runtime.Connections = Nothing
Dim var2 As Microsoft.SqlServer.Dts.Runtime.Variables = Nothing
Dim var3 As Microsoft.SqlServer.Dts.Runtime.IDTSLogging = Nothing

Res = dtsPkg.Validate(var1, var2, events, var3)
Res = dtsPkg.Execute()

I get the following error:
The product level is insufficient for component "Data Conversion 1" (101).

This particular package imports a table from an Access db into a SQL2000 DB.  I understand the error message(and that it's probably tied to the fact that I'm trying to use a sql2000 database for a destination), but what I don't get is why it works from Bi but not from the VB.Net code   You would think that it would fail in both



Answer this question

SSIS Package runs in BI but not VB.Net

  • knopper2005

    Yes, this is exactly what I was looking for.  Thanks.  It appears that you did not install SSIS but only management tools, etc.  Is that correct   If so, then this error is expected.  You have to install SSIS in order to be able to run a package outside of the designer (i.e. from VB.NET).

    Thanks,

  • Robert II

    You know what, just to move this project along I removed SQL2000, uninstalled SQL2005 then reinstalled SQL2005 with everything, and it's working. 

    Thanks for your time Matt.
    Steve

  • Phong Nguyen

    Actually this error has nothing to do with having sql2000 as a destination as this is a supported scenario.  This error implies that you have an edition of sql server installed that does not support the data conversion transform.  What SKU of SQL do you have installed and how did you install SSIS   FYI, the reason it works in the designer is because we allow running from the designer so you can debug packages without SKU issues.  However, to run from anything but the designer you need the appropriate SKU for the components/tasks that you are using.

    Thanks,

  • everguess

    I have everything except the actual SQL Server Engine of Microsoft SQL Server 2005 Community Technology Preview (June 2005) Developers Edition installed.  Here is the info from the about box:
    Microsoft SQL Server Management Studio        9.00.1187.00
    Microsoft Analysis Services Client Tools      2000.090.1187.00
    Microsoft Data Access Components (MDAC)       2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
    Microsoft MSXML                               2.6 3.0 4.0 5.0 6.0
    Microsoft Internet Explorer                   6.0.2900.2180
    Microsoft .NET Framework                      2.0.50215.312
    Operating System                              5.1.2600

    SQL2000 is also the Developers Edition Version 8.0.2039

    I hope that what you were looking for when you refered to SKU

    >>need the appropriate SKU for the components/tasks that you are using.
    What would be the appropriate SKU's to get this scenario working

    Thanks Steve
  • SSIS Package runs in BI but not VB.Net
Answer this question