Process %1 (PID=%2). Could not find file %3. This is normal if the file has never been generated. Otherwise, make sure this file has read permission for the “Exchange Servers” group.

Details
Product: Exchange
Event ID: 1022
Source: MSExchangeFDS
Version: 8.0
Symbolic Name: SourceManifestNotAvailable
Message: Process %1 (PID=%2). Could not find file %3. This is normal if the file has never been generated. Otherwise, make sure this file has read permission for the “Exchange Servers” group.
   
Explanation

This Warning event indicates that the Microsoft Exchange File Distribution service did not find an offline address book manifest file (oab.xml). The File Distribution service requires this file to synchronize offline address book files between Exchange servers that have the Mailbox server role and Client Access (CAS) server roles installed.

This event may occur if either of the following conditions is true:

  • The offline address book manifest file (oab.xml) has not been generated yet. This file is generated when the corresponding offline address book is updated. By default, every offline address book is updated daily at 5:00 A.M.

  • The Exchange Servers group does not have Read permission on this manifest file (oab.xml).

    Note   If the corresponding offline address book update has yet to run, you may ignore this event. Otherwise, see User Action.

    Note   The offline address book GUID that follows the ExchangeOAB file share in the event description indicates the corresponding offline address book.

   
User Action

To resolve this Warning event, follow one or more of these steps:

  • Regenerate the manifest file by using the following procedure:

    • Note the offline address book GUID that follows the ExchangeOAB file share in the event description.

    • Run the following Exchange Management Shell command:

      Update-OfflineAddressBook -Identity <offline address book identifier>

      Note   In this command, replace <offline address book identifier> with the GUID that you determined in step 1.

    • Restart the Microsoft Exchange File Distribution service from the Microsoft Windows Services console on the Exchange server that logged this event.

  • Make sure that Exchange Servers group has Read permission on the oab.xml file specified in the event description.

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:

Failed to delete identifier {attribute name} on key with path {path}. Error code is {error code}.

Details
Product: Exchange
Event ID: 1022
Source: MSExchangeMU
Version: 6.0
Component: Metabase Update Service
Symbolic Name: DSMBLOG_DEL_ID_FAILED
Message: Failed to delete identifier {attribute name} on key with path {path}. Error code is {error code}.
   
Explanation
The Metabase Update agent failed to delete an attribute in the Metabase. This may be a temporary error. If so, the Metabase will eventually recover from this error and the Metabase Update agent will update the Metabase properly.
   
User Action
No user action is required. If the problem persists, verify that the IIS Admin Service is running properly.For more information about the error code reference specified in the message, go to www.reskit.com.

Related:

DS lookup for user , connecting from , failed with error .

Details
Product: Exchange
Event ID: 1022
Source: POP3SVC
Version: 6.5.6940.0
Component: Microsoft Exchange POP3 Service
Message: DS lookup for user <user name>, connecting from <host name>, failed with error <error code>.
   
Explanation

This event indicates that when a POP3 client made an attempt to access a mailbox on the Exchange Server, the attempt failed because lookup of Active Directory for that user failed.

This behavior occurs because the value in the User Logon Name (Pre-Windows 2000) box does not match the value in the Mailbox Alias box.

   
User Action
  • Verify that the Mailbox Alias value and the User Logon Name (Pre-Windows 2000) value match
  • Enter the logon credentials in the format

    DomainName\LogonName\MailboxAlias when you are connecting through POP3

Related:

Anti-spam agents are enabled, but the list of internal SMTP servers is empty. If there are any MTAs between this server and the Internet, populate this list by using the Set-TransportConfig cmdlet in the Exchange Management Shell.

Details
Product: Exchange
Event ID: 1022
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: InternalSMTPServerListEmpty
Message: Anti-spam agents are enabled, but the list of internal SMTP servers is empty. If there are any MTAs between this server and the Internet, populate this list by using the Set-TransportConfig cmdlet in the Exchange Management Shell.
   
Explanation

The Warning event indicates that Microsoft Exchange Server 2007 anti-spam agents are enabled and the list of internal Simple Mail Transfer Protocol (SMTP) servers is empty.

In some organizations, the Hub Transport server role or Edge Transport server role that is running connection filtering is installed on computers that don’t process SMTP requests directly on the Internet. In this scenario, the Exchange 2007 transport server is behind another front-end SMTP server that processes inbound messages directly from the Internet. The Connection Filter agent must be able to extract the correct originating IP address from the message. To extract and evaluate the originating IP address, the Connection Filter agent must parse the Received headers from the message and compare those headers with the known SMTP server in the perimeter network.

When an RFC-compliant SMTP server receives a message, the server updates the message’s Received header with the domain name and IP address of the sender. Therefore, for each SMTP server that is between the originating sender and the Exchange 2007 transport server, the SMTP server adds an additional Received header entry.

   
User Action

To resolve this warning, you must specify all internal SMTP servers on the transport configuration object in the Active Directory directory service forest before you run connection filtering.

Specify the internal SMTP servers by using the InternalSMTPServers parameter on the Set-TransportConfig cmdlet. For more information, see Set-TransportConfig.

For more information about how to configure connection filtering see Configuring Connection Filtering.

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:

The connection between the Client Access server and Mailbox server “%1” failed. If this event is logged infrequently or only during scheduled downtime for a Mailbox server, no user action is required. If this event occurs repeatedly, check network connectivity using PING or PingPath. Also, check connectivity using the Test-ActiveSyncConnectivity cmdlet. More information: %2

Details
Product: Exchange
Event ID: 1022
Source: MSExchange ActiveSync
Version: 8.0
Symbolic Name: ConnectionFailed
Message: The connection between the Client Access server and Mailbox server “%1” failed. If this event is logged infrequently or only during scheduled downtime for a Mailbox server, no user action is required. If this event occurs repeatedly, check network connectivity using PING or PingPath. Also, check connectivity using the Test-ActiveSyncConnectivity cmdlet. More information: %2
   
Explanation

This Warning event indicates that Exchange ActiveSync has temporarily detected a connection problem between the computer that is running the Mailbox server role and the computer that is running the Client Access server role. Exchange ActiveSync will retry ActiveSync operations between the Client Access server and the Mailbox server.

This event may be logged in the following conditions:

  • If there are network connectivity issues between the Mailbox server and the Client Access server.

  • If the Mailbox server is offline for any reason.

   
User Action

To resolve this event, consider the following:

  • If this event is infrequently logged, or only during scheduled downtime for a Mailbox server, no user action is required.

  • If this event frequently occurs, do one or more of the following:

    • Check network connectivity between the Mailbox server and the Client Access server. Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

    • Use the test-ActiveSyncConnectivity task. For information about how to use this command, see test-ActiveSyncConnectivity in the Microsoft® Exchange Server 2007 Help file.

    • Review the Application log on the Mailbox server to determine the root cause of the inability of the Client Access server to connect to the Mailbox server.

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:

Logon Failure on database “%4” – Windows account %1; mailbox %2.Error: %3 Client Machine: %5 Client Process: %6 Client ProcessId: %7 Client ApplicationId: %8

Details
Product: Exchange
Event ID: 1022
Source: MSExchangeIS Mailbox Store
Version: 8.0
Symbolic Name: msgidOwnerLogonFailed
Message: Logon Failure on database “%4” – Windows account %1; mailbox %2.Error: %3
Client Machine: %5
Client Process: %6
Client ProcessId: %7
Client ApplicationId: %8
   
Explanation

The Error event indicates that there was a logon failure to the mailbox database. This error could be seen together with event 1044. Use ERROR.exe to decode the error as it could provide information about the underlying problem. For example, the error might be MAPI_E_LOGON_FAILED or ecWrongServer or MAPI_E_NO_ACCESS. The following are some of the possible conditions for the cause of the event:

  • This event could be seen during a Move Mailbox operation if a user tries to access their mailbox when it is being moved.

  • The disabled Active Directory user account associated with the mailbox in question might not have the MSExchMasterAccountSID attribute populated.

  • The domain controller that was first updated during the mailbox move differs from the domain controller that the Exchange Server uses during the user’s logon attempt.

  • The user tries to gain access to the mailbox before Active Directory replicates the information to the domain controller.

   
User Action

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

  • Do nothing. In the Move Mailbox operation, the problem will be resolved in approximately 15 minutes after a mailbox has been moved and when Active Directory replication occurs. The user will then be able to log on to their mailbox.

  • Make sure that users are not accessing their mailboxes during a Move Mailbox operation.

  • Make sure that the SELF account is listed in the permissions list for the Active Directory User Object associated with the mailbox in question.

  • Make sure that the Active Directory user accounts are enabled.

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: