Monday, March 18, 2013 10:55 PM
Long time reader- first time poster - and I'm stuck! :(
I have a .Net 4.5 framework application built in VS 2012 that runs SSIS packages on SQL Server 2008 R2 enterprise. It is a console based app and is designed to be run locally on the SSIS server.
I am using Microsoft.SQLServer.ManagedDTS version 10.50.1600.1 and have confirmed that this is the version being referenced by my project on my dev machine and is the same installed in the GAC on the SSIS server.
The tool successfully starts and runs a number of different packages, however it fails when it hits a package that has the Partition Processing destination component and gives the error:
Component "component "Partition Processing1" (49)" could not be created and returned error code 0xC1000002. Make sure that the component is registered correctly.
Data Flow Task
The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
Now here is the kicker - if I run the same package using dtsexec on the same machine (integration services) it works!
My feeling is this has *something* to do with this component being an enterprise edition component and the referenced assembly of Microsoft.SQLserver.Dts.Runtime not being the correct version.
Any ideas would be greatly appreciated
Tuesday, March 19, 2013 3:52 AM
it's seems to me that your partition processing componet is not registerd correctly. so please run this command to register the partition processing componet:
Regsvr32 "c:\Program Files (x86)\Microsoft SQL Server\100\dts\PipelineComponents\msmdpp.dll"
if this path is wrong please try to find the msmdpp.dll and register it.
I hope this helps you.
Tuesday, March 19, 2013 7:39 AM
unfortunately this didn't resolve the issue and I'm getting the same error.
Something interesting to note is in the assembly the version listed for Microsoft.SQLServer.ManagedDTS is 10.0.0.0 but when I right click->properties and go to the file version it says 10.50.1600.1 - could this have something to do with it?
I'm also wondering if this could be a 'mixed assembly' type issue and there are problems with .Net 4.5?