Error Setting Security On Machine Software Licenses
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 19:21:25 GMT by s_ac15 (squid/3.5.20)
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Warning 1336: The access control list (ACL) structure is invalid. Want to Advertise Here? Solved Warning 1336: http://answers.microsoft.com/en-us/windows/forum/windows_7-security/warning-1336-the-access-control-list-acl-structure/b1b54d44-9320-4983-a1fe-61a925d212d3 The access control list (ACL) structure is invalid. Posted on 2005-04-25 Windows Server 2003 1 Verified Solution 3 Comments 2,993 Views Last Modified: 2008-01-09 Installed AD on a new server this morning and received the following message in the scedcpro.log file. Warning 1336: The access control list (ACL) structure is invalid. Error setting security on machine\software\license. This https://www.experts-exchange.com/questions/21401339/Warning-1336-The-access-control-list-ACL-structure-is-invalid.html server was added as a DC to an existing domain. Has anyone out there seen this before? If so, what gives? I have searched Microsoft and have not been able to find anything on this, as of yet. Any help would be appreciated! Thank you, Mike 0 Question by:keatscon Facebook Twitter LinkedIn Google LVL 20 Active 4 days ago Best Solution byLazarus Try these: http://support.microsoft.com/?kbid=178170 http://support.gradient.com/private/doclib/docs/osfhtm/refer/comref/Comref95.htm The ACLs can be different for each one. Go to Solution 3 Comments LVL 20 Overall: Level 20 Windows Server 2003 11 Message Active 4 days ago Expert Comment by:Lazarus2005-04-25 Your ACL is probably has the incorrect permissions. Use the access control list editor to fix the structure of the ACL. 0 Message Author Comment by:keatscon2005-04-25 Lazarus, I do not know what the permissions should be. Can you point me to a MS article that will tell me wha they shold be? Thank you, Mike 0 LVL 20 Overall: Level 20 Windows Server 2003 11 Message
Posted November 29, 2007 5:01 PM Categories: Vista I'm attempting to track down a very strange Windows Vista registry permissions issue that hit me on two machines, that I've found mentioned in random various forum http://brianpeek.com/post/weird-vista-registry-issue posts across the Internet, that has no known cause or solution, and which I cannot seem to reproduce in a VM though I've seen it happen on 2 machines across 4 Vista installs. I'm hoping everyone that happens to read this post will take a few minutes to check the following and contact me directly or leave a comment with a way to communicate back to you. Here's what to do: error setting Run regedit.exe, everybody's favorite Registry Editor. At the root node of HKEY_CLASSES_ROOT, right-click and select Permissions from the context menu. Report what you see. The first image is correct. The second image is the problem scenario. Subsequently, every subkey that is created or modified after this problem occurs has no permissions attached to them, causing all sorts of issues like COM components not being registered, file extensions not being registered, etc. error setting security Permissions on every entry prior to the problem occurring are set properly. I first noticed the problem when installing XNA 2.0 Beta, though its problems were caused by the already unnoticed and broken permission state. Several folks in the XNA forums have reported a similar issue with no evidence of a cause, though I did find a not-so-perfect solution for x86 machines. I have a feeling this is something that has happened recently, perhaps due to a Windows Update, but that's just a guess. I attempted to reproduce this in a VM and failed. I rebuilt my Vista x64 desktop since this was causing chaos and managed to reproduce it twice by installing Office 2007. Yet, doing that same thing in a clean Vista VM would not reproduce it. So that's not it either. There are reports of it happening on both x86 and x64 installs. There's obviously some sort of interaction here, but I have yet to find the common link. My original installations were running with UAC off. My first two re-install attempts ran with UAC off as I typically run. On the third re-install attempt I left UAC on instead of turning it off and that seemed to make all the difference. However....note that in attempting to r