Event Viewer Error 1030
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Group Policy processing error. Event ID 1030 Windows Server > Group Policy Question 0 Sign event viewer error 4201 in to vote We are getting event ID 1030, error code 58 appearing event viewer error 10016 on all domain joined computers, including domain controllers. Event Description:
The processing of Group Policy failed. Windows attempted toEvent Viewer Error 10
retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers
Event Viewer Error 55
joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. Event Detail: System - Provider [ Name] Microsoft-Windows-GroupPolicy [ Guid] {AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9} EventID 1030 Version 0 Level 2 Task 0 Opcode 1 event viewer error 7001 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2012-06-12T00:19:31.734258300Z EventRecordID 191165 - Correlation [ ActivityID] {464CBB72-656C-4632-A2AA-31E797F0A8DE} - Execution [ ProcessID] 908 [ ThreadID] 2368 Channel System Computer DC1.domain.local - Security [ UserID] S-1-5-18 - EventData SupportInfo1 1 SupportInfo2 2070 ProcessingMode 0 ProcessingTimeInMilliseconds 515 ErrorCode 58 ErrorDescription The specified server cannot perform the requested operation. DCName \\DC1.domain.local I've followed http://technet.microsoft.com/en-us/library/7e940882-33b7-43db-b097-f3752c84f67fand everything is looking good up to event ID 5311 and then Group Policy processing fails. I've run GPLOGVIEW -m and it shows processing fail for the currently logged on user as well as the computer. The computer in question (that I want to resolve first) is one of three domain controllers in the AD domain. It is hosting DNS, and IP settings are pointing to itself (127.0.0.1) for DNS. I have tried/checked: pointing at another DNS (DC), running ipconfig /flushdns and nbtstat -R with no improvement.DCDIAG/test:dns comes back clean on all DCs.I can ping by host name all DCs.I can ping the domain name and a DC responds.DNS SRV records have been checked and
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=1030&EvtSrc=Userenv&LCID=1033 areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
Event ID 1058 & 1030 So... I have this customer... and for quite a while now (unsure how long - I suspect a year or more) they have been having challenges enumerating & applying group http://www.darylhunter.me/blog/2011/06/solved-group-policy-gptini-event-id-1058-1030.html policies. Event ID 1030/1058 would appear in their Application Logs... and it was no fun... I did the usual stuff. I asked Dr. Google of course. I tried permissions. I tried re-shares. I checked FRS and DFS https://community.spiceworks.com/windows_event/show/616-microsoft-windows-grouppolicy-1030 and many other TLAs along the way. Nothing. From the 2x domain controllers, I could access the \\server\sysvol\domain\policies stuff just fine. I could also access the \\domain\sysvol\domain\policies stuff. No problems. But, from domain joined servers/computers, it was event viewer a no go. I could get to \\server\sysvol\domain but it was empty. Same with \\domain\sysvol\domain - empty. Finally, I dropped to a command prompt and found this Do you see it? No, I don't mean my horrible "coloring job" - I mean the Junction pointing to C:\Winnt\path... Really? WINNT? What decade is this? Anyway, without trying to figure out who/what/why, I simply removed that junction point and re-added it with "mklink" like so Then, I event viewer error did a "gpupdate /force" to force a Group Policy Update. Then went to check the logs again... BAM! I still got it... Hope this helps. I found many "me too" people with issues, and many different forums suggesting many different fixes. I thought I would add my own fix to the mix. Woah, that rhymed. G'nite. Posted by DWHunter on 06/18/2011 at 01:41 AM in Active Directory, Networking, Server 2008 | Permalink Digg This | Save to del.icio.us | | Comments You can follow this conversation by subscribing to the comment feed for this post. My friend. I had the same problem and was resolved after remove all groups of the user. Then i went puting the groups one-by-one until find the problem group. Posted by: Ricardo | 08/04/2012 at 09:55 PM Hi Daryl, my JUNCTION path was pointing to "domain.local". 1/ Would I still need to make that change since WINNT wasn't part of the path? 2/ If so, would you be able to email me the command to removed and re-add the JUNCTION entry to my gmail account at bostonbajan@gmail.com thank you in advance. Posted by: Tony | 02/27/2013 at 11:56 AM The comments to this entry are closed. About Twitter Updates follow me on Twitter Subscribe to this blog's feed Categories Active Directory Blackberry Cisco Current Affairs E
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 1030 (Error) Source: Microsoft-Windows-GroupPolicy How important is this event? (5 votes) 1 2 3 4 5 not important very important Description The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. Resolve Query for Group Policy objects This issue occurs when there is an absence of authenticated connectivity from the computer to the domain controller. Use the Group Policy Operational log and Group Policy troubleshooting procedures (http://go.microsoft.com/fwlink/?LinkId=74139) to further diagnose the problem. Verify Group Policy applies during computer startup and user logon. Afterward, Group Policy applies every 90 to 120 minutes. Events appearing in the event log may not reflect the most current state of Group Policy. Therefore, you should always refresh Group Policy to determine if Group Policy is working correctly. To refresh Group Policy on a specific computer: Open the Start menu. Click All Programs and then click Accessories. Click Command Prompt. In the command prompt window, type gpupdate and then press ENTER. When the gpupdate command completes, open the Event Viewer. Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs: 1500 1501 1502 1503 The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows w