October 30, 2008 at 5:42 pm
For the last few days I've been experiencing a problem when trying to add a previously created package to a project. Regardless of where the package was created or where I am trying to save it, I get the following message:
Failed to save package file "[file path]" with error 0xC020207E "The file name is not valid. The file name is a device or contains invalid characters."
The source and destination are both in the file system.
Leaving aside the possibility that the file name really is invalid (it is not!), does anyone have any ideas what else could cause this? It seems like some gremlin has crept into my dev environment somewhere.
Thanks
Phil
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
October 30, 2008 at 11:07 pm
A reinstall of VS2005 and .NET Framework 2 has not fixed it. Bizarre.
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
November 12, 2008 at 5:00 pm
I'm getting the same error.
Have you made any progress?
November 13, 2008 at 12:50 am
No - this error was driving me so mental with irritation that I had to give up before I snapped!
I now use traditional copy/paste methods to get the job done - thankfully it's not too often that I need to do this.
If you find a solution, please post it. And when your boss asks you what you were doing for the last three hours and you say: "Trying to add a copy of an existing package to my solution," be prepared for some supplementary questions 🙂
Phil
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
November 13, 2008 at 6:43 am
Phil Parkin (11/13/2008)
No - this error was driving me so mental with irritation that I had to give up before I snapped!I now use traditional copy/paste methods to get the job done - thankfully it's not too often that I need to do this.
If you find a solution, please post it. And when your boss asks you what you were doing for the last three hours and you say: "Trying to add a copy of an existing package to my solution," be prepared for some supplementary questions 🙂
Phil
LOL. I arrived at the same place you did. I had been debugging with filemon and found it checks if the file is present. If not found it gives the error. So I put a dummy file with same name hopeing it would ask to replace it. Instead when it finds that file it then checks for "filename (1).dtsx" and since that one is missing gives an error. Crazy, yet for internet searches it appears to work for some and not for others.
Mike
March 19, 2009 at 10:03 pm
I was having this problem in my home computer, today this started in my main computer at work. I have installed the SQL Server 2008, but the same error appears in both computers. I have used the solution to create a file with the name, and it works. There will be a solution other than this?
July 6, 2009 at 12:55 pm
Did anybody ever figure this out? There are 3 of us that work on SQL and SSIS. One of us can open "older" SSIS (DTSX) files and the other two get this error. There is nothing wrong with the DTSX file so it has to be something bungled in our SQL Dev environment. Very furstrating that I cannot open legitimate files.
July 6, 2009 at 9:52 pm
Never got to the bottom of it. Somehow, by some means, the problem stopped happening for me. I have no idea why. Seeing your post reminded me of just how annoying this one is.
Does it happen for all solutions, or just one?
Phil
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
July 11, 2009 at 4:42 am
Thanks for coming back to this one Phil. I'm glad the problem went away for you. For me the challenge of developing has moved from writing good code to getting my tools to be consistent...
Anyway, to answer your question the problem never occurs for packages that we've written using SQL 2005 on our XP computers. It's pretty much any SSIS or converted DTS that started it's life on Windows 2000. One of my guys found a thread about just that. They suggested installing SQL 2000 on the XP machine, open the DTS package and save it and then we should be able to work with it using VS 2005. I'll report back after we learn more.
Later
September 10, 2009 at 11:09 am
Well -- should I say just happen to think a little 'twisted'
My Problem was:
I have two SSIS VSS solutions so...I wanted to merege them to one solution and ....the error....
Soluition:
1. Create a new package in your solution "package.dtsx"
2. Saving at the "Pain.dtsx" ("pain.dtsx" is the name of the package your are importing
3. copy and replace the files ...VSS studion will prompt you to reload...YES!! 🙂
eliman
October 9, 2009 at 8:35 am
I was having this same issue and this worked for me: right click the project (or use the project menu) and select "Add, Existing Item...". That worked like a charm.
October 14, 2009 at 2:47 am
Thanks all. The create, reload option worked for me....
January 27, 2011 at 1:37 am
I have also same problem.
But I've resolved it by following Steps.
1. Open .dtsx file in Notepad ( to view XML source).
2. Create New SSIS package in solution where you wanted to copy it.
3. Close design mode of newly created package.
4. Open source code of newly created package (Right click package, click on view Source).
5. Remove all xml code.
6. Copy all source code from step 1 and Paste it.
7. Close source mode and open it on design mode.
Hope this will work for you.
Thanks.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply