Home » Features

Category: Features

Emails not sending from Exchange 2003 to new Exchange 2007 server

When you introduce a the first Exchange Server 2007 server into an existing Exchange Server 2003 organization you may encounter an issue with mail flow between the two servers.

Emails sent from Exchange 2007 to Exchange 2003 work fine, however emails sent from Exchange 2003 to Exchange 2007 do not work and can be seen in the deferred delivery queue of the Exchange 2003 server.

This issue can be caused by the use of a smart host configured on the Default SMTP Virtual Server on the Exchange 2003 server.

smarthost

To resolve the issue remove the smart host from the Default SMTP Virtual Server and instead configure a new SMTP Connector for the Routing Group to send internet email (the namespace of “*”) to the smart host.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.

Emails not sending from Exchange 2003 to new Exchange 2007 server

When you introduce a the first Exchange Server 2007 server into an existing Exchange Server 2003 organization you may encounter an issue with mail flow between the two servers.

Emails sent from Exchange 2007 to Exchange 2003 work fine, however emails sent from Exchange 2003 to Exchange 2007 do not work and can be seen in the deferred delivery queue of the Exchange 2003 server.

This issue can be caused by the use of a smart host configured on the Default SMTP Virtual Server on the Exchange 2003 server.

smarthost

To resolve the issue remove the smart host from the Default SMTP Virtual Server and instead configure a new SMTP Connector for the Routing Group to send internet email (the namespace of “*”) to the smart host.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.

Exchange 2007 OWA stops working with “reason=0” error

Outlook Web Access on Exchange Server 2007 may stop working after an Update Rollup is applied.  Users who connect to OWA may receive a browser script error or a blank page with a URL of:

 

https://mail.yourdomain.com/owa/auth/logon.aspx?url=https://mail.yourdomain.com/owa/&reason=0

This problem can be caused by either of these conditions:

Cause #1

The Update Rollup was applied while the %systemdrive%\ExchangeSetupLogs folder was missing.

Resolution #1

Replace or restore the ExchangeSetupLogs folder and run the Update Rollup again.

Cause #2

The Update Rollup was applied while IIS services were stopped or disabled.  This will be apparent when you inspect the %systemdrive%\ExchangeSetupLogs\UpdateOwa.log file and find entries with the following text:

 

Getting all Exchange 2007 OWA Virtual Directories
There are no Exchange 2007 OWA Virtual Directories.  Aborting.

owapdatelog

Resolution #2

Enable and start the IIS services (which are required for the Client Access Server role) and run the Update Rollup again.

owapdatelog2

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.

Exchange 2007 OWA stops working with “reason=0” error

Outlook Web Access on Exchange Server 2007 may stop working after an Update Rollup is applied.  Users who connect to OWA may receive a browser script error or a blank page with a URL of:

 

https://mail.yourdomain.com/owa/auth/logon.aspx?url=https://mail.yourdomain.com/owa/&reason=0

This problem can be caused by either of these conditions:

Cause #1

The Update Rollup was applied while the %systemdrive%ExchangeSetupLogs folder was missing.

Resolution #1

Replace or restore the ExchangeSetupLogs folder and run the Update Rollup again.

Cause #2

The Update Rollup was applied while IIS services were stopped or disabled.  This will be apparent when you inspect the %systemdrive%ExchangeSetupLogsUpdateOwa.log file and find entries with the following text:

 

Getting all Exchange 2007 OWA Virtual Directories
There are no Exchange 2007 OWA Virtual Directories.  Aborting.

owapdatelog

Resolution #2

Enable and start the IIS services (which are required for the Client Access Server role) and run the Update Rollup again.

owapdatelog2

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.

Exchange 2007 mailbox users with incorrect language settings

Users may report that their Exchange mailbox displays in an incorrect foreign language in Outlook and Outlook Web Access.  This issue may occur when the Languages attribute of the mailbox is incorrectly set.

You can view the language of a mailbox using the Get-Mailbox cmdlet.

To see all mailboxes that do not match the language you are expecting you can use this PowerShell command, where “en-AU” is the expected language in this example:

To set a user mailbox to the language you desire use the Set-Mailbox cmdlet.

Link: How to change the languages for a user mailbox

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.

Exchange 2007 mailbox users with incorrect language settings

Users may report that their Exchange mailbox displays in an incorrect foreign language in Outlook and Outlook Web Access.  This issue may occur when the Languages attribute of the mailbox is incorrectly set.

You can view the language of a mailbox using the Get-Mailbox cmdlet.

To see all mailboxes that do not match the language you are expecting you can use this PowerShell command, where “en-AU” is the expected language in this example:

To set a user mailbox to the language you desire use the Set-Mailbox cmdlet.

Link: How to change the languages for a user mailbox

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.