Outlook Web Access was unable to initialize..A base theme could not be found. The base theme must be in a folder with the name “%1”.

Details
Product: Exchange
Event ID: 26
Source: MSExchange OWA
Version: 8.0
Symbolic Name: NoBaseTheme
Message: Outlook Web Access was unable to initialize..A base theme could not be found. The base theme must be in a folder with the name “%1”.
   
Explanation

This Error event indicates that Microsoft® Office Outlook® Web Access did not initialize because the Outlook Web Access base themes folder referenced in the event description does not exist. The base folder contains images and cascading style sheets that are used to control the default appearance of Outlook Web Access for your organization. The base folder is also used by other custom Outlook Web Access themes if they are installed. By default, the base folder is located in C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\<version> hemes\.

   
User Action

To resolve the error, replace the base folder and its contents with the files and folders that are located on the Microsoft Exchange Server 2007 DVD. By default, the base folder is located in the \Setup\ServerRoles\ClientAccess\owa\version hemes folder of the Exchange 2007 DVD.

For more information about Outlook Web Access themes, see How to Create a Theme for Outlook Web Access.

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:

This address is already in use. Binding: %1

Details
Product: Exchange
Event ID: 1001
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: AddressInUse
Message: This address is already in use. Binding: %1
   
Explanation

This Error event indicates that the specified combination of IP address and port number is being used by another process on the server.

Each Receive connector on a Microsoft Exchange Server 2007 Hub Transport server or Edge Transport server must use a unique combination of IP addresses and port numbers to listen for inbound connections from remote SMTP messaging servers.

If other SMTP messaging services are running on this server, they may be using an IP address and port number combination that conflicts with an existing Receive connector. For example, the default Receive connector on an Edge Transport server is configured to use 0.0.0.0:25. The default Receive connectors on a Hub Transport server are configured to use 0.0.0.0:25 and 0.0.0.0:587.

   
User Action

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

  • Remove or relocate any other SMTP messaging services that are running on this server.

  • Configure any other SMTP messaging services that must run on this Hub Transport server or Edge Transport server to use an IP address and port number combination that doesn’t conflict with any Receive connectors that are configured on the server.

  • Configure the Receive connectors on this Hub Transport server or Edge Transport server to use an IP address and port number combination that doesn’t conflict with any other SMTP messaging services that must run on this server.

For more information, see Receive Connectors.

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 RPC over HTTP Proxy component is not installed or is not configured correctly. Use the Windows Component Wizard to add the RPC over HTTP Proxy component to the Networking Services.

Details
Product: Exchange
Event ID: 2003
Source: MSExchange RPC Over HTTP Autoconfig
Version: 8.0
Symbolic Name: ProxyNotInstalled
Message: The RPC over HTTP Proxy component is not installed or is not configured correctly. Use the Windows Component Wizard to add the RPC over HTTP Proxy component to the Networking Services.
   
Explanation

This Error event indicates that the RPC over HTTP Proxy component of the Networking Services is not installed or is configured incorrectly. The Outlook Anywhere feature requires the RPC over HTTP Proxy component to be installed on the Exchange Client Access server. When the RPC over HTTP component is installed and the Secure Sockets Layer (SSL) certificate for the default Web site is configured appropriately, the RPC over HTTP Autoconfiguration component sets and maintains the remaining required Exchange Client Access server configuration.

   
User Action

To resolve the error, follow these steps on the Exchange Client Access server:

  1. From Add or Remove Programs, select Add/remove Windows Components.

  2. If the RPC over HTTP component of the Networking Services is not installed, use the Windows Components Wizard to add the RPC over HTTP proxy component.

    Note   After the component is installed, it may take 15 minutes before the Exchange Client Access server is fully configured for Outlook Anywhere operation.

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:

Outlook Web Access did not initialize.A forms registry file is not valid %1 Line number = %2 Position = %3. You must define a base experience or a forms registry to inherit from.The forms registry is a critical component of Outlook Web Access. If this error is not addressed, users might be unable to access the Outlook Web Access client. For more information about how to troubleshoot the forms registry, see the Help and Support Center.

Details
Product: Exchange
Event ID: 8
Source: MSExchange OWA
Version: 8.0
Symbolic Name: FormsRegistryExpectedBaseExperienceOrInheritsFrom
Message: Outlook Web Access did not initialize.A forms registry file is not valid %1 Line number = %2 Position = %3. You must define a base experience or a forms registry to inherit from.The forms registry is a critical component of Outlook Web Access. If this error is not addressed, users might be unable to access the Outlook Web Access client. For more information about how to troubleshoot the forms registry, see the Help and Support Center.
   
Explanation

This Error event indicates that a forms registry does not have a base experience. A forms registry must either define a base experience or inherit a base experience from another forms registry.

   
User Action

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

  • Open the registry that does not have a base experience and define a base experience. Or open the registry that does not have a base experience and configure it to inherit from a forms registry that has the base experience that you want.

  • If you have difficulty resolving the issue, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

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:

An unexpected MAPI error occurred. Error returned was [].

Details
Product: Exchange
Event ID: 5
Source: MSExchangeES
Version: 6.5.6940.0
Message: An unexpected MAPI error occurred. Error returned was [<error code>].
   
Explanation

This event can occur when attempting to start the Microsoft Exchange Event service. It means that the service could not be started because an unexpected error was encountered. The Error Code in the Description section of the event can be converted to a readable message using the ERROR.EXE program included on the Exchange Server CD ROM. This error code will usually provide information as to the underlying cause of the problem.

This issue can be seen if there are multiple “EventConfig_(Servername)” folders or if the “EventConfig_(ServerName)” folder is not replicated to the Exchange Server named “ServerName.”

   
User Action

Try the following steps to resolve this issue:

  • Open Exchange System Manager and check if there is more than one instance of the same EventConfig_ServerName folder. If so, rename one of the instances so that both can be deleted. If you try to delete one while a duplicate exists, you get a warning tht indicates you must rename one of the folders. Delete both instances of the EventConfig_(servername) folder. Restart the Event service. This recreates a single instance of the EventConfig_(servername).
  • Error Code 0x8000ffff indicates “catastrophic failure.” This usually occurs in mixed mode environments, where an Exchange 5.X server existed but is no longer present. In such a case, you can try to start the Event service using the 5.5 Service Account. In Exchange Server versions 2000 and later, the Exchange Server Services always start in the context of the Local System Account, unlike earlier versions where a “Service Account” was used to initialize the services.
  • If there are multiple Exchange Servers, you should see one EventConfig(ServerName) Public Folder for each ServerName. Ensure that each of those Public Folders (also referred to as System Folders) has a replica on the server it corresponds to. So, for example, EventConfig(ServerOne) should have a replica on ServerOne and EventConfig(ServerTwo) should have a replica on ServerTwo.

Related:

An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. URL=%1%2.

Details
Product: Exchange
Event ID: 1008
Source: MSExchange ActiveSync
Version: 8.0
Symbolic Name: AirSyncException
Message: An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. URL=%1%2.
   
Explanation

This Warning event indicates that an exception occurred during the Exchange ActiveSync synchronization process. The event description includes details about the root cause of the problem. The following are possible causes of this event:

  • The partnership configuration for this device was created by using computer that is running an earlier version of Microsoft® Exchange. The partnership cannot be used. This problem may occur after you upgrade a computer to Exchange Server 2007. Exchange will update the partnership on the Exchange server. After the partnership is updated, all the data configured for synchronization in the partnership will be resynchronized.

  • The partnership configuration for this device is damaged. Exchange will update the partnership on the Exchange server. After the partnership is updated, all of the data configured for synchronization in the partnership will be resynchronized.

  • A user has accessed the same item from multiple computers or mobile devices. For example, this may occur if a user tries to reply to a message on their mobile device after that device has been deleted on the user’s desktop computer that runs Microsoft Office Outlook® 2007. This will be corrected the next time that the user synchronizes their device..

  • When AirSync calls the ADSystemConfigurationSession.GetDefaultAcceptedDomain method, AirSync tries to read all accepted domains. Then, AirSync filters on the client side for the default domain. If the Exchange Server 2007 organization has more than one thousand accepted domain objects, the Active Directory directory service returns an error. Therefore, AirSync cannot synchronize successfully.

   
User Action

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

  • If this error was caused by an outdated partnership or a damaged partnership, no user action is required. Exchange will re-create a partnership with the mobile device.

  • Make sure that the user has an Exchange mailbox and that the user has been enabled for Exchange ActiveSync. For more information, How to Enable or Disable Exchange ActiveSync for a Mailbox User in the Exchange 2007 Help file.

  • Wait for the Active Directory® directory service replication to occur.

  • To resolve the issue when the Exchange Server 2007 organization has more than one thousand accepted domain objects, install Update Rollup 4 for Exchange Server 2007.

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:

Exchange – High Memory Utilization

Back pressure is a system resource monitoring feature of the Microsoft Exchange Transport service that exists on Microsoft Exchange 2013 Mailbox servers and Edge Transport servers. What this means is that the Exchange server monitors key resources, such as hard drive space and memory, and under pressure, can take action to prevent service unavailability. While this can prevent system resources from being completely exhausted, back pressure can cause service degradation.

The Exchange server tries to process existing messages before accepting any new messages and therefore introduces delivery delays. Exchange Server resource sizing is an exact science. Over time, with more users, higher email volume, and larger message sizes, environment will change over time. Therefore the initial Exchange Server sizing may be inadequate a year later.

In this scenario back pressure was avoided by actively monitoring the Exchange Server resources with Intelligent Monitoring. As shown in the figure below, the Exchange mailbox server memory utilization was increasing. Knowing that this was happening allowed the IT team to completely avoid Exchange performance issues by allocating more memory to the Exchange Server. Identifying this potential issue would not have happened without having Intelligent Monitoring in place. Intelligent Monitoring gives you access to server performance information easily and with the guidance of the PCIS team, can avert a potential Exchange service degradation issue.

Related:

Lotus Domino wiki

Learn how to use IBM Lotus Domino, contribute to its product knowledge base, and collaborate with others. Find IBM Product Documentation and Learning Center materials, including how-to videos and getting started materials, and supplemental articles written by Lotus community members.

Related: