UAA Service could not connect

Category: Troubleshooting & error messages
Date: March 2010
Product: Exchange Server Archiver

When the Admin Console cannot connect to the UAA Service, an alert is displayed in the Alerts tab, and in the Maintenance tab 'Could not connect' is displayed next to the UAA Service.

There are a number of reasons why this message may be displayed:

there is a problem with your configuration
ASP.NET version is not set to 2.0
ASP.NET 2.0 is not allowed (IIS 6 only)
SSL protocol was selected on IIS 5.1

Problem with configuration

If the Admin Console cannot connect to the UAA Service, there may be a problem with your configuration.

For example:

check that the server on which you installed the UAA Service is running correctly
check that you can browse to the default Web site

ASP.NET version not set to 2.0

By default, IIS (Internet Information Services) runs on the lowest available version of ASP.NET. However, the UAA Service Web application has a minimum requirement of ASP.NET 2.0.

Exchange Server Archiver version 1.1 or later

If you are using Exchange Server Archiver version 1.1 or later, for IIS 7 and IIS 6, the UAA Service installer creates an application pool that is configured for ASP.NET 2.0.

For IIS 5.1, you must set the ASP.NET version to 2.0. The option to set the ASP.NET version may not be available if you installed IIS before .NET 2.0. To make the option available, at the command line, navigate to:

C:\Windows\Microsoft.NET\Framework\v2.0.50727 (for x86)

C:\Windows\Microsoft.NET\Framework64\v2.0.50727 (for x64)

and then run:

aspnet_regiis /iru

To set the ASP.NET version to 2.0:

In the Control Panel, select Administrative Tools, and then Internet Information Services (IIS) Manager.
Navigate to the Web site on which you installed the UAA Service, and then right-click UAAService and click Properties.
Select the ASP.NET tab and ensure that the ASP.NET version is set to v2.0.
Click OK.

Exchange Server Archiver version 1.0

If you are using Exchange Server Archiver version 1.0, you must ensure that the ASP.NET version is set to 2.0 for all versions of IIS. For details of how to do this, see Configuring IIS.

ASP.NET 2.0 is not allowed (IIS 6 only)

In Exchange Server Archiver version 1.0 on IIS 6, if the Admin Console Maintenance tab displays 'Could not connect' next to the UAA Service, and double-clicking the corresponding warning in the Alerts pane displays:

'The request failed with HTTP status 404: Not Found.'

this could be because Web Service Extensions has not allowed the ASP.NET version.

To fix this, follow the instructions under IIS 5.1 and IIS 6.0 in Configuring IIS.

In Exchange Server Archiver version 1.1 on IIS 6, the UAA Service installer automatically sets ASP.NET to Allowed in Web Service Extensions.

SSL protocol selected on IIS 5.1

When you install the UAA Service and you choose to create a new Web site, if you are using IIS 5.1 you cannot use SSL as the communication protocol.

If you selected SSL in the UAA Service installer, the UAA Service appears to complete the installation with no errors. However, when the UAA Service is registered with the Admin Console, in the Maintenance tab 'Could not connect' is displayed next to the UAA Service.

If you open the IIS Microsoft® Management Console snap-in, an error may be displayed against the UAA Service, and you will be unable to start it because it has not installed correctly.

To fix this issue, uninstall the UAA Service, and then either:

reinstall the UAA Service on the same server; and on the Web site creation page select Communication protocol: non-SSL.
or install the UAA Service on a server that uses a later version of IIS

For more information about installing the UAA Service, see Installing the UAA Service.

Was this article helpful?

Search support