Ds Error 14009 Mac
enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked quarterwit Level 1 (0 points) Q: Unable to make any
by just holding the power button all users have lost administrator access they might have had before. A very quick fix helps most people: - Restart - Hold down Apple + S when the first blue/greyish screen appears to boot into single user mode - The hard drive is mounted read-only so we have to do $ /sbin/fsck -fy $ /sbin/mount -uw / - Now the system's standard root user (whom we are at the moment) gets a password (any will do) so we can log in with it $ passwd $ exit - Click on "Other" in the Login Window and login as user "root" with the password you have just https://discussions.apple.com/thread/1448801?tstart=0 assigned to him - Use "System Preferences" -> "Accounts" to give administrator access back to the users whom you want to have it - Log out - Log in with your newly re-appointed administrator, launch Directory Utility, authenticate by clicking on the lock icon and disable the root user via "Edit" -> "Disable Root User" Most users live happily ever after but for some this simply doesn't work. Specifically System Preferences seems to https://panoramification.wordpress.com/2008/03/22/fixed-mac-os-x-users-lost-administrator-access/ immediately "forget" that you want a specific user to be an administrator. You tick the box, you click on another user or click the lock and then when you click on your desired administrator again the box is unchecked once more. The more curious among us will at this time already have checked the system logs where most likely the message "mbr_group_name_to_uuid failed with err=2" sticks out. At the usual places (discussions.apple.com, et al) people will want you to insert your installation disk, use a password utility, reboot repeatedly, even reinstall your OS X or just pray. Well, welcome to panoramification where everything is different ;) What we'll do is the following: - back to single user mode as described above, also do the fsck and mounting 1. load directory services: $ launchctl load /System/Library/LaunchDaemons/com.apple.DirectoryServices.plist 2. Try to add a user to the admin group, use the shortname of the user for this $ dscl . append /groups/admin GroupMembership myuser - If this works: congratulations. Reboot and you're done! If however it fails with =>
Password Your News Feed Likes You've Received Your Content People You Follow People You Ignore Log Out Show online status Conversations Show All... https://macosx.com/threads/dscl-please-help.297965/ Alerts Alert Preferences Show All... macosx.com Home Forums Forums Quick Links Search Forums Recent Posts Media Media Quick Links Search Media New Media Members Members Quick Links Notable Members Current Visitors Recent Activity New Profile Posts Menu Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display ds error results as threads More... Useful Searches Recent Posts Mac Support Forums Mac Help Forums Mac OS X Server dscl - please help Discussion in 'Mac OS X Server' started by cupojava, Jan 25, 2008. cupojava uix_expand uix_collapse Registered Joined: Nov 29, 2007 Messages: 8 Likes Received: 0 I upgraded from OS X Server 10.4.10 to 10.5 recently and I've ds error 14009 experienced nothing but problems. It seems as though whenever I use Server Admin to set up a file share, then attempt to "unshare" it, client nodes are still attempting to mount it. For example, I have a folder called "scratch" which I "shared" then "unshared". After "unsharing", running the command `showmount -e` fails to show the directory "scratch" as an export... which is correct. However, running this command: dscl /LDAPv3/127.0.0.1 -list /Mounts does in fact reveal the directory... which is wrong. I know for a fact that this is where it needs to be deleted because I had this exact problem on another 10.4 Server. I'm pretty sure I remember the dscl syntax for deleting a node, but on this machine I only get an error. % dscl -u