Problem setting a SecurityDescriptor using ADSI
From: John Harvey (harveydad_at_hotmail.com)
Date: 01/24/04
- Next message: Dominick: "Removing the IPC Share Automatically"
- Previous message: Dominick: "Security Event ID 627"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 23 Jan 2004 19:33:03 -0800
Hello,
I have just run into an interesting problem when setting a Security
Decriptor on an NTFS file. I get the following error:
Run-time error '-2147023589 (8007051b)':
Automation Error
This security ID may not be assigned as the owner of this object.
I am logged in as the Domain Administrator, and I haven't tried to change
the ownership, I've simply added an ACE and tried to save the DACL with the
same (untouched) SecurityDescriptor
(i.e. objSecurity.SetSecurityDescriptor "D:\SecTest", ADS_PATH_FILE,
objSecDesc, ADS_SD_FORMAT_IID )
I was trying to add code to change the owner programmatically, so I went and
"manually" set the owner to another (non-admin) account to see if I could
pick up the change of ownership in my code, and then discovered that while
the owner was set to the non-admin account, I would get this error message
whenever I tried to write the SD, even though that account is already the
owner, and I'm not trying to change the ownership, just the DACL!
I would really appreciate any help you could give me... I obviously can't
deploy the component if it blows up when a different owner is set on file...
Thanks in Advance!
John Harvey
---- Go! Canucks, Go! http://www.canucks.com
- Next message: Dominick: "Removing the IPC Share Automatically"
- Previous message: Dominick: "Security Event ID 627"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
