Exchange Server Pro » IIS

Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade

Paul Cunningham — Tue, 06 Dec 2011 12:40:52 +0000

While attempting to upgrade an Exchange Server 2010 Client Access server to Service Pack 2 you may encounter the following error message.

The ‘IIS 6 WMI Compatibility’ component is required. Install the component via Server Manager.

Error message upgrading Exchange 2010 Client Access server to SP2

This error occurs because a new feature of Exchange 2010 SP2 called Outlook Web App Mini requires that IIS component to be installed on Client Access servers.

You can install the component manually by opening a PowerShell window and running the following commands.

PS C:\> Import-Module servermanager

PS C:\> Add-WindowsFeature Web-WMI

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True    No             Success   {IIS 6 WMI Compatibility}

Click Retry on the Readiness Checks dialog box above, or if you’ve already cancelled the installation simply start it again.

You can also avoid the error by installing the Service Pack 2 upgrade from the command line. Open a command prompt and navigate to the folder where the Exchange 2010 SP2 files have been extracted, and run the following command:

C:\Admin\ex2010sp2>setup /mode:upgrade /installwindowscomponents

This will automatically install the required components for you when the upgrade process runs.

Get more Exchange Server tips at ExchangeServerPro.com

500 Internal Server Error for Exchange 2007 Outlook Web Access

Paul Cunningham — Fri, 05 Aug 2011 11:36:52 +0000

In an Exchange Server 2007 environment you may encounter the following error when users attempt to access Outlook Web Access.

500 – Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

The error occurs when user access OWA via the /exchange path but not the /owa. For example:

https://mail.company.net/owa (gets no error)
https://mail.company.net/exchange (gets the 500 internal error)

This can occur when the Exchange 2007 Mailbox server is missing the Web-ISAPI-Ext feature. You can check this by logging on to the server and running this command:

C:\>servermanagercmd -q | findstr "Web-ISAPI-Ext"
            [ ] ISAPI Extensions  [Web-ISAPI-Ext]

If there is no check mark next to the feature then it will need to be installed by running the following command:

C:\>servermanagercmd -i web-isapi-ext
..

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Application Development.
[Installation] Succeeded: [Web Server (IIS)] ISAPI Extensions.

Success: Installation succeeded.

When you check the status of the feature it will now show as installed.

C:\>servermanagercmd -q | findstr "Web-ISAPI-Ext"
            [X] ISAPI Extensions  [Web-ISAPI-Ext]

That should resolve the “500 internal error” when accessing OWA via the /exchange path.

Get more Exchange Server tips at ExchangeServerPro.com

How to Change the Log File Directory in IIS7

Paul Cunningham — Wed, 03 Aug 2011 12:41:39 +0000

On an Exchange Server 2010 Client Access server a lot of logging can be generated by IIS for client traffic such as OWA and ActiveSync.

For some servers the need to retain this logging for a long time may cause a disk space issue. To resolve this you can simply change the log file directory that IIS7 uses.

Open IIS Manager from Administrative Tools and click on the Default Web Site.

Double-click the Logging icon.

Type in the path to the new log directory that you want to use, or click Browse and navigate to it.

When you’ve entered or chosen the new log directory click Apply.

The new directory will be created (if it doesn’t already exist) when the next log entries are written by the server.

You can copy the existing logs from the old location to the new log directory. Just be aware that the server may have already created a log file in the new directory for the current day, but you can simply tell the copy to keep both files by renaming one of them. Or if you make the change during a period of the day that there is no activity then you probably won’t run into any duplicate file name issues.

We can also make the same configuration change using Powershell. From a Powershell window type the following commands.

PS C:\> Import-Module WebAdministration

PS C:\> Set-ItemProperty 'IIS:\Sites\Default Web Site' -name logfile.directory "D:\IISLogs"

Get more Exchange Server tips at ExchangeServerPro.com

Migrate SSL Certificates from Exchange Server 2003 to Exchange Server 2007

Paul Cunningham — Fri, 28 Aug 2009 08:30:10 +0000

The Exchange Server 2007 Client Access Server is installed with a self-signed certificate on the IIS site hosting Exchange remote access services. Before publishing this to the internet you should export your existing SSL certificate from the Exchange Server 2003 server and import it on the Exchange Server 2007 server.

Export the SSL Certificate from the Exchange Server 2003 server

On the Exchange Server 2003 server go to Start -> Run and launch mmc.exe.

Click File and Add/Remove Snap-in.

Click on Add and choose the Certificates snap-in.

Choose Computer Account then click Next.

Choose Local Computer and then click Finish.

Click Close and OK to return to the MMC, with the Certificates snap-in now installed. Navigate to Certificates (Local Computer)/Personal/Certificates. The SSL certificate used for Exchange remote access will be visible in the right pane of the console.

Right-click the certificate and choose All Tasks -> Export. Click Next to move past the welcome dialog for the Certificate Export Wizard.

Choose Yes, export the private key and then click Next.

Click Next to accept the default file format.

Enter a password for the exported certificate. You will need to remember this password to import the certificate onto other servers. Click Next to continue.

Enter a file name for the exported certificate. Click Next to continue.

Click Finish to complete the wizard.

Import the SSL Certificate on the Exchange Server 2007 server

Copy the exported certificate file to the Exchange Server 2007 server.

On the Exchange Server 2007 server launch mmc.exe and add the Certificates snap-in. Navigate to Certificates (Local Computer)/Personal/Certificates. Right-click Certificates and choose All Tasks -> Import. Click Next to move past the welcome dialog.

Browse to the location you copied the certificate file to. Select the file and click Open.

Click Next to continue.

Enter the password for the certificate, and tick the box to mark the key as exportable. Click Next to continue.

Click Next to import the certificate to the Personal certificate store.

Click Finish to complete the Certificate Import Wizard.

Note: These next steps apply to IIS 7 on Windows Server 2008.

Launch Internet Information Services (IIS) Manager from the Administrative Tools menu of the Exchange Server 2007 server. Navigate to the Default Web Site.

Click Bindings in the Actions pane of the IIS Manager console.

Select https and then click Edit.

Use the drop-down list to select the SSL certificate that you imported on the server.

Click OK and then Close.

Get more Exchange Server tips at ExchangeServerPro.com

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

Paul Cunningham — Fri, 30 Jan 2009 03:49:24 +0000

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.

Resolution #2

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

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server Pro » IIS

Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade

Related posts:

500 Internal Server Error for Exchange 2007 Outlook Web Access

Related posts:

How to Change the Log File Directory in IIS7

Related posts:

Migrate SSL Certificates from Exchange Server 2003 to Exchange Server 2007

Export the SSL Certificate from the Exchange Server 2003 server

Import the SSL Certificate on the Exchange Server 2007 server

Related posts:

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

Cause #1

Resolution #1

Cause #2

Resolution #2

Related posts: