Microsoft Fix it BLOG

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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

davecal_ms — Fri, 29 Jan 2010 19:00:00 GMT

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