Tag: Exchange 08.01.0106.000

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.

PCIS Support Team Leave a comment
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:

The Unified Messaging-enabled user “%1” is not configured to receive fax messages. The fax message that originated from phone number “%2”, destined for extension “%3”, was terminated. To resolve this issue, use the Exchange Management Console or the Set-UMMailbox cmdlet to enable the user to receive incoming fax messages.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1033
Source: MSExchange Unified Messaging
Version: 08.01.0106.000
Symbolic Name: UMUserNotConfiguredForFax
Message: The Unified Messaging-enabled user “%1” is not configured to receive fax messages. The fax message that originated from phone number “%2”, destined for extension “%3”, was terminated. To resolve this issue, use the Exchange Management Console or the Set-UMMailbox cmdlet to enable the user to receive incoming fax messages.
   
Explanation

This Warning event indicates that an incoming fax message destined for the user specified in the event description was discarded. This event may occur when the user account is not configured to receive any fax messages.
   
User Action

To resolve this warning, modify the Unified Messaging (UM) settings for the UM-enabled user so that the user can receive incoming faxes:

  • Use the Exchange Management Console to let users receive faxes:

    1. In the console root of the Exchange Management Console, expand the Recipient Configuration node.

    2. In the results pane, right-click the user, and then click Properties.

    3. On the Mailbox Features tab, right-click Unified Messaging, and then click Properties.

    4. Select Allow faxes to be received, and then click OK.

  • Use the Set-UMDialPlan cmdlet to let users receive faxes.

    For example, run the following command: Set-UMMailbox -Identity haochen@contoso.com -FaxEnabled:$true, where haochen@contoso.com is the SMTP address of the user you want to enable to receive faxes.

For more information about this setting, see the following Exchange 2007 Help topics:

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:

Process %1 (PID=%2). Failed to read from metabase. Metabase object %3 can not be found. OAB synchronization suspended.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1014
Source: MSExchangeFDS
Version: 08.01.0106.000
Symbolic Name: MetabaseOperationFailedExistsObject
Message: Process %1 (PID=%2). Failed to read from metabase. Metabase object %3 can not be found. OAB synchronization suspended.
   
Explanation

This Error event indicates that the Microsoft File Distribution service could not find one or more offline address book objects in the metabase. The metabase contains configuration information about the offline address book virtual directory that links to the offline address book objects. The File Distribution service requires offline address book virtual directory information to distribute offline address book files.

This event may occur because of corrupted metabase or configuration problems in offline address book virtual directory.
   
User Action

To resolve this error, follow these steps.

  • Open the Internet Information Services (IIS) Manager console.

  • Expand the Web Sites container and then expand Default Web Site.

  • Make sure that the Default Web Site container has the OAB virtual directory. If the OAB virtual directory does not exist, you can create a new virtual directory using New-OABVirtualDirectory Exchange Management Shell command.

You may have to re-associate existing offline address books with the new OAB virtual directory. This process is also referred to as enabling Web-based distribution.

  • Review the Application event log for related events. These related events may indicate a corrupted metabase. If the metabase is corrupted, you must restore the metabase. For more information, see Working with the Metabase (IIS 6.0) on Microsoft Windows Server 2003 TechCenter.

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:

Process %1 (PID=%2). Active Directory contains invalid configuration object, validation error is “%3”. Will wait for %4 seconds and retry.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1011
Source: MSExchangeFDS
Version: 08.01.0106.000
Symbolic Name: InvalidADObject
Message: Process %1 (PID=%2). Active Directory contains invalid configuration object, validation error is “%3”. Will wait for %4 seconds and retry.
   
Explanation

This Warning event indicates that Microsoft Exchange File Distribution service found an invalid configuration object in the Active Directory directory service. The File Distribution service must read the configuration data from Active Directory to distribute offline address book and custom Unified Messaging prompts.

This event may occur because of Active Directory schema violations.
   
User Action

If this Warning event frequently occurs, follow these steps:

  1. Use the following Exchange Management Shell cmdlet to increase the diagnostic logging level on the General counter of the MSExchangeFDS performance object to the High setting:

    Set-EventLogLevel MSExchangeFDS\General -Level High

    Note   For detailed information about how to change diagnostic logging levels, see How to Change Logging Levels for Exchange Processes.

  2. Review other related Error and Warning events in the Application log. These related events may help you determine the root cause of this warning.

  3. Use the following Exchange Management Shell cmdlet to set the diagnostic logging level on the General counter of the MSExchangeFDS performance object back to the default Lowest setting:

    Set-EventLogLevel MSExchangeFDS\General -Level Lowest

    Important   After you have completed troubleshooting this issue, you should return logging to the default level to avoid filling your event logs.

This Warning event may be ignored if it occurred during an Active Directory schema upgrade.

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:

Process %1 (PID=%2). Unhandled exception occured in worker thread %3. Exception message: %4 Current synchronization task is aborted.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1007
Source: MSExchangeFDS
Version: 08.01.0106.000
Symbolic Name: UnhandledExceptionInWorkerThread
Message: Process %1 (PID=%2). Unhandled exception occured in worker thread %3. Exception message: %4 Current synchronization task is aborted.
   
Explanation

This Error event indicates that the Microsoft Exchange File Distribution service did not finish the file synchronization task because of an error. The File Distribution service is used to distribute offline address books and custom Unified Messaging prompts. This event may occur for various reasons.
   
User Action

To determine the root cause of this Warning event, follow these steps:

  1. Use the following Exchange Management Shell cmdlet to increase the diagnostic logging level on the General counter of the MSExchangeFDS performance object to the High setting:

    Set-EventLogLevel MSExchangeFDS\General -Level High

    Note   For detailed information about increasing logging, see How to Change Logging Levels for Exchange Processes.

  2. Review other related Error and Warning events in the Application log. These related events may help you determine the root cause of this error.

  3. Use the following Exchange Management Shell cmdlet to set the diagnostic logging level on the General counter of the MSExchangeFDS performance object back to the default Lowest setting:

    Set-EventLogLevel MSExchangeFDS\General -Level Lowest

    Important   After you have completed troubleshooting this issue, you should always return logging to the default level to avoid filling your event logs.

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:

Process %1 (PID=%2). Temporarily unable to connect to Active Directory to read configuration data for object %3 (%4). Will wait for %5 seconds and retry.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1003
Source: MSExchangeFDS
Version: 08.01.0106.000
Symbolic Name: ADUnavailable
Message: Process %1 (PID=%2). Temporarily unable to connect to Active Directory to read configuration data for object %3 (%4). Will wait for %5 seconds and retry.
   
Explanation

This Warning event indicates that there is no suitable Active Directory directory service server available to read the configuration data for the object specified in the event description. The Microsoft Exchange File Distribution service must read the configuration data from Active Directory to distribute offline address book and custom Unified Messaging prompts.

This event may occur because of intermittent network issues.
   
User Action

If this Warning event frequently occurs, follow these steps:

  • Use the Ping or PathPing command-line tools to test basic connectivity with the domain controller. 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.

  • Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange Server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see the Microsoft Windows Server TechCenter article, Dcdiag Overview.

  • Review other related events in the Application log and System log for Warning events and Error events. These related events may provide more information about the root cause of this Warning event.

This Warning event may be ignored if occurred during known network issues.

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:

%1 (%2) %3Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error %4.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 413
Source: ESE
Version: 08.01.0106.000
Symbolic Name: NEW_LOG_ERROR_ID
Message: %1 (%2) %3Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error %4.
   
Explanation

This Warning event indicates that a new log file could not be created because the database cannot write to the log file drive.

The event may be logged if the drive is read-only, out of disk space, configured incorrectly, or corrupted. The cause depends on the error number in the Description section of the event. The most common error codes for event 413 are listed below.

  • Error -1032 = 0xfffffbf8 = 4294966264 = Jet_errFileAccessDenied = Cannot access file – the file is locked or in use. Another process has locked the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access.

  • Error -1811 = 0xfffff8ed = Jet_errFileNotFound = File not found. The following are possible causes for this error:

    • The current log file (such as E00.log) may have a mismatching signature between the log and the database.

    • The checkpoint file may be corrupted, or the log drive itself may have failed.

    • The current log file may have been deleted by antivirus software running on the server.

    • There may have been problems creating the temp log file for the storage group (such as e00tmp.log ). For example, the temp log file itself may become corrupted.

  • Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = disk I/O error. The -1022 error is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. The controller software or firmware may be out of date. This issue may also occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.
   
User Action

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

  • Check the integrity of the file system.

  • Check the System log for related entries.

  • Review and change the access permissions properties, and then note the disk space available.

  • Review the disk and log file to which you are trying to write.

  • For error -1811, ensure that the antivirus software is not running against the Exchange store, the Site Replication Service (SRS) database directories. Ensure that the log file drive has not run out of space.

  • For error -1032, change the permissions on the folders that contain the information store files to the default permissions. Configure the flat file backup and antivirus software to not scan the Exchange store subdirectories. Use Exchange-aware online backup and antivirus software.

  • For error -1022, ensure that the drive for the Exchange store files is accessible and that the path for the Exchange store files is specified correctly. If it is, run chkdsk /f /r. If the Chkdsk tool does not resolve the issue, examine the permissions on the Exchange Server folder structure. Ensure that System has full control of Exchange Server (install path for Exchange) and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any file-level antivirus software running on the Exchange server.  Check the System log for I/O or drive errors near the time of the 413 event. Check and correct the path for the check file (such as E00.chk).

After correcting the root cause, if the database is inconsistent, restore from online backup. If there is no valid backup, you can restore the database to consistency using the hard repair (/p) functionality of the Eseutil utility. Run isinteg -fix until all fixes are removed. Mount the database and use Move Mailbox to move to a new, blank database. Before doing this, you should always back up all Exchange store files in a storage group (*.log files, *.edb files and *.stm files).

For information about ESE error -1022, see Microsoft Knowledge Base article 314917

Understanding and analyzing -1018, -1019, and -1022 Exchange database errors.

For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

For information about properly configuring your antivirus software, see Microsoft Knowledge Base article 328841 Exchange and antivirus software.

Related: