VS2008 SSIS build error - cannot create the output file

Question

VS2008 SSIS build error - cannot create the output file

SQL Swerver

Hall of Fame

Points: 3074
More actions
January 14, 2016 at 7:18 am

#324026

I've downloaded an SSIS package from our own internal STASH/GIT source-control in order to add some functionality. The package is currently running successfully in production and obviously built successfully previously.
When I try to build the package and even before I've made any changes, I get the following build-failure error:
Error4Cannot create the output file "c:\ <filePath > \ <CurrentPackageName>.dtsx": The process cannot access the file 'c:\ <filePath > \ <CurrentPackageName>.dtsx because it is being used by another process..00
VS2008 (BIDS)
Windows 7 PC
I can rename the file, detach it from the solution, re-attach it, new name, none of this helps.
I've also investigated this error through this forum and MS:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/51d617bc-b80a-4d70-afed-75f44b1ebe7f/ssis-build-error?forum=sqlintegrationservices
https://social.technet.microsoft.com/Forums/sqlserver/en-US/5930e5b8-38c4-4b35-8cc4-c1a8f5b80dfd/error-cannot-create-output-file?forum=sqlintegrationservices
Has anybody seen this before?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246956 More actions · Answer 1

Are you opening a VS solution which includes the package? Or attempting to open the dtsx directly?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

SQL Swerver Hall of Fame Points: 3074 More actions · Answer 2

literally, download from Source, open VS Solution, click on Build package.

Update:

Moved the entire solution close to the root of C: drive in case the path was too long. No joy.

Exported a copy of the package from a pre-prod server and imported locally into my VS Solution. Same build error.

SQL Swerver Hall of Fame Points: 3074 More actions · Answer 3

This problem seems to only relate to my Windows account. My colleague does not have this problem on his PC, I still have the same problem on a different PC.

Weird.