Product level is insufficient error

Configuration: Windows XP Pro with SQL 2005 Workgroup Sp2

Hi, we have a package that runs fine in BI Studio but fails with the following error when executing it using DTExec.

Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Derived Column" (10660).

The package imports a CSV into a table mapping some columns. The MSDN article at http://msdn2.microsoft.com/en-us/library/ms143761.aspx describes features supported by different versions.

The article says OLE DB source/destination adapters are supported in WG edition but a couple of lines later seems to imply that all source/destination adapters are not supported in WG.

Could you clarify whether stuff like import of a csv into a table with some column mappings should work in WG edition? Also if we have a legacy SQL 2K package doing the same thing, will that work in WG edition? Thx.

Features/Integration Services Enhancements EE (32-bit) DE (32-bit) EE (64-bit) DE (64-bit) SE (32-bit) WG (32-bit) SSE (32-bit) SSEA (32-bit) SE (64-bit)

SQL Server Import and Export Wizard and supporting connections, source and destination adapters, and tasks

Yes

Yes

Yes

No

Yes

Execute SQL Task

Yes

Yes

Yes

No

Yes

OLE DB Source and Destination Adapters

Yes

Yes

Yes

No

Yes

SSIS command prompt tools

Yes

Yes

Yes

No

Yes

SSIS Package Designer

Yes

Yes

Yes

No

Yes

Legacy support for DTS packages

Yes

Yes

Yes

Yes

Yes

SSIS Service

Yes

Yes

No

No

Yes

All other source and destination adapters, tasks, and transformations, except for those listed below

Yes

Yes

No

No

Yes

You might want to be sure that you have actually installed the full SSIS client.|||

As Phil wrote, most likely you've only Workstation components installed and need to install full SSIS.

See Books Online and my blog for details:

http://msdn2.microsoft.com/en-US/library/aa337371.aspx

http://blogs.msdn.com/michen/archive/2006/11/11/ssis-product-level-is-insufficient.aspx

process add and configuration

SSIS Destination Adapter ProcessADD does not correctly use the Analysis Services Connection with and dynamic connection string.

I use process add for cube Processing - we use Production and Development environment. The analysis Services Connection is parameterized with a differnt Database name.

The Process add - does not like all other analysis services processing tasks, allow you to use an expression for the processing command - it only gives you the UI with design time tools.

But I guess like all other SSIS Components with SSAS the Database Name is hardcoded in the prcessing command. For the Processing Task I could change this with an expression.

But Howto change the Processing Command withing the Process ADD Destination -

or how do I get it working while the database name changes (at the moment if the database name changes by configuration all mappings are lost and execution fails)

Best Regards

HANNES

I am doing something wrong? or is a configuration for data datasource of the olap destination is ssis not supported?

Best regards, HANNES

|||

I got it

The Database is always part of the XMLA command and therefore not affected by the connection manager initial catalog property.

You always have to code the database name in the XML Command

HANNES

process add and configuration

SSIS Destination Adapter ProcessADD does not correctly use the Analysis Services Connection with and dynamic connection string.

I use process add for cube Processing - we use Production and Development environment. The analysis Services Connection is parameterized with a differnt Database name.

The Process add - does not like all other analysis services processing tasks, allow you to use an expression for the processing command - it only gives you the UI with design time tools.

But I guess like all other SSIS Components with SSAS the Database Name is hardcoded in the prcessing command. For the Processing Task I could change this with an expression.

But Howto change the Processing Command withing the Process ADD Destination -

or how do I get it working while the database name changes (at the moment if the database name changes by configuration all mappings are lost and execution fails)

Best Regards

HANNES

I am doing something wrong? or is a configuration for data datasource of the olap destination is ssis not supported?

Best regards, HANNES

|||

I got it

The Database is always part of the XMLA command and therefore not affected by the connection manager initial catalog property.

You always have to code the database name in the XML Command

HANNES