|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
My Windows account do not have administrator priviliges anymoreMy Windows account do not have administrator priviliges anymore even though the user account window accessible from the control panel claims I do. I did my first time programming with setting ACL:s. I thought I had completed my application since it seemed to work fine setting the ACL:s the way I wanted to. Then I had a huge problem one day all of a sudden. My laptop claimed I did not have DotNet 2.0 installed (even though I have, I can even see it in the add/remove programs list). I went into Windows explorer and clicked on the c:/Windows folder. The Microsoft.NET folder existed but it had no + sign indicating subfolders. When clicking on it it I get a not available, access denied kind of message. I am not able (or allowed maybe) to install, repair or remove DotNet 2.0. I went to "Windows Update" on the Web to download updates for my OS (Win XP pro SP2 by the way) but there I got the message that I have to have administrator priviligies to update Windows. The very same thing happened a couple of weeks later on my other computer (this one I am using right now, I guess I will format this one tonight...) Can it be my application messing my system up? All I do is set some files (application specific) (full rights except delete) for all Windows accounts. My application is written in c# and depends on DotNet 2.0. The methods I use for setting ACL's are: AddAccessRule, RemoveAccessRule, SetAccessControl. During the developement of this application (about a year) I have NOT had this problems earlier. I got them after trying setting ACL's. One other thing I have done recently is adding dotnet2.0 and windows installer 3.1 as prerequisites in my VS2005 setup project (could this be the source of my problem?). I guess these methods have been used plenty and also VS2005 setup project has been tested very much. When I got the problems on the first computer I thought, well a case of bad luck... but when I got it again on another computer I begin to wonder. I have tested for viruses - none found. Right click on the framework folder and go to properties, security, advanced
(button), Owner. take ownership of it. then you can add permissions to it. It has probably lost the ACL allowing admins access but Owners alsways have access to change permissions. Ciaran O'Donnell Show quote "Marcus" wrote: > Hi, > > My Windows account do not have administrator priviliges anymore even > though the user account window accessible from the control panel claims > I do. > > I did my first time programming with setting ACL:s. I thought I had > completed my application since it seemed to work fine setting the ACL:s > the way I wanted to. > > Then I had a huge problem one day all of a sudden. My laptop claimed I > did not have DotNet 2.0 installed (even though I have, I can even see > it in the add/remove programs list). > > I went into Windows explorer and clicked on the c:/Windows folder. The > Microsoft.NET folder existed but it had no + sign indicating > subfolders. When clicking on it it I get a not available, access denied > kind of message. > > I am not able (or allowed maybe) to install, repair or remove DotNet > 2.0. > > I went to "Windows Update" on the Web to download updates for my OS > (Win XP pro SP2 by the way) but there I got the message that I have to > have administrator priviligies to update Windows. > > The very same thing happened a couple of weeks later on my other > computer (this one I am using right now, I guess I will format this one > tonight...) > > Can it be my application messing my system up? > > All I do is set some files (application specific) (full rights except > delete) for all Windows accounts. My application is written in c# and > depends on DotNet 2.0. The methods I use for setting ACL's are: > AddAccessRule, RemoveAccessRule, SetAccessControl. > > During the developement of this application (about a year) I have NOT > had this problems earlier. I got them after trying setting ACL's. One > other thing I have done recently is adding dotnet2.0 and windows > installer 3.1 as prerequisites in my VS2005 setup project (could this > be the source of my problem?). > > I guess these methods have been used plenty and also VS2005 setup > project has been tested very much. When I got the problems on the first > computer I thought, well a case of bad luck... but when I got it again > on another computer I begin to wonder. I have tested for viruses - none > found. > > |
|||||||||||||||||||||||