Microsoft Fix it BLOG

Set a delay for forwarding connector state changes and server changes (DMON info) in Exchange 2000 Server

SMTP / Routing Group connector state changes cause needless connector state toggling in Exchange 2000 Server

Problem description

A Simple Mail Transport Protocol/Routing Group (SMTP/RG) connector may go into a "down" state temporarily, and then change within a minute to an "up" state after Advanced Queuing (AQ) retries the connector and determines that the SMTP/RG service on the target server is responding. This issue can occur if an SMTP/RG server on the other side does not close the connection properly. When a connector is in a down state, AQ flags the connector to indicate that it is in an error state. This type of connector state toggling can occur many times in an hour.

Solution Information

Delay the forwarding of connector state changes and server changes (DMON info).

Enable update to permit the caching of incoming SMTP messages as IPM.Note in Exchange Server 2003

Update to permit the caching of incoming SMTP messages as IPM.Note in Exchange Server 2003

Problem description

When you send Simple Mail Transfer Protocol (SMTP) mail to a Microsoft Exchange 2000 Server or a Microsoft Exchange Server 2003 public folder, the message class is IPM.Post.

There is an update that you can use to configure the setting of the PR_MESSAGE_CLASS attribute of SMTP messages that are sent to public folders as IPM.Note instead of as IPM.Post.

Solution Information

After you install the update, the message class of incoming messages to public folders may be changed to IPM.Note (instead of IPM.Post). You can configure this new setting by creating the "Incoming defaults to IPM.Note" registry value.

"Server Error in '/OMA' Application" Error Message When You View the Outlook Mobile Access Web Site

XCCC: "Server Error in '/OMA' Application" Error Message When You View the Outlook Mobile Access Web Site

Problem description

When you try to view the Microsoft Outlook Mobile Access Web site on a server after you install Exchange Server 2003 on that server, you receive an error message:

Server Error in '/OMA' Application.
Access to the path "Drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\4707b1f2\a6dd9810" is denied.

Description: An unhandled exception occurred during the execution of the current Web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UnauthorizedAccessException: Access to the path "Drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\4707b1f2\a6dd9810" is denied. ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

Solution Information

To resolve this problem, reset the ASP.NET ACLs.

Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers

Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers

Problem description

Windows Vista cannot obtain an IP address when connected to a router or other device that is configured as a Dynamic Host Configuration Protocol (DHCP) server is configured on the network and the router or the other device does not support the DHCP BROADCAST flag.

Solution Information

Disable the DHCP BROADCAST flag in Windows Vista.

You receive an "Error 1606" error message when you try to install or remove a Microsoft program

You receive an "Error 1606" error message when you try to install or remove a Microsoft program

Problem description

When you try to install or remove any one of the following products, you may receive an error message that resembles the following:

Error 1606: Could Not Access Network Location

• Microsoft Digital Image Pro 9
• Microsoft Excel 2002
• Microsoft MapPoint 2002
• Microsoft Money 2005
• Microsoft Office 2003
• Microsoft Office Access 2003
• Microsoft Office PowerPoint 2003
• Microsoft Office Outlook 2003
• Microsoft Office Publisher 2003
• Microsoft Office XP
• Microsoft FrontPage 2002
• Microsoft PowerPoint 2002
• Microsoft Streets & Trips 2003
• Microsoft Picture It! Photo 2002
• Microsoft Office 2000
• Microsoft Outlook 2002
• Microsoft Word 2002
• Microsoft Access 2002
• Microsoft Excel 2000
• Microsoft FrontPage 2000
• Microsoft PowerPoint 2000
• Microsoft Word 2000

Automatically configure Outlook to a specific global catalog server or the closest global catalog server

How to configure Outlook to a specific global catalog server or to the closest global catalog server

Problem description

You may notice excessive network traffic when Microsoft Outlook attempts to contact the global catalog server.

Solution Information

Configure Outlook to identify and use the closest global catalog server.

Messages remain in an Exchange Server outbound queue until a non-delivery report is generated when you send e-mail to a remote domain

Messages remain in an outbound queue until a non-delivery report is generated when you send e-mail to a remote domain

Problem description

When you send e-mail messages to certain external domains, they may remain in an outbound queue on the Microsoft Exchange Server 2003 or Microsoft Exchange 2000 Server computer until a non-delivery report (NDR) is generated.

Solution Information

Configure the XEXCH50 Registry sub-key or configure the SMTP Connector.

Force Outlook 2007 or Outlook 2003 to resolve proxy addresses and custom properties in Cached Exchange Mode

How to force Outlook 2007 or Outlook 2003 to resolve proxy addresses and custom properties in Cached Exchange Mode

When you use Microsoft Office Outlook 2007 or Microsoft Office Outlook 2003 in Cached Exchange Mode, Outlook verifies and resolves the names of e-mail recipients with the Offline Address Book. The process of resolving e-mail addresses with similar fields, such as the DisplayName, is called Ambiguous Name Resolution (ANR).

Enable Security tab on all Exchange objects in System Manager

XADM: Security tab not available on all objects in System Manager

In Exchange System Manager, the Security tab is displayed in an object's properties. However by default, the Security tab is displayed only on the following objects:

• Address Lists
• Global Address Lists
• Databases (Mailbox stores and Public Folder stores)
• Top Level Public Folder Hierarchy

This solution will help you display the Security tab on all Exchange objects.

Enable hotfix to reduce CPU usage by the Exchange System Attendant service on offline address list servers in a hosting environment

CPU usage by the Exchange System Attendant service on offline address list servers in a hosting environment increases to 50 percent

In a hosting environment where Microsoft Exchange Server 2003 computers are configured as offline address list servers, you may find that CPU usage by the Microsoft Exchange System Attendant service (Mad.exe) on each of the servers increases to 50 percent. You experience these symptoms even after you restart each server.
For example, you may experience these symptoms in a hosting environment where you have 10,000 offline address lists and 10 Exchange Server 2003 computers that are configured as offline address list servers.

Enable additional Exchange information store logging

How to enable additional Exchange information store logging

You may need to enable additional Microsoft Windows Performance Monitor information store logging for troubleshooting purposes on an Exchange Server.

PowerShell commands for the Exchange 2007 Edge server role do not work as expected after you uninstall an update rollup or an interim update on the Edge server

PowerShell commands for the Exchange 2007 Edge server role do not work as expected after you uninstall an update rollup or an interim update on the Edge server

You uninstall an update rollup or an interim update on a Microsoft Exchange Server 2007 Edge server. Then, PowerShell commands that are used for the Edge server role do not work as expected.

Services for Exchange Server cannot start automatically after you install Exchange Server 2007 and Exchange Server 2010 on a global catalog server

Services for Exchange Server 2007 or Exchange Server 2010 cannot start automatically after you install Exchange Server 2007 and Exchange Server 2010 on a global catalog server

When you install Microsoft Exchange Server 2007 or install Microsoft Exchange server 2010 on a global catalog server, Exchange Server services cannot start. However, you can start other services manually. Servers in this configuration may take a long time to shut down.

A meeting update message or a meeting cancellation message from an Exchange 2003 user is not delivered to an Exchange 2007 user

A meeting update message or a meeting cancellation message from an Exchange 2003 user is not delivered to an Exchange 2007 user

A Microsoft Exchange Server 2003 organization and a Microsoft Exchange Server 2007 organization exchange communications by using SMTP. An Exchange 2003 user organizes a meeting and then sends a meeting request to an Exchange 2007 user. The Exchange 2007 user accepts the meeting request.  The meeting organizer uses Microsoft Office Outlook to send a meeting update message or a meeting cancellation message to the Exchange 2007 user.

In this scenario, the meeting update message or the meeting cancellation message is not delivered to the Exchange 2007 user. Instead, the meeting update message or the meeting cancellation message goes into the SMTP retry queue. If an administrator tries to open the message in the Exchange System Manager console, the administrator may receive the following error message:

Unable to open for delivery

Error messages when you try to connect Outlook 2007 to Exchange Server: "The action cannot be completed" or "Your Microsoft Exchange Server is unavailable" or "Cannot start Microsoft Office Outlook"

Error messages when you try to connect Outlook 2007 to Exchange Server: "The action cannot be completed" or "Your Microsoft Exchange Server is unavailable" or "Cannot start Microsoft Office Outlook"

When you try to connect Microsoft Office Outlook 2007 to Microsoft Exchange Server, you may experience any one of the following symptoms:

• If your Outlook profile has been automatically configured, you may receive the following error message:
  The action cannot be completed. The connection to the Microsoft Exchange Server is unavailable. Your network adapter does not have a default gateway.
• If your Outlook profile has been manually configured, you may receive the following error message:
  Your Microsoft Exchange Server is unavailable
  For example, this error may occur when you have an existing profile that was previously connected to the Exchange Server, and then you lose the setting for your default gateway. In this scenario, if you click Check Name to verify your settings in the E-mail Accounts dialog box, you may receive the following error message:
  Outlook cannot log on. Verify that you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Your network adapter does not have a default gateway.

When you try to connect Outlook 2007 to Microsoft Exchange Server 2003 by using RPC over HTTPS, you may receive the following error message:

Cannot start Microsoft Office Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.

This problem may occur if the Outlook 2007 client computer does not have a default gateway configured.