Group policy error 1006

-

 hello!

after servers unexpectly shutdown have problem gp on 1 server.

source: grouppolicy
event id: 1006
error code: 81

"the processing of group policy failed. windows not authenticate active directory service on domain controller. (ldap bind function call failed). in details tab error code , description."

3 servers windows server 2008. forest/domain level - 2008. no dcdiag errors.

gpsvc.log

gpsvc(2d4.a9c) 12:32:49:519 refreshpolicyforprincipal: entering bmachine = 0, sid = null, options: 1, dwtimeout = 600000,
gpsvc(204.f10) 12:32:49:534 gpothread: background forced refresh requested, calling getusernameex refresh dn cache returned 0x0
gpsvc(204.13d0) 12:32:49:534 gplockpolicysection: sid = (null), dwtimeout = 30000, dwflags = 65538
gpsvc(204.f10) 12:32:49:534 nlaquerynetsignatures returned 1 networks
gpsvc(204.13d0) 12:32:49:534 lockpolicysection called user <machine>
gpsvc(204.f10) 12:32:49:534 there no domain compartment
gpsvc(204.13d0) 12:32:49:534 sync lock called
gpsvc(204.13d0) 12:32:49:534 reader lock got immediately. m_creadersinlock : 1
gpsvc(204.13d0) 12:32:49:534 lock taken successfully
gpsvc(204.13d0) 12:32:49:534 unlockpolicysection called user <machine>
gpsvc(204.13d0) 12:32:49:534 found caller in readerhavinglock list. removing it...
gpsvc(204.13d0) 12:32:49:534 setting lock state notlocked
gpsvc(204.13d0) 12:32:49:534 unlocked successfully
gpsvc(204.f10) 12:32:49:534 getdomaincontrollerconnectioninfo: enabling bandwidth estimate.
gpsvc(204.13d0) 12:32:49:550 getdomaincontrollerconnectioninfo: enabling bandwidth estimate.
gpsvc(204.f10) 12:32:51:562 started bandwidth estimation successfully
gpsvc(204.13d0) 12:32:51:562 started bandwidth estimation successfully
gpsvc(204.f10) 12:32:51:562 getdomaincontrollerconnectioninfo: getting ldap handles.
gpsvc(204.13d0) 12:32:51:562 getdomaincontrollerconnectioninfo: getting ldap handles.
gpsvc(204.f10) 12:32:51:562 getldaphandle:  getting ldap handle host: dc01.domain.corp in domain: domain.corp.
gpsvc(204.13d0) 12:32:51:562 getldaphandle:  getting ldap handle host: dc01.domain.corp in domain: domain.corp.
gpsvc(204.f10) 12:32:51:562 getldaphandle:  server connection established.
gpsvc(204.13d0) 12:32:51:562 getldaphandle:  server connection established.
gpsvc(204.f10) 12:32:51:562 getldaphandle:  binding using kerberos.
gpsvc(204.13d0) 12:32:52:561 getldaphandle:  ldap_bind_s failed = <81>
gpsvc(204.f10) 12:32:52:561 getdomaincontrollerconnectioninfo: getldaphandle failed 0x3a. try forcefully discover dc.
gpsvc(204.13d0) 12:32:52:561 getdomaincontrollerconnectioninfo: getldaphandle failed 0x3a. try forcefully discover dc.
gpsvc(204.f10) 12:32:52:561 getdomaincontrollerconnectioninfo: enabling bandwidth estimate.
gpsvc(204.13d0) 12:32:52:561 getdomaincontrollerconnectioninfo: enabling bandwidth estimate.
gpsvc(204.f10) 12:32:54:573 started bandwidth estimation successfully
gpsvc(204.13d0) 12:32:54:573 started bandwidth estimation successfully
gpsvc(204.f10) 12:32:54:573 getdomaincontrollerconnectioninfo: getting ldap handles.
gpsvc(204.13d0) 12:32:54:573 getdomaincontrollerconnectioninfo: getting ldap handles.
gpsvc(204.f10) 12:32:54:573 getldaphandle:  getting ldap handle host: dc01.domain.corp in domain: domain.corp.
gpsvc(204.13d0) 12:32:54:573 getldaphandle:  getting ldap handle host: dc01.domain.corp in domain: domain.corp.
gpsvc(204.f10) 12:32:54:573 getldaphandle:  server connection established.
gpsvc(204.13d0) 12:32:54:573 getldaphandle:  server connection established.
gpsvc(204.f10) 12:32:54:573 getldaphandle:  binding using kerberos.
gpsvc(204.f10) 12:32:55:572 getldaphandle:  ldap_bind_s failed = <81>
gpsvc(204.13d0) 12:32:55:572 getdomaincontrollerconnectioninfo: getldaphandles failed after force rediscovery 0x3a
gpsvc(204.f10) 12:32:55:572 getdomaincontrollerconnectioninfo: getldaphandles failed after force rediscovery 0x3a
gpsvc(204.13d0) 12:32:55:572 processgpos: getdomaincontrollerconnectioninfo failed 58.
gpsvc(204.f10) 12:32:55:572 processgpos: getdomaincontrollerconnectioninfo failed 58.
gpsvc(204.13d0) 12:32:55:572 processgpos: no wmi logging done in policy cycle.
gpsvc(204.f10) 12:32:55:572 processgpos: no wmi logging done in policy cycle.
gpsvc(204.13d0) 12:32:55:572 processgpos: processing failed error 58.
gpsvc(204.f10) 12:32:55:572 processgpos: processing failed error 58.
gpsvc(204.13d0) 12:32:55:572 application complete bconnectivityfailure = 1.
gpsvc(204.f10) 12:32:55:572 application complete bconnectivityfailure = 1.
gpsvc(204.13d0) 12:32:55:572 registering connectivity notification.
gpsvc(204.f10) 12:32:55:572 registering connectivity notification.
gpsvc(204.13d0) 12:32:55:572 registerfornotificationifrequired returned status = 0x32 continuing...
gpsvc(204.f10) 12:32:55:572 registerfornotificationifrequired returned status = 0x32 continuing...
gpsvc(204.13d0) 12:32:55:572 signalling 1 refresh policy callers
gpsvc(204.f10) 12:32:55:572 signalling 1 refresh policy callers
gpsvc(2d4.a9c) 12:32:55:572 exiting refreshpolicyforprincipal status = 0
gpsvc(2d4.1734) 12:32:55:572 exiting refreshpolicyforprincipal status = 0
gpsvc(204.f10) 12:32:55:572 sync lock called
gpsvc(204.f10) 12:32:55:572 writer lock got immediately.
gpsvc(204.f10) 12:32:55:572 lock taken successfully
gpsvc(204.f10) 12:32:55:587 unlockpolicysection called user <machine>
gpsvc(204.f10) 12:32:55:587 unlocked successfully

mcsa2003, mcse2003, mcts:vista

hi,

this error may caused corrupt file or dns entry. please check dns server , make sure dc registered correctly.

if cannot find error in dns server, please collect following information research.

the mps reporting tool utilized gather detailed information regarding systems current configuration. data collected assist fault isolation.

a . please download mps reporting tool (mpsrpt_pfe.exe) following link:
(http://www.microsoft.com/downloads/details.aspx?familyid=00ad0eac-720f-4441-9ef6-ea9f657b5c2f&displaylang=en)

please note: link may truncated when read e-mail. sure include text between '(' , ')' when navigating download location.

b . right click mpsrpt_pfe.exe , select run administrator run tool, , see command window start up.

c . please type y message of <include msinfo32 report? (defaults y in 15 seconds)[y,n]?

d . when tool done see explorer window opening %systemroot%\mpsreports\setup\reports\cab folder , containing <computername>mpsreports.cab file. after collecting, please use windows live skydrive (http://www.skydrive.live.com/) upload file , give me download address.

thanks.

this posting provided "as is" no warranties, , confers no rights.


Windows Server  >  Directory Services



Comments

  1. Randy Turner9 October 2024 at 02:16

    What a fantastic perspective! I appreciate the positivity and motivation you bring to your writing. Looking forward to more!

    ReplyDelete
  2. Vikashpatel22 December 2024 at 22:17

    Group Policy error 1006 often occurs due to network connectivity issues or authentication failures. Using services like DVHosting can help ensure stable and secure network infrastructure to prevent such errors.

    ReplyDelete

Post a Comment

Popular posts from this blog

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authenticati...
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema ...
Read more

Failed to setup initiator portal. Error status is given in the dump data.

-
hi team, server configured boot san  after booting  facing issue windows server 2008 r2 system logs continuously generating iscsi port error event id 5 failed setup initiator portal. error status given in dump data. eventdata \device\raidport1 000004000100000000000000050000c0000000000000000000000000000000000000000000000000070200c0 binary data: in words 0000: 00040000 00000001 00000000 c0000005 0008: 00000000 00000000 00000000 00000000 0010: 00000000 00000000 c0000207 in bytes 0000: 00 00 04 00 01 00 00 00 ........ 0008: 00 00 00 00 05 00 00 c0 .......À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 07 02 00 c0 ...À hi, please read through article below troubleshoot issue: error event id 5 logged in system log on computer uses iscsi software initiator connect iscsi target device http://suppo...
Read more