The SNMP Service is ignoring extension agent dll %1 because it is missing or misconfigured.

Details
Product: Windows Operating System
Event ID: 1102
Source: SNMP
Version: 5.2
Symbolic Name: SNMP_EVENT_INVALID_EXTENSION_AGENT_DLL
Message: The SNMP Service is ignoring extension agent dll %1 because it is missing or misconfigured.
   
Explanation

The Simple Network Management Protocol (SNMP) service cannot load the extension agent named in the message.

   
User Action

To configure the registry so that the SNMP extension agent is loaded when the SNMP service starts, try the following:

  • Verify that the SNMP extension agent is configured correctly. For details, please see Article 128729, “HOWTO: Add an SNMP Extension Agent to the NT Registry” in the Microsoft Knowledge Base.
  • Restore SNMP to a clean, known state by removing and then reinstalling it.Warning: Before removing SNMP, be sure to back up the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters.

Related:

Could not allocate a new page for database ‘%.*ls’ because of insufficient disk space in filegroup ‘%.*ls’. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Details
Product: SQL Server
Event ID: 1101
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: NOALLOCPG
Message: Could not allocate a new page for database ‘%.*ls’ because of insufficient disk space in filegroup ‘%.*ls’. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
   
Explanation

No disk space available in a filegroup.

   
User Action

The following actions may make space available in the filegroup.

  • Turn on AUTOGROW.

  • Add more files to the file group.

  • Free up disk space by dropping unnecessary indexes or tables in the filegroup.

Related:

The SNMP Service has started successfully.

Details
Product: Windows Operating System
Event ID: 1001
Source: SNMP
Version: 5.2
Symbolic Name: SNMP_EVENT_SERVICE_STARTED
Message: The SNMP Service has started successfully.
   
Explanation

The Simple Network Management Protocol (SNMP) service is now running.

   
User Action

No user action is required.

Related:

The SNMP Service is ignoring extension agent key %1 because it is missing or misconfigured.

Details
Product: Windows Operating System
Event ID: 1101
Source: SNMP
Version: 5.2
Symbolic Name: SNMP_EVENT_INVALID_EXTENSION_AGENT_KEY
Message: The SNMP Service is ignoring extension agent key %1 because it is missing or misconfigured.
   
Explanation

The Simple Network Management Protocol (SNMP) service cannot load an extension agent because the extension agent is no longer installed on the computer or is incorrectly configured in the registry key.

   
User Action

To correct the problem, try the following:

Warning: This procedure changes system registry settings. If Registry Editor is used incorrectly, serious system problems can occur, and the operating system may need to be reinstalled.

  • For examples of correct extension agent entries, see Article 128729, “HOWTO: Add an SNMP Extension Agent to the NT Registry” in the Microsoft Knowledge Base.
  • If the extension agent is no longer installed on the computer, use Registry Editor to delete its entry from the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents.
  • If the extension agent is installed on the computer and there is an entry for it in the registry key, ensure that the entry is configured correctly.
  • If none of these solutions correct the problem, restore the SNMP installation to a clean, known state by removing and then re-installing SNMP.Warning: Before removing SNMP, be sure to back up the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters.

Related:

User “%1” attempted to modify a custom prompt for auto attendant “%2”. The operation failed. Make sure that the UM administrator is a member of the local Administrators group and Exchange Organization Administrators, and has at least read and write permissions to the UM prompt publishing point shared folder. More information follows: “%3”.

Details
Product: Exchange
Event ID: 1099
Source: MSExchange Unified Messaging
Version: 8.0
Symbolic Name: AutoAttendantCustomPromptUploadFailed
Message: User “%1” attempted to modify a custom prompt for auto attendant “%2”. The operation failed. Make sure that the UM administrator is a member of the local Administrators group and Exchange Organization Administrators, and has at least read and write permissions to the UM prompt publishing point shared folder. More information follows: “%3”.
   
Explanation

This Warning event indicates that the Copy-UMCustomPrompt cmdlet did not copy the custom audio prompt file to the Unified Messaging (UM) prompt publishing point. The prompt file (*.wav) is used by the auto attendant to provide the audio for a given custom prompt when it is required by the Telephone User Interface (TUI). The prompt publishing point is a shared folder structure that is created on the first computer in your Exchange 2007 organization that has the Unified Messaging server role installed. The prompt publishing point is used to distribute UM custom prompts to other UM servers in the Exchange 2007 organization. This event may be caused when the UM administrator who performs the operation does not have the correct access permissions to the UM prompt publishing point.

   
User Action

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

  • Make sure that the UM administrator is a member of Administrators or Exchange Organization Administrators.

  • Make sure that the UM prompt publishing point has the following minimum permissions:

    • File-Level Permissions

    •    Administrators: Full Control

    •    Exchange Organization Administrators: Full Control

    •    Exchange Servers: Full Control

    •    System: Full Control

    •    Creator Owner: Special Permissions (Full Control on subfolders and files only)

    • Sharing Permissions:

    •    Administrators: Full Control

    •    Exchange Organization Administrators: Full Control

    •    Exchange Servers: Full Control

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:

During intersite replication the directory replication agent (DRA) received an invalid update-replica message for partition %1 from the directory at %2. This directory does not have a replica of that partition. Try running the consistency checker on this Windows Domain Controller and on Windows Domain Controller %2.

Details
Product: Windows Operating System
Event ID: 1098
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_DRA_MAIL_UPDREP_BADNC
Message: During intersite replication the directory replication agent (DRA) received an invalid update-replica message for partition %1 from the directory at %2. This directory does not have a replica of that partition. Try running the consistency checker on this Windows Domain Controller and on Windows Domain Controller %2.
   
Explanation

Internal event: During intersite replication, Active Directory received an update-replica message that is not valid for the specified directory partition. The local domain controller does not contain this directory partition.

   
User Action

Try running the Knowledge Consistency Checker (KCC) on both Windows Domain Controllers.

Related:

During intersite replication, the directory replication agent (DRA) received an invalid update-replica message for naming context {object name} from the directory at {object name}. This Site Replication service is not replicating from that directory.

Details
Product: Exchange
Event ID: 1098
Source: MSExchangeSRS
Version: 6.0
Component: Site Replication Service
Symbolic Name: DIRLOG_DRA_MAIL_UPDREP_BADSRC
Message: During intersite replication, the directory replication agent (DRA) received an invalid update-replica message for naming context {object name} from the directory at {object name}. This Site Replication service is not replicating from that directory.
   
Explanation
The foreign directory is not in the source directory replicas list for the named object. All updates from that directory will be ignored.The directory replication agent (DRA) is responsible for synchronizing with the other directories and accepting directory updates.
   
User Action
Verify that there are no inconsistencies in the replication connectors. Examples include moving a bridgehead or deleting a replication connector that exists between the two directories.

Related:

Error {error code} occurred while cleaning up background folder {folder id} on database “{name}”.

Details
Product: Exchange
Event ID: 1097
Source: MSExchangeIS Public Store
Version: 6.0
Component: Information Store
Symbolic Name: msgidFolderCleanupError
Message: Error {error code} occurred while cleaning up background folder {folder id} on database “{name}”.
   
Explanation
An inconsistency exists between Active Directory and Information Store.
   
User Action
Contact Microsoft Product Support Services.

Related:

Windows cannot load the locally stored profile. Contact your network administrator. DETAIL – %s

Details
Product: Windows Operating System
Event ID: 1000
Source: Userenv
Version: 5.0
Symbolic Name: IDS_FAILED_LOAD_LOCAL
Message: Windows cannot load the locally stored profile. Contact your network administrator. DETAIL – %s
   
Explanation

This error can occur if the user profile registry hive gets corrupted or if permissions are set incorrectly on the profile folders.

   
User Action

To troubleshoot this problem, try the following:

  • Review the Event Viewer logs and look for related profile (userenv) events to obtain additional details about this error.
  • If the user profile registry hive (ntuser.dat, the user profile registry hive’s supporting file) is corrupted, replace ntuser.dat with a backup copy of this file.
  • Verify that permissions are set correctly on the local user profile folders. On a computer that has a clean installation (with no previous operating system) of Windows Server 2003, Windows XP, or Windows 2000 operating system, the user profile folders are stored in system_drive\Documents and Settings; for example, C:\Documents and Settings.

Related: