Skip to Content

FAQ - Troubleshooting

Active Subscriber uses Exchange's "auto-discovery" to find the EWS URL which is used to retrieve the listserver's mail from Exchange.

It is possible however to over-ride the auto-discovered web services directory with a user specified setting as follows:

Consider upgrading to our latest service release (available from

Add a sting value to the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ActiveSubscriberService\Parameters Add a REG_SZ value 'EWS URL' with value 'https://EWSSERVER/ews/exchange.asmx'

Where EWSSERVER is the hostname of your EWS server (which is usually the hostname you use for OWA).

The EWS URL should normally match what you would see running Get-WebServicesVirtualDirectory in the Exchange Management Shell command line, but some networks do not seem to return a useable URL.

Administrative groups which allow multiple users to manage all lists (ListServer Managers) or a given list ([List Name] Managers) need to be mail enabled.

The documentation for the ListServer Managers group suggests that the group can be either a Distribution Group or a Security Group. But if the group is a Security Group, the group needs te be "mail enabled" in order to work with the list management capability in Active Subscriber. To mail enable a distribution group, you can use the Exchange Management Console (see

The installer needs to run with full administrative permissions.

Open a new console window with "Run as administrator". From the console window, change to the directory containing the MSI.

Run the installer with the following command:
msiexec /i "activesubscriber.msi"

Download our latest service release ( or later). Service releases can be found here.

Versions of Active Subscriber prior to cannot process command messages with certain kinds of attachments, the messages will be "stuck" in the listserver inbox and prevent the list server from continuing until the message is deleted.

The question marks mean that a pre-requisite was not checked because an earlier pre-requisite is missing. As there are dependencies on earlier pre-requisites the checker does not continue to check pre-requisites when it finds one missing. Instead it displays them with a question mark.

If you specify an incorrect password for the service account, the service will install, but you will not be able to start the service. Check the password for the service using the Window Services applet.
Sometimes these errors also occur if the service account does not have sufficient access rights. Try "emulating the list server" as described in the manual.