Process 1 exec/sbin/Launchd failed, errno 85\n"@SourceCache/........ bla bla bla

my mac get freez and now could not boot.
just a black screen with some text
Process 1 exec/sbin/Launchd failed, errno 85\n"@SourceCache/........ bla bla bla
i have access to macintash hd from bootcamp.
i tired everything.
- premision fix via disk utility or ...
- command + option +p r
- hold down shift key
but no luck.
there is no way for fix this problem via windows?
q2 : can i make bootable usb disc with windows?

Hi,
Is there more after that on the same line?
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
Reboot, test again.
If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts (Users & Groups in later OSX versions)>Login Items window to see if it or something relevant is listed.
Check the System Preferences>Other Row, for 3rd party Pref Panes.
Also look in these if they exist, some are invisible...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
/System/Library/LaunchDaemons
/Library/LaunchDaemons

Similar Messages

  • Process 1 exec/sbin/Launchd failed, errno 85\n"@SourceCache/xnu-xnu-1504.15

    What does this take to fix ?

    Hi,
    Is there more after that on the same line?
    Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
    Reboot, test again.
    If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts (Users & Groups in later OSX versions)>Login Items window to see if it or something relevant is listed.
    Check the System Preferences>Other Row, for 3rd party Pref Panes.
    Also look in these if they exist, some are invisible...
    /private/var/run/StartupItems
    /Library/StartupItems
    /System/Library/StartupItems
    /System/Library/LaunchDaemons
    /Library/LaunchDaemons

  • Panic(cpu 0 caller 0x47f5ad): "Process 1 exac of /sbin/launchd failed, errno 8\n"@/SourceCache/xnu/xnu-1504.15.3/bsd/kern/kern_exec.c:3145 Anyone know a fix?

    I'm really curious, so far I've isolated it down to the HDD, I've tried Data Migration using firewire, and Target Disk mode. Anything would help.

    what is your mac OS version and your iMac model? The pre-2006 iMacs this forum covers have different troubleshooting steps from newer iMacs, so we need to make sure which you have. The non-intuituve forum labeling here means people with relatively recent iMacs are tricked in to posting here instead of a more active forum for iMacs made since 2006.

  • Error sbin/launchd failed errno 2 Help!

    Hi, have a MacBook Pro and upon start up the full error that has come up is panic(cpu 0 aller 8xffffff800047cc6c): "Process 1 exec of /sbin/launchd failed, errno 2\n"@/SourceCache/xnu/xnu-1504. 15.3/bsb/kern/kern_exec.c:3145
    It just tells me to restart my computer. Hold down the power button until it turns off, then press the power button again.... that's it!
    I put the disc in that it came with so I could see if a recovery file has come up but nothing.
    Please know that I'm not a tech, but I can follow instructions well.
    Can anyone help please?

    Hi, have a MacBook Pro and upon start up the full error that has come up is panic(cpu 0 aller 8xffffff800047cc6c): "Process 1 exec of /sbin/launchd failed, errno 2\n"@/SourceCache/xnu/xnu-1504. 15.3/bsb/kern/kern_exec.c:3145
    It just tells me to restart my computer. Hold down the power button until it turns off, then press the power button again.... that's it!
    I put the disc in that it came with so I could see if a recovery file has come up but nothing.
    Please know that I'm not a tech, but I can follow instructions well.
    Can anyone help please?

  • Load of /sbin/launchd failed, errno 2 - CRT iMac

    Hi,
    I've been working on my parents' iMac, which was booting to Darwin. I followed the instructions in another thread and booted to single user mode, and then did the /sbin/fsck -fy. This produced a massive stream of errors to be corrected - it went for pages and pages. I didn't write it down, because I didn't expect to be locked out, but it was lots of different errors. It seemed to be correcting things, but then it got to something about a directory or header file, and it stalled on the message **Look in the lost-found something something for the missing files**. At this point it died...I gave it some time, and when it was obvious nothing was going on, I hesitantly forced a reboot.
    Now in a single-user boot I can't even get to a command prompt. I wrote down some of the last few lines displayed:
    BSD root diskOs5, major 14, minor 5
    jnl: journal start/end pointers reset (some number strings in here)
    Load of /sbin/launchd errno2, trying /sbin/mach_init
    Load of /sbin/launchd failed, errno2
    And that's where it stops every time. Is it bricked? I'm afraid I don't know what their model is, but I believe there were running the latest Mac OS compatible with a CRT iMac - I recall putting more RAM in the machine so they could upgrade the OS a year ago, maybe.
    Many thanks...

    Since it's a slot-loader iMac (600 MHz), you can use a feature called FireWire Target Disk Mode.
    http://support.apple.com/kb/HT1661
    You can then connect the iMac to your other Mac using a FireWIre cable (assuming it also has a FireWire port). Now, the iMac's hard drive will (hopefully) appear as an external FireWire drive on the other Mac's Desktop. If that works, immediately attempt to copy off all the valuable user data on the iMac's hard drive to the other Mac. Then, if the other Mac has sufficient free storage space, you may want to make a disk image of the iMac's hard drive using Disk Utility. After the image file is created and saved to the other Mac, make sure it can be mounted and accessed.
    At this point, you should try using Disk Utility on the other Mac to repair the iMac's hard drive. If the other Mac has Leopard, it has a newer version of Disk Utility so it may be able to do the fix.
    If that does not work, and you don't have third party utilities such as DiskWarrior or TechTool Pro to try, you should probably erase the iMac's internal drive using Disk Utility. After erasing completes, go to the Restore tab in Disk Utility. Make that disk image file the Source and the newly erased internal drive the Destination. Check the box for +Erase destination+, and click the Restore button.
    If that process completes successfully, use +Repair Disk+ again to make sure there are no errors on the iMac's internal drive. Then, unmount the iMac's internal drive and disconnect the iMac from the other Mac, and attempt to start it up normally.
    If it does start up and operate normally, great... If not, you may have to start up from the Mac OS X installation disk for 10.4.x and use the installation option for +Archive and Install+. This this give you a fresh system while retaining the user's account and data. Be sure to run Software Update a few times to install all the updates.
    Worst case (if +Archive and Install+ does not make the Mac bootable), you will have to use the +Erase and Install+ option and then separately restore the user's data from that disk image.
    Please post back if there are any questions about the above, or you don't get passed one of my many "if" statements.

  • Panic(CPU 1 caller 0xffffff800005412af): "Process 1 exec of /sbin/launchd failed, errno 85"@/SourceCAche/xnu/xnu-1699.31.2/bsd/kern/kern_exec.c:3536   HELP. WHAT DOES THIS MEAN!!

    I tried to turn my mac on 2 days ago and this is what came up. The message tells me to restart my computer but every time I do it just comes back to the same screen. We done have Internet at my home so I am unsure how this could have happened. Any help would be greatly appreciated.

    what is your mac OS version and your iMac model? The pre-2006 iMacs this forum covers have different troubleshooting steps from newer iMacs, so we need to make sure which you have. The non-intuituve forum labeling here means people with relatively recent iMacs are tricked in to posting here instead of a more active forum for iMacs made since 2006.

  • Load of /sbin/launchd failed, errno88 - revisited

    Hi,
    I am looking for a solution to what seems to be a fairly frequently occuring problem.
    Software Update ran on my MacBook, failed to download/install some OS update (I think it was 11), told me to reboot, when I rebooted, I got the apple logo and a spinning wheel.
    Verbose mode gives me /sbin/launchd failed, errno 88.
    Can't log in via Single User mode, same reason - stops at /sbin/launchd failed, never get to the prompt.
    Ran fsck in target mode as a sudo (that, and diskutil, and fsck_hfs - all came back that my volume was fine). http://docs.info.apple.com/article.html?artnum=106214 on using those commands
    Can't boot to my installation DVD to fix it as was described in http://discussions.apple.com/thread.jspa?threadID=1250841&tstart=75
    Nor can I see the CD option when I boot with Option key, nor shift-option-command-delete (is that still supposed to work on the new Wintels?)
    However, I can access my slot loader if I boot my MacBook in target mode onto another Mac (unfortunately, it's not a Wintel Mac, so I can't run the Installer on it to reinstall the upgrade and hopefully fix my Mac).
    Why can I access my CD drive from another machine in target mode, but not from my machine when trying to reboot from the installation disk? I think if I could get the machine to boot from CD, I could finish the upgrade (which is already downloaded and on my MacBook, I just can't install it), and hopefully that'll get 'er done.
    Any ideas / suggestions would be greatly appreciated.
    Best Regards.

    Hi,
    I am looking for a solution to what seems to be a fairly frequently occuring problem.
    Software Update ran on my MacBook, failed to download/install some OS update (I think it was 11), told me to reboot, when I rebooted, I got the apple logo and a spinning wheel.
    Verbose mode gives me /sbin/launchd failed, errno 88.
    Can't log in via Single User mode, same reason - stops at /sbin/launchd failed, never get to the prompt.
    Ran fsck in target mode as a sudo (that, and diskutil, and fsck_hfs - all came back that my volume was fine). http://docs.info.apple.com/article.html?artnum=106214 on using those commands
    Can't boot to my installation DVD to fix it as was described in http://discussions.apple.com/thread.jspa?threadID=1250841&tstart=75
    Nor can I see the CD option when I boot with Option key, nor shift-option-command-delete (is that still supposed to work on the new Wintels?)
    However, I can access my slot loader if I boot my MacBook in target mode onto another Mac (unfortunately, it's not a Wintel Mac, so I can't run the Installer on it to reinstall the upgrade and hopefully fix my Mac).
    Why can I access my CD drive from another machine in target mode, but not from my machine when trying to reboot from the installation disk? I think if I could get the machine to boot from CD, I could finish the upgrade (which is already downloaded and on my MacBook, I just can't install it), and hopefully that'll get 'er done.
    Any ideas / suggestions would be greatly appreciated.
    Best Regards.

  • Forwarding FAILED: errno=Broken pipe

    Hi,
    I have the following SMTP error when I try to send mail.
    host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=03105-02, forwarding FAILED: errno=Broken pipe (in reply to end of DATA command
    no matter what i try, it won't work. Does anyone has an idea? that would be really sweet!!!
    _Here is my postconf -n output :_
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains =
    messagesizelimit = 15728640
    mydestination = $myhostname,localhost.$mydomain,localhost,server.eremiya.com,eremiya.com
    mydomain = eremiya.com
    mydomain_fallback = localhost
    myhostname = server.eremiya.com
    mynetworks = 168.100.189.0/28, 127.0.0.0/8
    mynetworks_style = host
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdclientrestrictions = permitsaslauthenticated permit_mynetworks rejectrblclient zen.spamhaus.org permit
    smtpdenforcetls = no
    smtpdpw_server_securityoptions = cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpdtls_certfile = /etc/certificates/Default.crt
    smtpdtls_keyfile = /etc/certificates/Default.key
    smtpduse_pwserver = yes
    smtpdusetls = yes
    unknownlocal_recipient_rejectcode = 550
    unknownvirtual_alias_rejectcode = 450
    unknownvirtual_mailbox_rejectcode = 450
    virtualaliasdomains = hash:/etc/postfix/virtual_domains
    virtualaliasmaps = hash:/etc/postfix/virtual
    virtualmailboxdomains = hash:/etc/postfix/virtualdomainsdummy
    virtual_transport = lmtp:unix:/var/imap/socket/lmtp
    _End of output_
    Thanks a lot in advance!!

    This looks like either a problem in your amavisd configuration in /etc/amavisd.conf (amavisd is the content filter) or in /etc/postfix/master.cf
    If you made any changes to those files, look for typos.

  • Launchd fails on re-login

    Hi,
    I have a launchd job that watches a file. This works fine as is, but when I log out and back in again it fails. It does not fail if I restart and login again. This seems odd to me, can anyone suggest what I'm doing wrong.
    After re-login, with Debug activated, I get this report in the Console when the watchfile is modified:
    launchd[225]: com.nhoj.myDates: log level debug temporarily enabled while processing job
    launchd[225]: com.nhoj.myDates: watch path modified: /Users/john/Library/Application Support/AddressBook/AddressBook.data
    launchd[225]: com.nhoj.myDates: Starting
    launchd[225]: restoring original log mask
    launchd[225]: com.nhoj.myDates: log level debug temporarily enabled while processing job
    launchd[225]: restoring original log mask
    2006-01-21 12:15:54.721 applet[377] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x2703, name = 'Processes-0.2359297'
    See /usr/include/servers/bootstrap_defs.h for the error codes.
    2006-01-21 12:15:54.725 applet[377] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (Processes-0.2359297)
    CFMessagePortCreateLocal failed (name = Processes-0.2359297 error = 0)
    launchd[225]: com.nhoj.myDates: log level debug temporarily enabled while processing job
    launchd[225]: com.nhoj.myDates: Reaping
    launchd[225]: com.nhoj.myDates: exited abnormally: Abort trap
    launchd[225]: com.nhoj.myDates: 8 more failures without living at least 60 seconds will cause job removal
    launchd[225]: restoring original log mask
    This is the XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Debug</key>
    <true/>
    <key>Label</key>
    <string>com.nhoj.myDates</string>
    <key>OnDemand</key>
    <true/>
    <key>ProgramArguments</key>
    <array>
    <string>/Users/john/PATHTOAPP/Contents/MacOS/applet</string>
    </array>
    <key>WatchPaths</key>
    <array>
    <string>/Users/john/Library/Application Support/AddressBook/AddressBook.data</string>
    </array>
    </dict>
    </plist>
    Thanks for any help.
    John M

    Hi John,
       There's certainly nothing wrong with your property list. I'm impressed. I don't think that Apple has documented Launchd that well and yet you've even discovered the debugging feature. I'm also intrigued with the idea of watching your address book. It sounds like you're up to something rather interesting.
       Considering the bugs in the early releases of Launchd, I was quite prepared to blame it. However, the first report of a problem comes from something named "Applet", with a process ID of 377. Since your program argument points to a file in an app bundle named "applet", I have to think that it is experiencing the problem instead of Launchd. Since you're careful to cover the name of the application bundle, I assume that it's not one of Apple's. Is that your own -- maybe a project on which you're working?
       I'm impressed with this applet as it's even polite enough to tell us where to look for the definition of the error that it throws. Error number 1100 is defined in bootstrap_defs.h as BOOTSTRAPNOTPRIVILEGED. I'm not a Mac programmer so I can't help with that but I've read a little on it so I'll proffer some thoughts. Just remember that they are purely conjecture.
       Process IDs tend to increase in number as they are assigned so the order provides at least a suggestion of when the process started. The higher the number, the more recent the process. (up to a point) Process ID 377 is rather low but not low enough to think that it had to have been started at boot. If it were a process on my machine, it would probably be one that was started just after I logged in the first time. However, you've logged out and logged back in. I think that process ID continue to increase as time goes on, even if lower number processes have died. Thus, I will conjecture that this applet did not die when you logged out. I'm going pretty far out on the limb at this point so I should probably quit but I'll add one more. If the applet didn't quit when you logged out, it may have lost the privilege of communicating with your user processes that started after you logged in the second time.
       I'm not sufficiently knowledgeable about Mac programming to know how to test the last hypothesis above but I can suggest something that may give you a little extra information. At this point, you may have rebooted again so the process numbers may have changed but I trust that you can look at your error message and discover the current process ID of this applet. Do this before and after logging out and logging back in. If the process ID doesn't change, it probably didn't quit when you logged out. If it is still 377, the following command will tell you something about this process:
    ps -xwwo user,pid,ppid,pgid,pri,state,start,%cpu,%mem,command -p 377
    The seventh column gives you the approximate time that the process was started. If that predates the logout then that would be further confirmation that it didn't quit when you logged out. The third column is the process ID of the parent process. If the applet doesn't die at logout but the parent process ID changes after logout then that would support my hypothesis that the failure of the applet to quit at logout is the problem. However, it's not a necessary condition for this conjecture as many applications are offspring of the windowserver and I don't think that dies at logout.
       Even stronger support of my hypothesis could be obtained with a simple experiment. Deliberately kill the applet and then logout and log back in. If that WatchPaths job then functions correctly then that would pretty much prove my conjecture.
       Of course this all depends on my guess that this applet is started when you login. However in any case, I still think that the applet is the problem so I would certainly test its behavior with respect to loggin out and logging back in. If the applet only has a problem in conjunction with Launchd, it will be difficult isolate the problem, especially given the lack of documentation of Launchd. I don't know how much information you want to divulge about this applet but an understanding of its lifecycle will be necessary in order for us to be able to say much more. It would be useful to know how it is started and whether or not it stops after the WatchPaths job ends. Naturally it's important to know whether it dies when you logout.
       I hope this helps a little. This sounds like an interesting project and a clever use of WatchPaths. I certainly hope that you're able to work this out.
    Gary
    ~~~~
       Coming together is a beginning;
          keeping together is progress;
             working together is success.

  • The processing of Group Policy failed. Windows attempted to read the file...

    Hello all-
    I am currently trying to configure group policy (specifically folder redirects) from a new Windows Server 2008 in my home... the server acts as both an AD DS and file server for 4 client computers, all running Windows Vista Ultimate.
    Here are the steps I am currently taking:
    I create a new Group Policy called All Users and Computers and apply it to the All Users and Computers OU, which contains exactly what it says (all users and computers in the domain).
    I verify that a new folder was created in \\<FQDN>\sysvol\<FQDN>\Policies.  The new folder created is named {6479C8E0-3134-4B4F-B047-7ADD51684684}
    I change the GPO Enforced setting to Enforced.
    I attempt to use the gpupdate command to see if the group policy can be updated successfully.  In a command prompt, I type gpupdate <enter>.  I receive the message 'Updating Policy...' then after about 15 seconds the message 'User Policy update has completed successfully.'
    I keep the cmd window open.  After about 10 seconds another message apperas which says "Computer policy could not be updated successfully.  The following errors were encountered: The processing of Group Policy failed.  Windows attempted to read the file \\<FQDN>\sysvol\<FQDN>\Policies\{6AC1786C-016F-11D2-945F-00C04Fb984F9}\gpt.ini from a domain controller and was not successful.  Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    To diagnose the failure, review the event log or invoke gpmc.msc to access information about Group Policy results."
    I confirm that the error code is #3 using the Event Log, "The system cannot find the file specificed"
    Of course the system cannot find the file specified because the folder does not exist in the sysvol folder. I am wondering why Windows is trying to read from this location when it does not exist, and is not the new group policy I created!  I have no other group policies linked or enforced to any other OU/Domain/etc.  Any help resolving this issue would be greatly appreciated.

    Hello all and thanks for the help.  First a few things:
    I understand that the DC should not be running RRAS, but this a simple server being used in aa home environment by 4 users and getting another server just for RRAS would be overkill.
    Secondly, I currently have it so that while the router is handling DHCP, I have reserved a fixed IP for the server, so it always has 192.168.1.100.  If I were to use the server as the DHCP, what would my hardware configuration have to look like?  I currently have the router plugged into the ISP modem, and then server plugged into the router.  All other clients connect to the router wirelessly.
    Here's the dcdiag output.  I tried dcdiag /fix but to no avail.
    Directory Server Diagnosis
    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine KELLERDCFS, is a Directory Server.
    Home Server = KELLERDCFS
    * Connecting to directory service on server KELLERDCFS.
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=keller-pa,DC=net,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=keller-pa,DC=net,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    * Identifying all NC cross-refs.
    * Found 1 DC(s). Testing 1 of them.
    Done gathering initial info.
    Doing initial required tests
    Testing server: Default-First-Site-Name\KELLERDCFS
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    Determining IP4 connectivity
    Determining IP6 connectivity
    * Active Directory RPC Services Check
    ......................... KELLERDCFS passed test Connectivity
    Doing primary tests
    Testing server: Default-First-Site-Name\KELLERDCFS
    Starting test: Advertising
    The DC KELLERDCFS is advertising itself as a DC and having a DS.
    The DC KELLERDCFS is advertising as an LDAP server
    The DC KELLERDCFS is advertising as having a writeable directory
    The DC KELLERDCFS is advertising as a Key Distribution Center
    The DC KELLERDCFS is advertising as a time server
    The DS KELLERDCFS is advertising as a GC.
    ......................... KELLERDCFS passed test Advertising
    Test omitted by user request: CheckSecurityError
    Test omitted by user request: CutoffServers
    Starting test: FrsEvent
    * The File Replication Service Event log test
    Skip the test because the event log File Replication Service does not exist.
    ......................... KELLERDCFS passed test FrsEvent
    Starting test: DFSREvent
    The DFS Replication Event Log.
    ......................... KELLERDCFS passed test DFSREvent
    Starting test: SysVolCheck
    * The File Replication Service SYSVOL ready test
    File Replication Service's SYSVOL is ready
    ......................... KELLERDCFS passed test SysVolCheck
    Starting test: KccEvent
    * The KCC Event log test
    Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
    ......................... KELLERDCFS passed test KccEvent
    Starting test: KnowsOfRoleHolders
    Role Schema Owner = CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    Role Domain Owner = CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    Role PDC Owner = CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    Role Rid Owner = CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    Role Infrastructure Update Owner = CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    ......................... KELLERDCFS passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    Checking machine account for DC KELLERDCFS on DC KELLERDCFS.
    * SPN found :LDAP/KELLERDCFS.keller-pa.net/keller-pa.net
    * SPN found :LDAP/KELLERDCFS.keller-pa.net
    * SPN found :LDAP/KELLERDCFS
    * SPN found :LDAP/KELLERDCFS.keller-pa.net/KELLER-PA
    * SPN found :LDAP/42268b36-801f-4a6d-b162-34f3b01e04bb._msdcs.keller-pa.net
    * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/42268b36-801f-4a6d-b162-34f3b01e04bb/keller-pa.net
    * SPN found :HOST/KELLERDCFS.keller-pa.net/keller-pa.net
    * SPN found :HOST/KELLERDCFS.keller-pa.net
    * SPN found :HOST/KELLERDCFS
    * SPN found :HOST/KELLERDCFS.keller-pa.net/KELLER-PA
    * SPN found :GC/KELLERDCFS.keller-pa.net/keller-pa.net
    ......................... KELLERDCFS passed test MachineAccount
    Starting test: NCSecDesc
    * Security Permissions check for all NC's on DC KELLERDCFS.
    * Security Permissions Check for
    DC=ForestDnsZones,DC=keller-pa,DC=net
    (NDNC,Version 3)
    * Security Permissions Check for
    DC=DomainDnsZones,DC=keller-pa,DC=net
    (NDNC,Version 3)
    * Security Permissions Check for
    CN=Schema,CN=Configuration,DC=keller-pa,DC=net
    (Schema,Version 3)
    * Security Permissions Check for
    CN=Configuration,DC=keller-pa,DC=net
    (Configuration,Version 3)
    * Security Permissions Check for
    DC=keller-pa,DC=net
    (Domain,Version 3)
    ......................... KELLERDCFS passed test NCSecDesc
    Starting test: NetLogons
    * Network Logons Privileges Check
    Verified share \\KELLERDCFS\netlogon
    Verified share \\KELLERDCFS\sysvol
    ......................... KELLERDCFS passed test NetLogons
    Starting test: ObjectsReplicated
    KELLERDCFS is in domain DC=keller-pa,DC=net
    Checking for CN=KELLERDCFS,OU=Domain Controllers,DC=keller-pa,DC=net in domain DC=keller-pa,DC=net on 1 servers
    Object is up-to-date on all servers.
    Checking for CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net in domain CN=Configuration,DC=keller-pa,DC=net on 1 servers
    Object is up-to-date on all servers.
    ......................... KELLERDCFS passed test ObjectsReplicated
    Test omitted by user request: OutboundSecureChannels
    Starting test: Replications
    * Replications Check
    * Replication Latency Check
    ......................... KELLERDCFS passed test Replications
    Starting test: RidManager
    * Available RID Pool for the Domain is 1600 to 1073741823
    * KELLERDCFS.keller-pa.net is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 1100 to 1599
    * rIDPreviousAllocationPool is 1100 to 1599
    * rIDNextRID: 1111
    ......................... KELLERDCFS passed test RidManager
    Starting test: Services
    * Checking Service: EventSystem
    * Checking Service: RpcSs
    * Checking Service: NTDS
    * Checking Service: DnsCache
    * Checking Service: DFSR
    * Checking Service: IsmServ
    * Checking Service: kdc
    * Checking Service: SamSs
    * Checking Service: LanmanServer
    * Checking Service: LanmanWorkstation
    * Checking Service: w32time
    * Checking Service: NETLOGON
    ......................... KELLERDCFS passed test Services
    Starting test: SystemLog
    * The System Event log test
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 17:53:59
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 17:59:02
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:04:04
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:09:06
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:14:08
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:19:10
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:24:12
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:29:15
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:34:17
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:39:19
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    An Error Event occurred. EventID: 0x00000422
    Time Generated: 07/07/2009 18:49:23
    Event String:
    The processing of Group Policy failed. Windows attempted to read the file \\keller-pa.net\sysvol\keller-pa.net\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    ......................... KELLERDCFS failed test SystemLog
    Test omitted by user request: Topology
    Test omitted by user request: VerifyEnterpriseReferences
    Starting test: VerifyReferences
    The system object reference (serverReference)
    CN=KELLERDCFS,OU=Domain Controllers,DC=keller-pa,DC=net and backlink
    on
    CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    are correct.
    The system object reference (serverReferenceBL)
    CN=KELLERDCFS,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=keller-pa,DC=net
    and backlink on
    CN=NTDS Settings,CN=KELLERDCFS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=keller-pa,DC=net
    are correct.
    ......................... KELLERDCFS passed test VerifyReferences
    Test omitted by user request: VerifyReplicas
    Test omitted by user request: DNS
    Test omitted by user request: DNS
    Running partition tests on : ForestDnsZones
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test
    CrossRefValidation
    Running partition tests on : DomainDnsZones
    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test
    CrossRefValidation
    Running partition tests on : Schema
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Running partition tests on : Configuration
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation
    Running partition tests on : keller-pa
    Starting test: CheckSDRefDom
    ......................... keller-pa passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... keller-pa passed test CrossRefValidation
    Running enterprise tests on : keller-pa.net
    Test omitted by user request: DNS
    Test omitted by user request: DNS
    Starting test: LocatorCheck
    GC Name: \\KELLERDCFS.keller-pa.net
    Locator Flags: 0xe00013fd
    PDC Name: \\KELLERDCFS.keller-pa.net
    Locator Flags: 0xe00013fd
    Time Server Name: \\KELLERDCFS.keller-pa.net
    Locator Flags: 0xe00013fd
    Preferred Time Server Name: \\KELLERDCFS.keller-pa.net
    Locator Flags: 0xe00013fd
    KDC Name: \\KELLERDCFS.keller-pa.net
    Locator Flags: 0xe00013fd
    ......................... keller-pa.net passed test LocatorCheck
    Starting test: Intersite
    Skipping site Default-First-Site-Name, this site is outside the scope
    provided by the command line arguments provided.
    ......................... keller-pa.net passed test Intersite
    Here's the nslookup from Vista client:
    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.
    C:\Users\Andrew>nslookup KELLERDCFS
    Server: UnKnown
    Address: 192.168.1.100
    Name: KELLERDCFS.keller-pa.net
    Addresses: 192.168.1.150
    192.168.1.100
    C:\Users\Andrew>
    Thanks again!

  • Processing of Group Policy failed - User Policy - Windows 7

    OP:
    http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/191f1ee1-a551-446b-9808-ff66a952bb25
    When running a gpupdate I get the following message:
    Updating Policy...
    User policy could not be updated successfully. The following errors were encount
    ered:
    The processing of Group Policy failed. Windows could not authenticate to the Act
    ive Directory service on a domain controller. (LDAP Bind function call failed).
    Look in the details tab for error code and description.
    Computer Policy update has completed successfully.
    To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
    rom the command line to access information about Group Policy results.
    This only happens on one computer under a certain account; other accounts work fine and the problem account works fine on other computers. Therefore the problem is located on the Windows 7 computer.
    I have tracked it down to an LDAP error code 49. 
    I tried the MS sollution (http://technet.microsoft.com/en-us/library/cc727283(v=ws.10).aspx) but the credentials are sound.
    I can also connect to the DC with LDP.exe fine. 
    Here are the diagnostic read outs (GPResult was too long to post):
    Log Name:      System
    Source:        Microsoft-Windows-GroupPolicy
    Date:          2/29/2012 1:56:09 PM
    Event ID:      1006
    Task Category: None
    Level:         Error
    Keywords:     
    User:          Domain\UserAccount
    Computer:      Win7-ComputerA.FQDomain
    Description:
    The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
        <EventID>1006</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>1</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2012-02-29T19:56:09.732842600Z" />
        <EventRecordID>32458</EventRecordID>
        <Correlation ActivityID="{CECE6DDC-E7CC-4563-8109-E62382F645D4}" />
        <Execution ProcessID="984" ThreadID="3688" />
        <Channel>System</Channel>
        <Computer>Win7-ComputerA.FQDomain</Computer>
        <Security UserID="S-1-5-21-416373151-1271962822-2142307910-40105" />
      </System>
      <EventData>
        <Data Name="SupportInfo1">1</Data>
        <Data Name="SupportInfo2">5012</Data>
        <Data Name="ProcessingMode">0</Data>
        <Data Name="ProcessingTimeInMilliseconds">1326</Data>
        <Data Name="ErrorCode">49</Data>
        <Data Name="ErrorDescription">Invalid Credentials</Data>
        <Data Name="DCName">
        </Data>
      </EventData>
    </Event>
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : WIN7-ComputerA
       Primary Dns Suffix  . . . . . . . : FQDomain
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : FQDomain
                                           ParentDomain
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : FQDomain
       Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
    on
       Physical Address. . . . . . . . . : 00-21-CC-5F-CF-DF
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 216.71.244.28(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Wednesday, February 29, 2012 12:38:25 PM
       Lease Expires . . . . . . . . . . : Thursday, March 01, 2012 12:38:24 PM
       Default Gateway . . . . . . . . . : 216.71.244.1
       DHCP Server . . . . . . . . . . . : 216.71.244.2
       DNS Servers . . . . . . . . . . . : 216.71.244.2
                                           216.71.240.120
                                           216.71.240.132
       Primary WINS Server . . . . . . . : 216.71.244.2
       Secondary WINS Server . . . . . . : 216.71.240.130
                                           216.71.240.122
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Wireless LAN adapter Wireless Network Connection:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) WiFi Link 1000 BGN
       Physical Address. . . . . . . . . : 8C-A9-82-B0-67-E8
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Hi,
    It sound like port blocking issue, Seems your client system connecting 216.71.240.x DNS Servers as a logon server and which seems on different subnet
    as per subnet mask, So there must be a router or firewall in between and so it might be Active directory ports are being blocked.
    So first for testing purpose just remove other
    216.71.240.x DNS
    servers from TCP/IP configuration and clear dns cache
    ipconfig/flushdns
    and restart the system. check if it works.
    or run this command on DC
    dcdiag /test:dns
    and share the error report.
    Cheers!
    Sanjay

  • Processing of Group Policy Failed - Single DC error 1058

    I have been getting the error every 5 mins for awhile: 
    The processing of Group Policy failed. Windows attempted to read the file \\xx.company\sysvol\xxx.company\Policies\{0000000-2323-2222-2222-333333}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this
    event is resolved. This issue may be transient and could be caused by one or more of the following: 
    a) Name Resolution/Network Connectivity to the current domain controller. 
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). 
    c) The Distributed File System (DFS) client has been disabled.
    So - this is a single DC 2008R2.  It started (I think) back when I joined another server on the domain and did a DCPromo to help build some redundancy.  DFS was/is not enabled, do I need to set this up to resolve this?
    User are able to login and policy are working, I only see this error on the DC, but other than the error everything seems to be working fine.  I can access the share \\xx.company\sysvol\xxx.company\Policies\ and see it from all systems on the domain.
    I looked for the Burflags to see if that would help but since there is no DFS there was nothing in the registry. 
    So at this point, I removed the secondary server via DCpromo, going back to just the 1 server DC but I still get the error.  DNS works. When I do a DCDiag everything looks ok except the SysVol - I get about 10 of these
          Starting test: SystemLog
             An error event occurred.  EventID: 0x00000422
                Time Generated: 03/17/2015   14:49:41
                Event String:
                The processing of Group Policy failed... blah blah - same as above. 
    I looked at this link because of the combination of the 2 errors - Error 1058 and 00422 but its suggesting Authoritative restore, but I don't have the replication.  
    Now I am wondering if there is a left over connection somewhere in the system that doesn't know that there isn't another DC on the network?
    So - any suggestions?  Thanks in advance.

    Hi,
    >>Now I am wondering if there is a left over connection somewhere in the system that doesn't know that there isn't another DC on the network?
    Did we clean up the metadata of the removed domain controller? If not, we can follow the article below to do this.
    Clean Up Server Metadata
    https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx
    Besides, on the existing domain controller, check Applications and Services Logs\FRS or DFSR logs in Event Viewer. If the issue persists, we can follow the method below to do an authoritative restore for Sysvol.
    If we use FRS to replicate Sysvol, we can try to follow the article below to an authoritative restore for Sysvol.
    Using the BurFlags registry key to reinitialize File Replication Service replica sets
    https://support.microsoft.com/en-us/kb/290762
    If we use DFSR to replicate Sysvol, we can try to follow the article below to do an authoritative restore for Sysvol.
    How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
    https://support.microsoft.com/en-us/kb/2218556
    Best regards,
    Frank Shen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • The processing of Group Policy failed because of lack of network connectivity to a domain controller

    We are setting up a new AD environment  with one AD/DC running DNS services,  and a secondary DNS server configured with secondary zone. The problem is that none of the machines in the the domain are getting GPO.
    When I run a gpupdate /force from a machine, I get the following output:
    "Updating Policy...
    User Policy update has completed successfully.
    Computer policy could not be updated successfully. The following errors were enc
    ountered:
    The processing of Group Policy failed because of lack of network connectivity to
     a domain controller. This may be a transient condition. A success message would
     be generated once the machine gets connected to the domain controller and Group
     Policy has succesfully processed. If you do not see a success message for sever
    al hours, then contact your administrator.
    To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
    rom the command line to access information about Group Policy results."
    While the system event log outputs the following:
    "The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy
    has succesfully processed. If you do not see a success message for several hours, then contact your administrator." 
    All the machines that were joined to the domain are able to resolve in forward and reverse lookups, ping the DC and ping each other so  I dont understand how the error can be resolved.
    Here are few things I have tried:
    1. I came across this KB which checked ok for me: http://support.microsoft.com/kb/241515
    2. Made a copy of the default GPO, applied to a OU with one machine, and made sure to remove any GPO links from above
    3. Enabled the following  two local Group policies on a test member:
    GP slow link detection
    Startup policy processing wait time
    4. Modified firewall to allow everything on both member and DC
    5. Verified DSN logs, SRV records, access to sysvol ( added authenticated users to sysvol)
    I have yet to figure out the reason for this issue. Has anyone seen anything like this before?

    1. I checked the NIC, it only has one IP. and I followed your article. I set the primary DNS to its own IP and the secondary DNS to the loopback ip
    2. This is a new DC and DNS server. I dont have old records yet. I also check the DNS event logs. No errors
    3. I made sure the member server is pointing only to the only DC/DNS server
    4. Here is the output from the dcdiag....  everything passed except, the Netlogons part. I'm not sure what means or how to fix it yet:
          Starting test: NetLogons
             * Warning BUILTIN\Administrators did not have the "Access this
             computer
             "*   from network" right.
             [hostname] An net use or LsaPolicy operation failed with error
             1, Incorrect function..
             ......................... hostname failed test NetLogons
    Complete output:
    > hostname
    Server:  hostname.domain.local
    Address:  X.X.X.95
    > ^C
    C:\Windows\system32>
    C:\Windows\system32>nslookup
    > set type=all
    >
    >
    >
    > _ldap._tcp.dc._msdcs.domainname
    _ldap._tcp.dc._msdcs.domain.local SRV service location:
              priority       = 0
              weight         = 100
              port           = 389
              svr hostname   = hostname.domain.local
    hostname.domain.local      internet address = X.X.X.95
    > ^C
    C:\Windows\system32>cd ..
    C:\Windows>cd SYSVOL
    C:\Windows\SYSVOL>cd sysvol
    C:\Windows\SYSVOL\sysvol>dir
     Volume in drive C has no label.
     Volume Serial Number is F624-CDB2
     Directory of C:\Windows\SYSVOL\sysvol
    10/29/2014  08:25 PM    <DIR>          .
    10/29/2014  08:25 PM    <DIR>          ..
    10/29/2014  08:25 PM    <JUNCTION>     domain.local [C:\Windows\SYSVOL\domain]
                   0 File(s)              0 bytes
                   3 Dir(s)  63,971,037,184 bytes free
    C:\Windows\SYSVOL\sysvol>dcdiag
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = hostname
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\hostname
          Starting test: Connectivity
             ......................... hostname passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\hostname
          Starting test: Advertising
             ......................... hostname passed test Advertising
          Starting test: FrsEvent
             ......................... hostname passed test FrsEvent
          Starting test: DFSREvent
             ......................... hostname passed test DFSREvent
          Starting test: SysVolCheck
             ......................... hostname passed test SysVolCheck
          Starting test: KccEvent
             ......................... hostname passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... hostname passed test
             KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... hostname passed test MachineAccount
          Starting test: NCSecDesc
             ......................... hostname passed test NCSecDesc
          Starting test: NetLogons
             * Warning BUILTIN\Administrators did not have the "Access this
             computer
             "*   from network" right.
             [hostname] An net use or LsaPolicy operation failed with error
             1, Incorrect function..
             ......................... hostname failed test NetLogons
          Starting test: ObjectsReplicated
             ......................... hostname passed test
             ObjectsReplicated
          Starting test: Replications
             ......................... hostname passed test Replications
          Starting test: RidManager
             ......................... hostname passed test RidManager
          Starting test: Services
             ......................... hostname passed test Services
          Starting test: SystemLog
             A warning event occurred.  EventID: 0x000003F6
                Time Generated: 03/04/2015   18:23:06
                Event String:
                Name resolution for the name ctldl.windowsupdate.com timed out after
     none of the configured DNS servers responded.
             ......................... hostname passed test SystemLog
          Starting test: VerifyReferences
             ......................... hostname passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : emcdsm
          Starting test: CheckSDRefDom
             ......................... emcdsm passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... emcdsm passed test CrossRefValidation
       Running enterprise tests on : domain.local
          Starting test: LocatorCheck
             ......................... domain.local passed test LocatorCheck
          Starting test: Intersite
             ......................... domain.local passed test Intersite
    C:\Windows\SYSVOL\sysvol>

  • [SOLVED] Boot fails with "ata4: SRST failed (errno = -16)"

    I have desktop that has four disks. They have similar three partitions sitting on RAID.
    /boot and swap are on RAID1
    / is on RAID5.
    This worked well until a couple of weeks ago I noticed I couldn't connect to it via SSH. I went onsite and the desktop was humming but I couldn't get picture on the screen and alt + sysrq + REISUB did nothing. I shut it down by pressing power button and started it again. It gave me following errors:
    ata4: SRST failed (errno = -16)
    After a while there was
    reset failed, give up
    I restarted the machine and went to BIOS. There was only two of four disks visible. I shut the computer down, removed the power cord and then plugged it back in. This time BIOS showed all the disks there. I tried to boot up Arch and got the following.
    Booting the kernel.
    running early hook [udev]
    running hook [udev]
    Triggering uevents
    mounting '/dev/md3' on real root # md3 is the RAID 5 device containing root
    mount: you must specify the filesystem type
    You are now being dropped into an emergency shell.
    sh: can't access tty; job control turned off
    After that I tried to chroot from USB installation disk. First I check the RAID devices and see that in md1 (/boot) all seems to be ok. In md2 (swap) half of the partitions are missing. I'm not sure how to interpret the last one.
    cat /proc/mdstat
    Personalities : [raid1]
    md1: active raid1 sdd1[3] sdb1[1] sda1[0] sdc1[2]
    1048564 block super 1.0 [4/4] [UUUU]
    md2: active raid1 sdb2[1] sda2[0]
    2096116 block super 1.2 [4/2] [UU__]
    md3: inactive sdb3[1](S) sda3[0](S) sdd3[4](S) sdc3[2](S)
    608169984 block super 1.2
    unused devices: <none>
    I remove those devices and try to recreate them. md1 says it starts with four drives. md2 starts with 2 driver out of 4. And then the last one.
    mdadm --assemble /dev/md3 /dev/sd[a-d]3
    mdadm: /dev/md3 assembled from 2 drives - not enough to start the array.
    Has anyone any idea where did the two partitions go? I ran SMART-tests to all four drives in long mode and all of them passed the tests.
    I use GPT partitioning table, UEFI and Syslinux if it matters.
    Last edited by Tha-Fox (2013-02-23 01:35:05)

    I just booted to chroot environment and checked that all the partitions show up all right. Below is output of one disk and all the four disks give similar info.
    gdisk -l /dev/sdd
    GPT fdisk (gdisk) version 0.8.6
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sdd: 312581808 sectors, 149.1 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 8B9EBB89-366E-4C81-8916-F61CB08273DB
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 312581774
    Partitions wil be aligned on 2-sector boundaries
    Total free space is 2203245 sectors (1.1 GiB)
    Number Start (sector) End (sector) Size Code Name
    1 34 2097185 1024.0 MiB FD00 Linux RAID
    2 2097186 6291489 2.0 GiB FD00 Linux RAID
    3 6291490 310378529 145.0 GiB FD00 Linux RAID

  • Java.lang.Process.exec()

    I have read a article about the "java.lang.Process.exec()" (url:http://www.javaworld.com/javaworld/jw-12-2000/jw-1229-traps.html)
    Having some questions with the example in it.
    The example code:
    import java.util.*;
    import java.io.*;
    public class BadExecJavac
        public static void main(String args[])
            try
                Runtime rt = Runtime.getRuntime();
                Process proc = rt.exec("javac");
                //int exitVal = proc.exitValue();
                int exitVal = proc.waitFor();
                System.out.println("Process exitValue: " + exitVal);
            } catch (Throwable t)
                t.printStackTrace();
    }The process can run but never complete.
    Why? Just because when invoke the javac.exe without any argument,it will product a set of usage statements that describe how to run the program and the meaning of all the available program options.So the process is in deadlock.
    The question is, when i change the exec("javac") to exec("javac a.java"), in which the "a.java" is not exist, so the jvm should product error:
    error: cannot read: a.java
    1 error
    But after i changed the code and run the class, at this time the process can run and complete.
    The two codes both product some statements,but why the first one never complete,but the second did. Why?

    import java.util.*;
    import java.io.*;
    public class A
        public static void main(String args[])
            try
                Runtime rt = Runtime.getRuntime();
                Process proc = rt.exec("javac");
                InputStream is = proc.getErrorStream();
                int i=0;
                while ((i = is.read()) != -1)
                    System.out.print((char)i);
                // int exitVal = proc.exitValue();
                // int exitVal = proc.waitFor();
                // System.out.println("Process exitValue: " + exitVal);
            } catch (Throwable t)
                t.printStackTrace();
    }usng this modification, i could see some error messages.
    because exec(cmd) executes the command in a separate process, it will not display the results on the current console. If you want see the results, you should use getInputStream() and getErrorStream().
    good luch ^^

Maybe you are looking for