Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Konesans Checksum 2008 issue Expand / Collapse
Author
Message
Posted Tuesday, April 20, 2010 5:18 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 12:50 PM
Points: 14, Visits: 347
Hi,

I installed Konesans checksum 2008 component on SQL Server 2005 box. It installed successfully but I am not seeing the component in 2005 BIDS toolbox and when I am trying to add it in I am getting error "Could not load file or assembly 'Microsoft.SqlServer.PipelineHost, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of it's dependencies. The system cannot find the file specified.'

Can anyone help me out in fixing the issue.

Thank you

Srini
Post #907330
Posted Wednesday, April 21, 2010 10:28 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 6:30 AM
Points: 1,114, Visits: 2,193
srinivasable (4/20/2010)
Hi,

I installed Konesans checksum 2008 component on SQL Server 2005 box. It installed successfully but I am not seeing the component in 2005 BIDS toolbox and when I am trying to add it in I am getting error "Could not load file or assembly 'Microsoft.SqlServer.PipelineHost, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of it's dependencies. The system cannot find the file specified.'

Can anyone help me out in fixing the issue.

Thank you

Srini



You have to install the version for SQL 2005.


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #907910
Posted Wednesday, April 21, 2010 11:11 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 12:50 PM
Points: 14, Visits: 347
Thanks for the reply,

I want to use Konesans checksum 2008 component in 2005 SSIS packages.

Please let me know to how to add it BIDS tool box.

Thanks in Advance.

Thank you
Srini

Post #907956
Posted Wednesday, April 21, 2010 12:06 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 6:30 AM
Points: 1,114, Visits: 2,193
srinivasable (4/21/2010)
Thanks for the reply,

I want to use Konesans checksum 2008 component in 2005 SSIS packages.

Please let me know to how to add it BIDS tool box.

Thanks in Advance.

Thank you
Srini



Srini,

The 2008 component is for 2008 SSIS packages. Why do you expect you can use 2008 version in 2005 packages?


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #908002
Posted Wednesday, April 21, 2010 3:04 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 12:50 PM
Points: 14, Visits: 347
Hi,

We have 2 clients. one client is using SQL2008 and the other client is using SQL2005.

I want use 1 set of packages (2005 SSIS packages with Konesans 2008 component).

Thank you
Srini
Post #908138
Posted Wednesday, April 21, 2010 3:14 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 6:30 AM
Points: 1,114, Visits: 2,193
srinivasable (4/21/2010)
Hi,

We have 2 clients. one client is using SQL2008 and the other client is using SQL2005.

I want use 1 set of packages (2005 SSIS packages with Konesans 2008 component).

Thank you
Srini


Srini,

There is no way you can use one and same package for both 2005 and 2008. What you can do is implement your package in 2005 and then whenever you have to make changes, make them in the 2005 version. Then use 'Add Existing Package..." command in 2008 solution and the SSIS framework will hopefully upgrade the package without issues to 2008. However for this to work your machine has to have both:

- SQL 2005 and 2008 installed
- Konesans component for 2005 an 2008 installed


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #908146
Posted Wednesday, April 21, 2010 3:36 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 12:50 PM
Points: 14, Visits: 347
I did that way too but when I am upgrading the packages are failing because of Konesans. by default konesans are not upgrading to 2008 konesans.

Thank you
Srini
Post #908163
Posted Wednesday, April 21, 2010 3:45 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 6:30 AM
Points: 1,114, Visits: 2,193
srinivasable (4/21/2010)
I did that way too but when I am upgrading the packages are failing because of Konesans. by default konesans are not upgrading to 2008 konesans.

Thank you
Srini


Srini,

You have to contact Konesans people and ask them to include the so-called upgrade manifest. It is very simple document, used by the SSIS framework to map the old component version to the new. You may also try to define the manifest by yourself. For example the Trash Destination manifest looks like this:

<?xml version="1.0" ?>
<Mappings xmlns="http://www.microsoft.com/SqlServer/Dts/UpgradeMapping.xsd">

<!--
Konesans SQL Server Integration Services Upgrade Mappings
Copyright © 2008 Konesans Limited

%ProgramFiles%\Microsoft SQL Server\100\DTS\UpgradeMappings\

Upgrade mapping for SQL Server 2005 to SQL Server 2008.
-->

<ExtensionMapping
tag="Konesans Trash Destination"
oldAssemblyStrongName="Konesans.Dts.Pipeline.TrashDestination.Trash, Konesans.Dts.Pipeline.TrashDestination, Version=1.0.1.0, Culture=neutral, PublicKeyToken=b8351fe7752642cc"
newAssemblyStrongName="Konesans.Dts.Pipeline.TrashDestination.Trash, Konesans.Dts.Pipeline.TrashDestination, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b2ab4a111192992b"
/>
</Mappings>

The manifest has to be deployed in this folder:

\Microsoft SQL Server\100\DTS\UpgradeMappings

and the file must have .xml extension.


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #908170
Posted Wednesday, April 21, 2010 5:29 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, March 11, 2014 12:50 PM
Points: 14, Visits: 347
Thanks for the detailed answer.

We have a package which will save all my packages in msdb databases.

Please let me know if run the packages it's going to upgrade and save it in sql 2008 with konesans 2008 right?

Thank you
Srini
Post #908228
Posted Wednesday, April 21, 2010 6:52 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 6:30 AM
Points: 1,114, Visits: 2,193
srinivasable (4/21/2010)
Thanks for the detailed answer.

We have a package which will save all my packages in msdb databases.

Please let me know if run the packages it's going to upgrade and save it in sql 2008 with konesans 2008 right?

Thank you
Srini


Srini,

I'm not sure. You have to try.


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #908253
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse