| Author |
Topic |
|
Peter99
Constraint Violating Yak Guru
498 Posts |
 Posted - 2012-10-15 : 13:57:51
|
| Hi,I recently migrated SQL Server from cluster to VM with same version and edition. (SQL Sever 2008 Enterprise Edition 64 bits).I moved databases and SSIS packges from cluster instance to vm. I moved packages by opening ssis package in BIDS from old server and saved on new server by save as copy. Then I changed connection string for new server. These packages are stored in msdb. These packages basically run through job every night and call other packges that are on application sever.All other packages run fine except one. When we run this package inside BIDS it runs fine but when it runs through schedule job it gives error. Here is the error:"Code: 0xC0047062 Source: xxxx Import xxxxx Import (xxxxx xxxxx [65]) Description: Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException: The version of component "xxxx xxxxx" (65) is not compatible with this version of the DataFlow. [[The version or pipeline version or both for the specified component is higher than the current version. This package was probably created on a new version of DTS or the component than is installed on the current PC.]] at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostCheckAndPerformUpgrade(IDTSManagedComponentWrapper100 wrapper, Int32 lPipelineVersion)"This package was running fine on old database server (cluster instance).Any help how to resove this issue?Thanks |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-10-15 : 22:21:41
|
| it seems like the ssis version in new machine is different from that in old or package was created in later version. So you wont be able to get this package executed in lower version. To understand more check versions of SQL Server SSIS in both machines------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
Peter99
Constraint Violating Yak Guru
498 Posts |
Posted - 2012-10-16 : 14:59:01
|
| Thanks for reply. Right now old server is not available. But I remember I installed same versiion/edition for sql server and installed ssis from same cd. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-10-16 : 23:45:37
|
quote:
Originally posted by Peter99
Thanks for reply. Right now old server is not available. But I remember I installed same versiion/edition for sql server and installed ssis from same cd.
whats the type of the component its complaining about? is it some kind of custom component or is it standard component in SSIS?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
Peter99
Constraint Violating Yak Guru
498 Posts |
Posted - 2012-10-17 : 10:38:40
|
| When I run this package through BIDS it run successfully. Problem is only through job. This is the main package that calls other packages. I don't know about the component types. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-10-17 : 23:23:31
|
quote:
Originally posted by Peter99
When I run this package through BIDS it run successfully. Problem is only through job. This is the main package that calls other packages. I don't know about the component types.
sorry without understanding that we might not be able to suggest anything further------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
nicklarge
Starting Member
40 Posts |
Posted - 2012-10-23 : 17:06:02
|
| Peter99,Have you looked at the error in the Job history? What is the error message that it is returning? There may be a consideration that there is a connection or number of connections where the value is an expression, and that the value relys on a sql entry in a table that hosts SSIS configurations which the new machine may not have access to through some firewall hole that doesnt exist which should. I am just throwing that out there as a stone in a pond as that is a common issue with moving SSIS packages to new machines. Also, maybe there is some documentation inside your company written by the developer which might contain some information on how the package should be moved.Without further information about the actual error it is not possible to know where to start troubleshooting the issue, and usually the first place to start is the job history of the job that failed.Hope this helps :)Nick. |
|
|
|
nicklarge
Starting Member
40 Posts |
Posted - 2012-10-23 : 17:08:58
|
| Oops, sorry, I see that you do have the information for the error on your original post.It looks like you need to register the component referred to in the script component [I assume that the error originated in the script component] on the new server.Regards, Nick. |
|
|
|
|
SSIS Package failure