October 11, 2014 at 10:45 am
Hi,
The job is running in Sql 2012 succefully.
I migrated that job in to Sql 2014 instance that is running in seperate box.
The job is running the ssis package. That is developed in 2012 and running fine in 2012 machine. After I scheduled that job in SQL 2014 SSMS job failed with the error message
Source file 'C:\Windows\TEMP\.NETFramework,Version=v4.0.AssemblyAttributes.cs' could not be found.
But this box already has .netframework 4.5
What is the solution to run this job?
October 11, 2014 at 10:49 am
ramana3327 (10/11/2014)
Hi,The job is running in Sql 2012 succefully.
I migrated that job in to Sql 2014 instance that is running in seperate box.
The job is running the ssis package. That is developed in 2012 and running fine in 2012 machine. After I scheduled that job in SQL 2014 SSMS job failed with the error message
Source file 'C:\Windows\TEMP\.NETFramework,Version=v4.0.AssemblyAttributes.cs' could not be found.
But this box already has .netframework 4.5
What is the solution to run this job?
Quick thought, is SSIS 2012 installed on the SQL 2014 box? There are different runtime files for these two versions.
😎
October 11, 2014 at 10:53 am
No SSIS 2012 is in different machine. In present box SQL 2008 R2 & Sql 2014 is running.
I selected the Integration services features while the installation of Sql 2014 but didn't see that data tools under 2014 folder.
What is the solution? Do I need to download (install) seperately the datatools. Why it didn't come with installation 2014 when I select the integration services folder
October 11, 2014 at 11:03 am
The SSDT 2014 is an additional download (last time I checked). To run the 2012 jobs/packages on the 2014 system there are two options, install the 2012 SSIS components on the system or upgrade the 2012 packages to 2014. For the upgrade, 2014 SSDT must be used.
😎
October 11, 2014 at 11:57 am
Hi Errikson,
I can't install the 2012 SSIS components on the system. I want to upgrade the 2012 packages to 2014. For the upgrade, 2014 SSDT must be used.
How can I get 2014 SSDT. Do I need to install seperately other than SQL installation?
I am using the Remote desktop, how to run SSDT on that machine?
October 11, 2014 at 12:09 pm
It is a separate download, SQL Server Data Tools for SQL Server 2014.
😎
October 11, 2014 at 4:21 pm
Thank You
October 13, 2014 at 10:17 am
Hi Eirikur,
I downloaded the the SQL Server data tools from the link you provided and try to run on the remote desktop where the Sql 2014 installed but there is no files to open this .iso file.
Before that I saw installed programs to make sure the Sql 2014 installation but it is showing that
installation of visual studio application for run time.
What is that mean is that work only for run time? It will work after seperated installation of SSDT
October 14, 2014 at 9:00 am
Hi,
The job is running fine in SSMS 2012. It is failing in 2008 R2 & 2014.
When I run the job in 2014 it is throwing error
code:0*00000005
Source: script1
Description: Failed to compiled scripts contained in the package. open the ssis package in SSIS designer and resolve the compilation errors
Source: script1
description: cs2001 source file 'c\\windows\temp\.netframework, version=4.0 Assembly attributes.cs couldn't be found ,scs,0,0
code:0*00000005
Source: script1
Description: The binary code for the script is not found. Please oopen the script in the designer by clicking the edit script button and make sure it builds successfully
I have two script tasks, it giving two similar error msgs
I tried to attach the package in BIDS (2008) but it is showing error that loading XML is failed
so I installed data tools and tried to edit that script task to build but it is not allowing me to do that and giving error
can't show visual studio 2012 tools for application editor
couldn't load file or assembly. The system can't find the file specified
January 19, 2016 at 11:10 am
Eirikur Eiriksson (10/11/2014)
The SSDT 2014 is an additional download (last time I checked). To run the 2012 jobs/packages on the 2014 system there are two options, install the 2012 SSIS components on the system or upgrade the 2012 packages to 2014. For the upgrade, 2014 SSDT must be used.😎
Hi, to install 2012 components on 2014 servers? Can we just copy file contents under 110 folder from SQL 2012 installation folder?
or Can you please explain how to do this?
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply