January 21, 2014 at 4:58 am
More than one developer working on one SSIS 2012 project.
Project protection level = dont save sensitive
Package protection level = dont save sensitive
I can create a new text file in the foilder where we save the packages but when I edit the package I can not save it?
When I log in as a different developer I can open and save the package.
When I log in as myself and go to save the package. A pop up file save box appears and when you click save to overwrite the original file you get an access denied message.
Very weird. Any suggestions gratefully received
Cheers
E
January 21, 2014 at 5:16 am
Have you checked your NTFS permissions on the package file?
John
January 21, 2014 at 5:32 am
On the folder that contains the project it comes up with a grey tick in the read only so I know some files \ folders undernmeath are read only.
So the top level has a sub foider for the project and a solution. The project folder is the one that comes up with a grey tick in the read only. I can change this but it does not seem to stick? i.e five minutes later its back as before.
All the packages in the project folder are not read only and thats where I will be saving the file.
Thanks
E
January 21, 2014 at 5:34 am
The Bin and Obj folders I just cant change that away from a greyed tick in the read only?
E
January 21, 2014 at 5:36 am
What are the permissions on ther actual file itself?
When changing NTFS permissions, you either need to change them at the level they were originally set and cascade them down, or change them directly on the object in question and disable inheritance.
John
January 21, 2014 at 6:18 am
The individual dtsx file is not showing as read only.
I can create or save a package as with a different name.
I cant run them from the designer now. It pops up a save as window before you can run it,
Puzzled.
😀
January 21, 2014 at 7:14 am
It's not a question of whether the file is read-only - it's whether you have permission to change it. Right-click on the file and choose Security. If you (or a group you are a member of) appear in the list of accounts with permissions with Change (I can't remember whether that's the exact name of the permission) then you should be able to save the package.
John
January 21, 2014 at 7:19 am
Having looked at another project I have created the bin folder and development subfolder both appear to have the same settings?
The only thing I can think about is the project we are having problems with the other developer was the first one to put it on the file system where it is stored as a project.
E
:crazy:
January 21, 2014 at 8:24 am
after a lot of effort this was resolved. Not quite sure which change did the trick but yes it was NTFS permissions based issue.
Quite a learning experience.
Thanks
😀
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply