XCCC: You May Be Unable to Connect to a Conference After You Change the Active Host Server (273184)

The information in this article applies to:

Microsoft Exchange 2000 Conferencing Server

This article was previously published under Q273184

SYMPTOMS

When you change the active host server for an Exchange 2000 conferencing site to another server in the site, some client computers may be unable to join the previously booked conferences.

CAUSE

This behavior can occur because the clients that attempt to join a conference that had been scheduled before the change occurred are referencing the previous active host server in the join Uniform Resource Locator (URL). As a result, the Conference Management Service that is contacted is idle, not active; therefore, this service is unable to locate the attributes that are needed for the clients to join the conference.

RESOLUTION

To resolve this behavior, replace the contents in the Default.asp file with a redirect parameter that can point the conference participants to the newly defined active host server for the Exchange 2000 conferencing site.

WORKAROUND

To work around this behavior, manually change the URL to reference the new hostname of the active host server or the fully qualified domain name (FQDN), instead of the hostname or FQDN of the previous server.

MORE INFORMATION

To redirect a Web page to another Web page, insert the following code into the new Default.asp page:

<META HTTP-EQUIV="REFRESH" CONTENT="1; URL=<hostname or FQDN">

Modification Type:	Minor	Last Reviewed:	4/25/2005
Keywords:	kbprb KB273184