SQL server agent job built on SSIS package not working

I transferred a job from the old SQL Server 2005 to an upgraded SQL Server 2008 R2 instance, and I scripted out everything, changed the data source and other details... "This job should copy some files automatically from stage locations to active directories" but it's not doing that like it was in the old server! So I'm not sure what I'm missing.

It seems that it's been built on an SSIS package as I can see from the file path location.
I'm trying to open this file using the SQL Server Integration Services, hoping to see the details about the stage location and the active directory details but I get an error about "Registration information for this application needs to be updated...", although there is a MS Visual Studio in the remote server and it should be up-to-date!

I don't know anything about Integration Services, and I see something in the code about
CONNECTION RCSMTP that I didn't change, maybe that need to be changed to this new server SMTP?

Below is the script for this job that's called elfCopy which is Electronic Library Format

```
USE [msdb]
GO

/ Object: Job [eLFCopy] Script Date: 12/30/2013 10:51:54 /
BEGIN TRANSACTION
DECLARE @ReturnCode INT
SELECT @ReturnCode = 0
/ Object: JobCategory [[Uncategorized (Local)]]] Script Date: 12/30/2013 10:51:54 /
IF NOT EXISTS (SELECT name FROM msdb.dbo.syscategories WHERE name=N'[Uncategorized (Local)]' AND category_class=1)
BEGIN
EXEC @ReturnCode = msdb.dbo.sp_add_category @class=N'JOB', @type=N'LOCAL', @name=N'[Uncategorized (Local)]'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback

END

DECLARE @jobId BINARY(16)
EXEC @ReturnCode = msdb.dbo.sp_add_job @job_name=N'eLFCopy',
@enabled=1,
@notify_level_eventlog=0,
@notify_level_email=0,
@notify_level_netsend=0,
@notify_level_page=0,
@delete_level=0,
@description=N'This job copies eLF files & folders from stage locations to active directories.',
@cat

I would advice you to upgrade the package by following these steps

If after your upgrade you still run in to problems, it could be that your package is using components/drivers that are not available on 64bit. In that case the "easiest" work around would be to have your package use a 32bit runtime.

Open de Job properties and then edit the job step that is calling the SSIS package.

Go to the Execution Options tab and check "use 32bit runtime"

It adds the switch /X86 to the Dtexec execution string. (please note that this switch will be ignored if you directly run it from the command line.)

However, be aware that in that case, you are running the package in 32bit while not making use of the 64bit benefits. This shouldn't have to be a problem, just something to keep in mind.

StackExchange Database Administrators Q#55832, answer score: 2