SSIS Package fails after move from Server 2003 to Server 2008 R2 with SQL 2005 SP3
I have SQL 2005 (64-bit) and Visual Studio 2005 Premier Partner Edition - ENU Service Pack 1 installed on a Server 2008R2 machine. I am in the process of upgrading my entire network and moving things from one server to another. I have several issues and I am not familiar at all with this so I don't know the precedence of the items. 1) I have a project that I did in SSIS on a 2003 (32-bit), box. I am running this through SQL Agent on a nightly basis and it works. I setup a new server (2008 R2), loaded SQL 2005 SP4, copied the project files and attempted to duplicate the process. The job fails. The history shows: Message Executed as user: BRUBAKER\Administrator. Microsoft (R) SQL Server Execute Package Utility Version 9.00.5000.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:00:01 PM Error: 2011-03-30 21:00:13.84 Code: 0xC002F304 Source: File System Task File System Task Description: An error occurred with the following error message: "Cannot create a file when that file already exists. ". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:00:01 PM Finished: 9:00:13 PM Elapsed: 12.531 seconds. The package execution failed. The step failed. 2) When I open SQL Server Business Intelligence Development Studio, I get an error that Visual Studio 2005 SP1 requires an updates for Windows Vista. I tried to run the update, but get an error code. I thought maybe it was because the download indicates x86, but I can't find a 64-bit version of the update anyway. So I am spinning my wheels trying to figure out if the there is an update that needs to be run or if the project has to be redone or if none of this is doable in my environment and I need to upgrade something to get this to work. I am not a developer by any stretch of the imagination and this was my first project and I blundered my way through getting it to work on my Server 2003, SQL 2005 box 9 months ago. Help Anyone?
April 13th, 2011 4:14pm

I think you just have a security issue, specifically the user account executing the SSIS package job has not the same rights this package used to run under that other account. Try running the package manually if I am not right, does it work then? And what you 've done to resolve the "file already exists" issue?Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 4:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics