Menu
The logs corresponding to the failed job are as follows:
04/11/2014 06:40:00,LPR_New,Error,0,USPHND0088,LPR_New,(Job outcome),,The job failed. The Job was invoked by Schedule 14 (LPR_New_Job). The last step to run was step 1 (Upload Material).,00:00:00,0,0,,,,0
04/11/2014 06:40:00,LPR_New,Error,1,USPHND0088,LPR_New,Upload Material,,Executed as user: nestle\ussqldbserver. ...00.5324.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 6:40:00 AM Error: 2014-04-11 06:40:00.39 Code: 0xC001700A Source: Description: The version number in the package is not valid. The version number cannot be greater than current version number. End Error Error: 2014-04-11 06:40:00.39
Code: 0xC0016020 Source: Description: Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.". End Error Error: 2014-04-11 06:40:00.39 Code: 0xC0010018 Source: Description: Error loading value "3" from node "DTS:Property". End Error Could not load package "\usphnd0088\dataxfer\LPR\LPR New\UploadMaterial.dtsx" becau... Process Exit Code 5. The step failed.,00:00:00,0,0,,,,0
600
When you see Properties select Configuration Properties. You will see TargetServerVersion , change that to other version click Yes if you see warning of Downgrade / Upgrade and then Click OK.
To determine what version of SSIS your packages are designed for, use your file explorer to navigate to where the packages are stored. Right click one and select 'Edit' or 'Open With Notepad'. Next, use the built in search feature by pressing both 'ctrl' and 'F' together.
In the Solution Explorer, Right-click on the SSIS package and click on Execute. The Red-Cross icon on the execute SQL Task shows that the package execution failed. Click on the Progress tab for the detailed error message. By looking at the following screenshot, we can identify the error message.
At the center of the project deployment model is the project deployment file (. ispac extension). The project deployment file is a self-contained unit of deployment that includes only the essential information about the packages and parameters in the project.
To provide a newer answer, using SQL Server Data Tools 2015, you can set the Deployment Target Version for your integration project to 2012, 2014 or 2016 (It defaults to 2016 and will result in version number errors on 2012/2014 DBs until you set it correctly). I successfully deploy SQL 2012 integrations now from SSDT 2015 after setting to "SQL Server 2012".
170
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
