SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Denied Access to DTSX File - File is Now Missing From Solution After Restart


Denied Access to DTSX File - File is Now Missing From Solution After Restart

Author
Message
Polymorphist
Polymorphist
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1036 Visits: 321
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.
Sue_H
Sue_H
SSC-Dedicated
SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)

Group: General Forum Members
Points: 35746 Visits: 10221
Polymorphist - Wednesday, January 31, 2018 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.


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



Polymorphist
Polymorphist
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1036 Visits: 321
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.
tim.ffitch 25252
tim.ffitch 25252
Right there with Babe
Right there with Babe (773 reputation)Right there with Babe (773 reputation)Right there with Babe (773 reputation)Right there with Babe (773 reputation)Right there with Babe (773 reputation)Right there with Babe (773 reputation)Right there with Babe (773 reputation)Right there with Babe (773 reputation)

Group: General Forum Members
Points: 773 Visits: 143
Polymorphist - Thursday, February 1, 2018 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.

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.

Polymorphist
Polymorphist
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1036 Visits: 321
tim.ffitch 25252 - Tuesday, February 6, 2018 6:49 AM

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.

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.

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search