January 31, 2018 at 11:52 am
Hello -
I'm encountering a problem with SSIS which i've not ever experienced before. I'll create a solution, work on the .dtsx file, save it, run it, etc and everything is fine. Then suddenly at some point i'll make a change - add a new data flow, for example - and then when I go to save the package i'll get a window which says I do not have permission to access the file. Trying to create another solution and attaching the package .dtsx file doesn't work, either, as I get the same permissions issue. Checking the permissions on both the file and the folder, I see that I have full control of both. Last week when I encountered this issue I simply restarted the machine and everything was fine. Today, however, after the restart the package .dtsx file is completely GONE from my hard drive.
GONE.
What the hell could be causing this issue? I've used SSIS for years now and have never ever experienced this before.
How do I get my package file back, and how the hell do I prevent this from happening in the future?
I'm using SSIS 2008 and saving my solution files to the default Projects folder (C:\Users\MyAccount\Documents\Visual Studio 2008\Projects)
Ugh....the joys of SSIS.
January 31, 2018 at 5:49 pm
Polymorphist - Wednesday, January 31, 2018 11:52 AMHello -
I'm encountering a problem with SSIS which i've not ever experienced before. I'll create a solution, work on the .dtsx file, save it, run it, etc and everything is fine. Then suddenly at some point i'll make a change - add a new data flow, for example - and then when I go to save the package i'll get a window which says I do not have permission to access the file. Trying to create another solution and attaching the package .dtsx file doesn't work, either, as I get the same permissions issue. Checking the permissions on both the file and the folder, I see that I have full control of both. Last week when I encountered this issue I simply restarted the machine and everything was fine. Today, however, after the restart the package .dtsx file is completely GONE from my hard drive.GONE.
What the hell could be causing this issue? I've used SSIS for years now and have never ever experienced this before.
How do I get my package file back, and how the hell do I prevent this from happening in the future?
I'm using SSIS 2008 and saving my solution files to the default Projects folder (C:\Users\MyAccount\Documents\Visual Studio 2008\Projects)
Ugh....the joys of SSIS.
I would guess you checked the recycle bin just to make sure. Other than viruses, malware and such the only other thing that I can think of that would result in files disappearing would be disk issues. Did you check the Windows event logs?
The other possibility is the file may be there but you could have something wrong with your profile - you'd usually have other weird things happening though as well. Nonetheless, it might be worth it to open a command prompt with run as administrator and try the location where the file is suppose to be as well as search the drive from the command prompt.
Sue
February 1, 2018 at 10:58 am
Thanks Sue.
I highly suspect this issue has something to do with account permissions via Visual Studio however I can't be certain. I did create a new folder at the root of C:\ and given myself explicit full-control permissions, hoping this means I won't ever see an issue like this again.
BTW, everyone in the office thinks i'm nuts after this happened. Not a great feeling, LOL.
February 6, 2018 at 6:49 am
Polymorphist - Thursday, February 1, 2018 10:58 AMThanks Sue.I highly suspect this issue has something to do with account permissions via Visual Studio however I can't be certain. I did create a new folder at the root of C:\ and given myself explicit full-control permissions, hoping this means I won't ever see an issue like this again.
BTW, everyone in the office thinks i'm nuts after this happened. Not a great feeling, LOL.
Are you also using Source Safe and are there multiple developers who work on the same project? I had issues similar to yours caused by Source Safe. We had to make sure if one developer was working on a project another would not also open it to make changes. It caused all kinds of grief.
February 6, 2018 at 12:20 pm
tim.ffitch 25252 - Tuesday, February 6, 2018 6:49 AMAre you also using Source Safe and are there multiple developers who work on the same project? I had issues similar to yours caused by Source Safe. We had to make sure if one developer was working on a project another would not also open it to make changes. It caused all kinds of grief.
No, my solution wasn't actually under source control yet, it was strictly on my local machine. This has to be a permissions issue between the directories and Visual Studio, since creating a new folder with explicit full control permissions I haven't had any problems.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply