Microsoft KB Archive/938288

= Error message when you try to use the Live Meeting console to connect to Communications Server 2007: &quot;Live Meeting cannot connect to the meeting.&quot; =

Article ID: 938288

Article Last Modified on 12/17/2007

-

APPLIES TO


 * Microsoft Office Communications Server 2007 Standard Edition
 * Microsoft Office Communications Server 2007 Enterprise Edition

-



SYMPTOMS
You cannot connect to Microsoft Office Communications Server 2007 by using the Microsoft Office Live Meeting console. You receive the following error message:

Live Meeting cannot connect to the meeting.

Wait a few moments, and then try to join the meeting again.

If you still cannot connect, contact your administrator or technical support.

Additionally, the following message is logged in the Pwconsole log file:

Invalid URL Specified.

Note By default, the Pwconsole log file is enabled. The file can be found in the %Temp% folder.

On the computer that is running Communications Server 2007, the following event is logged in the Event Viewer Application log: OCS Data MCU Category 1018 Event ID: 41059 Failed to connect External Users because the Download URL is invalid. Failure occurrences: NE, since FE.



CAUSE
This issue occurs because Communications Server 2007 is not configured to use an external URL.



Resolution 1
To resolve this issue, use Windows Management Instrumentation (WMI) to configure the server to use the external URL.

If you did not configure a fully qualified domain name (FQDN) for an external Web farm when you created the Communications Server 2007 Enterprise pool or when you configured the Communications Server 2007 Standard Edition server, you must manually add this FQDN by using WMI.

To configure the external Web farm FQDN, follow these steps:  Log on to the computer that is running Communications Server 2007 Standard Edition or Communications Server 2007 Enterprise edition by using an account that is a member of the RTCUniversalServerAdmins group or that has equivalent permissions. Click Start, click Run, type wbemtest, and then click OK. In the Windows Management Instrumentation Tester dialog box, click Connect. In the Connect dialog box, type root\cimv2 in the Namespace box, and then click Connect. In the Windows Management Instrumentation Tester dialog box, click Query. In the Query dialog box, type the following in the Enter Query box according to the edition of Communications Server 2007 that you are using, and then click Apply:

For Communications Server 2007 Enterprise pool

Select * from MSFT_SIPGroupExpansionSetting where backend=&quot; \\ &quot;

For Communications Server 2007 Standard Edition

Select * from MSFT_SIPGroupExpansionSetting where backend=&quot;(local)\\ &quot; </li> In the Query Result dialog box, double-click the result.</li> Select ExternalDLExpansionWebURL, and then click Edit Property.</li> In the Property Editor dialog box, click to select the Not NULL option.</li> In the Value box, type the external Web farm URL in the following format, and then click Save Property and Save Object:

https://. .com/GroupExpansion/Ext/service.asmx

</li> Click Save Object, and then click Close.</li> In the Windows Management Instrumentation Tester dialog box, click Query.</li> In the Query dialog box, type the following in the Enter Query box according to the edition of Communications Server 2007 that you are using, and then click Apply:

For Communications Server 2007 Enterprise pool

Select * from MSFT_SIPDataMCUCapabilitySetting where backend=&quot; \\ &quot;

For Communications Server 2007 Standard Edition

Select * from MSFT_SIPDataMCUCapabilitySetting where backend=&quot;(local)\\ &quot; </li> In the Query Result dialog box, double-click the result.</li> Select ExternalClientContentDownloadURL, and then click Edit Property.</li> In the Property Editor dialog box, click to select the Not NULL option.</li> In the Value box, type the external Web farm URL in the following format, and then click Save Property and Save Object:

https://. .com/etc/place/null

</li> Click Save Object, and then click Close.</li> In the Windows Management Instrumentation Tester dialog box, click Query.</li> In the Query dialog box, type the following in the Enter Query box according to the edition of Communications Server 2007 that you are using, and then click Apply:

For Communications Server 2007 Enterprise pool

Select * from MSFT_SIPAddressBookSetting where backend=&quot; \\ &quot;

For Communications Server 2007 Standard Edition

Select * from MSFT_SIPAddressBookSetting where backend=&quot;(local)\\ &quot; </li> In the Query Result dialog box, double-click the result.</li> Select ExternalURL, and then click Edit Property.</li> <li>In the Property Editor dialog box, click to select the Not NULL option.</li> <li>In the Value box, type the external Web farm URL in the following format, and then click Save Property and Save Object:

https://. .com/abs/Ext/Handler

</li> <li>Click Save Object, and then click Close.</li> <li>Click Exit.</li></ol>

Resolution 2
If you did not configure an FQDN for an external Web farm when you created the Communications Server 2007 Enterprise pool or when you configured the Communications Server 2007 Standard Edition server, you can manually change the URLs. To do this, you can use the following LCSCmd commands to configure or change the external URLS that are specified in Table 3 Directories that are used by Web Components servers.

To configure the external Web farm FQDN, follow these steps: <ol> <li>Log on to the server in the pool by using an account that is a member of RTCUniversalServerAdmins group or that has equivalent permissions.</li> <li>Open a command prompt.</li> <li>Move to the &quot;Program Files\Common Files\Microsoft Office Communications Server 2007&quot; directory.</li> <li>To set the external URL for the Web farm, type the following command:

Lcscmd /web /action:updatepoolurls /externalwebfqdn: /poolname:

For example, type the following:

Lcscmd /web /action:updatepoolurls /externalwebfqdn:contoso.com /poolname:pool2

</li></ol>

To list the external Web farm FQDNs, follow these steps: <ol> <li>Log on to the server in the pool by using an account that is a member of RTCUniversalServerAdmins group or that has equivalent permissions.</li> <li>Open a command prompt.</li> <li>Move to the &quot;Program Files\Common Files\Microsoft Office Communications Server 2007&quot; directory.</li> <li>To list the external URLs for the Web farm, type the following command:

Lcscmd /web /action:ListWMISettings /poolname:

For example, type the following:

Lcscmd /web /action: ListWMISettings /poolname:pool2

This command creates a remote list of WMI setting values and outputs the location of the report.</li> <li>Open the file by using Internet Explorer or another Web browser, and then look up the values for the external URLs:

Lcscmd /web /action:ListWMISettings /poolname:

For example, look up the following:

Lcscmd /web /action: ListWMISettings /poolname:pool2

</li></ol>

To clear the external Web farm FQDN, follow these steps: <ol> <li>Log on to the server in the pool by using an account that is a member of RTCUniversalServerAdmins group or that has equivalent permissions.</li> <li>Open a command prompt.</li> <li>Move to the &quot;Program Files\Common Files\Microsoft Office Communications Server 2007&quot; directory.</li> <li>To clear the external URL for the Web farm, type the following command:

Lcscmd /web /action:clearpoolexternalurls /poolname:

For example, type the following:

Lcscmd /web /action:clearpoolexternalurls /poolname:pool2

</li></ol>

Keywords: kbexpertiseinter kbtshoot kberrmsg kbprb KB938288

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.