Event ID 1080 — Group Policy Preprocessing (Active Directory)

Event ID 1080 — Group Policy Preprocessing (Active Directory)

Updated: September 21, 2007

Applies To: Windows Server 2008

Group Policy processing requires Active Directory. The Group Policy service reads and updates information stored in Active Directory. The absence of Active Directory (or a domain controller) prevents Group Policy from applying to the computer or user.

Event Details

Product: Windows Operating System
ID: 1080
Source: Microsoft-Windows-GroupPolicy
Version: 6.0
Symbolic Name: gpEvent_FAILED_OU_SEARCH
Message: The processing of Group Policy failed. Windows could not search the Active Directory organization unit hierarchy. View the event details for more information.

Resolve
Search Active Directory

The Group Policy service failed when querying Active Directory.

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:

  1. Open the Start menu. Click All Programs and then click Accessories.
  2. Click Command Prompt.
  3. In the command prompt window, type gpupdate and then press ENTER.
  4. 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

Related Management Information

Group Policy Preprocessing (Active Directory)

Group Policy Infrastructure

Related:

The Unified Messaging (UM) server failed to process messages for user “%1” during the call with ID “%2” because the user has exceeded their mailbox quota.

Details
Product: Exchange
Event ID: 1080
Source: MSExchange Unified Messaging
Version: 08.01.0106.000
Symbolic Name: QuotaExceededFailedSubmit
Message: The Unified Messaging (UM) server failed to process messages for user “%1” during the call with ID “%2” because the user has exceeded their mailbox quota.
   
Explanation

This Warning event indicates that the computer that has the Unified Messaging server role installed was not able to accept any new voice or fax messages intended for the user specified in the event description. If this occurs, the Unified Messaging (UM) server delivers a response to the user who tried to send the voice message, and then disconnects the call. For example, the UM server response may be: “Sorry, the user’s mailbox is full. Please call back later.” This event may occur if the Exchange mailbox for the user specified in the event description exceeds the configured storage limit. Storage limits for a user’s mailbox can be configured at the user level or at the Exchange database level.

   
User Action

To resolve this warning, do one or more of the following:

  • Increase or remove the storage limit defined at the Exchange database level or at the mailbox level. For more information configuring storage limits, see How to Configure Database Limits and Properties and How to Configure Storage Quotas for a Mailbox.

  • Archive or delete messages from the user’s mailbox to reduce the size of the mailbox to less than the storage limit. To obtain mailbox information such as the size of the mailbox, the number of messages it contains, and the last time it was accessed, use the Get-MailboxStatistics command. For more information, see Get-Mailbox Statistics.

Note  If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Unable to recover the database “” because error occurred after a restore operation.

Details
Product: Exchange
Event ID: 1080
Source: MSExchangeIS
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: Unable to recover the database “<name>” because error <error code> occurred after a restore operation. <text>
   
Explanation

Unable to recover the database because an error occurred after a restore operation.

   
User Action

Look for events in the application event log with the category ESE. Search the Microsoft Support Knowledge Base for these errors.

Related:

Unable to recover the database “%3” because error %1 occurred after a restore operation. %2

Details
Product: Exchange
Event ID: 1080
Source: MSExchangeIS
Version: 6.5.7596.0
Message: Unable to recover the database “%3” because error %1 occurred after a restore operation. %2
   
Explanation

Microsoft® Exchange Server cannot recover the database because an error occurred after a restore operation.

   
User Action

To resolve this error, do one or more of the following:

Related:

Windows cannot search for Organizational Unit hierarchy. (%1). Group Policy processing aborted.

Details
Product: Windows Operating System
Event ID: 1080
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_FAILED_OU_SEARCH
Message: Windows cannot search for Organizational Unit hierarchy. (%1). Group Policy processing aborted.
   
Explanation

A network connectivity or network configuration problem is preventing Group Policy settings from being applied. Group Policy processing for the computer or user has failed and will continue to fail until this error is resolved.

   
User Action

To troubleshoot this problem, try one or all of the following:

  • Review the event description to obtain additional details regarding why the machine has an account problem.
  • In the Event Viewer, click System, and then look for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
  • At the command prompt, type netdiag, and look for any errors. Typically, these errors have to be resolved before Group Policy processing can continue.For more information about using NetDiag, see article Q265706, “DCDiag and NetDiag Facilitate Join and DC Creation,” in the Microsoft Knowledge Base.
  • At the command prompt, type gpupdate, and then check the Event Viewer to see if the Userenv events are logged again.
  • To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com represents the fully qualified DNS name of your domain.
  • Verify that you can access the domain controller by using tools such as Active Directory Users and Computers.
  • Check whether other computers on your network are having the same problem.
  • If this is a forest trust scenario, ensure that the forest for the user account is currently available and can be contacted from the computer where policy processing failed.
  • Use verbose logging to debug this error. The log file explains the specific error.For more information about enabling userenv logging, see article 221833 , “How to Enable User Environment Debug Logging in Retail Builds of Windows” at the Microsoft Knowledge Base.

If none of the previous user actions identified the problem, follow the steps in “Troubleshooting Group Policy in Windows Server 2003” at the Microsoft Web site.

Related: