Error message when you try to use the Live Meeting console to connect to Communications Server 2007: "Live Meeting cannot connect to the meeting."
2008-02-19 22:25
931 查看
这篇文章我觉得比较重要,而且更能了解些从OCS知识大家可以学习下这篇KB
function loadTOCNode(){}
var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'";
var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif";
var depthLimit = 10;
var depth3Limit = 10;
var depth4Limit = 5;
var depth5Limit = 3;
var tocEntryMinimum = 1;
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:
This issue occurs because Communications Server 2007 is not configured to use an 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:
To configure the external Web farm FQDN, follow these steps:
To list the external Web farm FQDNs, follow these steps:
To clear the external Web farm FQDN, follow these steps:
APPLIES TO
Error message when you try to use the Live Meeting console to connect to Communications Server 2007: "Live Meeting cannot connect to the meeting."
function loadTOCNode(){}
Article ID | : | 938288 |
Last Review | : | December 17, 2007 |
Revision | : | 5.0 |
var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif";
var depthLimit = 10;
var depth3Limit = 10;
var depth4Limit = 5;
var depth5Limit = 3;
var tocEntryMinimum = 1;
SYMPTOMS
loadTOCNode(1, '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
loadTOCNode(1, 'cause');This issue occurs because Communications Server 2007 is not configured to use an external URL.
RESOLUTION
loadTOCNode(1, 'resolution');Resolution 1
loadTOCNode(2, 'resolution');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:
1. | 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. |
2. | Click Start, click Run, type wbemtest, and then click OK. |
3. | In the Windows Management Instrumentation Tester dialog box, click Connect. |
4. | In the Connect dialog box, type root\cimv2 in the Namespace box, and then click Connect. |
5. | In the Windows Management Instrumentation Tester dialog box, click Query. |
6. | 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="server name\\sql instance" For Communications Server 2007 Standard Edition Select * from MSFT_SIPGroupExpansionSetting where backend="(local)\\rtc" |
7. | In the Query Result dialog box, double-click the result. |
8. | Select ExternalDLExpansionWebURL, and then click Edit Property. |
9. | In the Property Editor dialog box, click to select the Not NULL option. |
10. | In the Value box, type the external Web farm URL in the following format, and then click Save Property and Save Object: https://externalurl.domain.com/GroupExpansion/Ext/service.asmx |
11. | Click Save Object, and then click Close. |
12. | In the Windows Management Instrumentation Tester dialog box, click Query. |
13. | 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="server name\\sql instance" For Communications Server 2007 Standard Edition Select * from MSFT_SIPDataMCUCapabilitySetting where backend="(local)\\rtc" |
14. | In the Query Result dialog box, double-click the result. |
15. | Select ExternalClientContentDownloadURL, and then click Edit Property. |
16. | In the Property Editor dialog box, click to select the Not NULL option. |
17. | In the Value box, type the external Web farm URL in the following format, and then click Save Property and Save Object: https://externalurl.domain.com/etc/place/null |
18. | Click Save Object, and then click Close. |
19. | In the Windows Management Instrumentation Tester dialog box, click Query. |
20. | 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="server name\\sql instance" For Communications Server 2007 Standard Edition Select * from MSFT_SIPAddressBookSetting where backend="(local)\\rtc" |
21. | In the Query Result dialog box, double-click the result. |
22. | Select ExternalURL, and then click Edit Property. |
23. | In the Property Editor dialog box, click to select the Not NULL option. |
24. | In the Value box, type the external Web farm URL in the following format, and then click Save Property and Save Object: https://externalurl.domain.com/abs/Ext/Handler |
25. | Click Save Object, and then click Close. |
26. | Click Exit. |
Resolution 2
loadTOCNode(2, 'resolution');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:
1. | Log on to the server in the pool by using an account that is a member of RTCUniversalServerAdmins group or that has equivalent permissions. |
2. | Open a command prompt. |
3. | Move to the "Program Files\Common Files\Microsoft Office Communications Server 2007" directory. |
4. | To set the external URL for the Web farm, type the following command: Lcscmd /web /action:updatepoolurls /externalwebfqdn:WebfarmFQDN/poolname:poolname For example, type the following: Lcscmd /web /action:updatepoolurls /externalwebfqdn:contoso.com /poolname:pool2 |
1. | Log on to the server in the pool by using an account that is a member of RTCUniversalServerAdmins group or that has equivalent permissions. |
2. | Open a command prompt. |
3. | Move to the "Program Files\Common Files\Microsoft Office Communications Server 2007" directory. |
4. | To list the external URLs for the Web farm, type the following command: Lcscmd /web /action:ListWMISettings /poolname: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. |
5. | 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:poolName For example, look up the following: Lcscmd /web /action: ListWMISettings /poolname:pool2 |
1. | Log on to the server in the pool by using an account that is a member of RTCUniversalServerAdmins group or that has equivalent permissions. |
2. | Open a command prompt. |
3. | Move to the "Program Files\Common Files\Microsoft Office Communications Server 2007" directory. |
4. | To clear the external URL for the Web farm, type the following command: Lcscmd /web /action:clearpoolexternalurls /poolname:poolName For example, type the following: Lcscmd /web /action:clearpoolexternalurls /poolname:pool2 |
APPLIES TO
• | Microsoft Office Communications Server 2007 Standard Edition |
• | Microsoft Office Communications Server 2007 Enterprise Edition |
Keywords: | kbexpertiseinter kbtshoot kberrmsg kbprb KB938288 |
相关文章推荐
- Error message when you try to install a SQL Server 2005 service pack or a SQL Server 2005 hotfix package: "Error 29528. The setup has encountered an unexpected error while Setting Internal Properties"
- BUG: You receive an "HTTP 500 - Internal server error" error message when you try to view an ASP page after you install Visual S
- FIX: Error message when you try to install a large Windows Installer package or a large Windows Installer patch package in Windows Server 2003 or in Windows XP: "Error 1718. File was rejected by digital signature policy"
- 1182566 - Error: "RUN-050406 Bad system" when you try to run jobs on the server
- Error message when you try to save a table in SQL Server 2008: "Saving changes is not permitted"
- Error message : "Live Meeting cannot connect to the meeting."
- when you try to reconfigure the BizTalk Server 2006 R2 EDI/AS2 Runtime feature
- Error message when you try to modify or to delete an alternate access mapping in Windows SharePoint Services 3.0: "An update conflict has occurred, and you must re-try this action"
- 关于CommunityServer2.1附件过大报错,即ASP.NET2.0中附件设置问题"Cannot Upload Large Files When You Use the HtmlInputFile Server Control"
- XL2000: "Project Is Unviewable" Error Message When You Try to View Project
- you try to use the STM32 Library examples with IAR 6.30.6 you get a loot of error
- You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use
- You receive a "Setup Library wbemupgd.dll could not be loaded" error message when you use Add or Remove Programs in Windows Server 2003
- 插入mysql语句报错:1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near
- You have an error MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 20
- "Unexpected Error 0x8ffe2740 Occurred" Error Message When You Try to Start a Web Site
- Cannot connect to the vCenter server due to a certificate error. Make sure that the appropriate cert
- WinRM不起作用 Connecting to remote server failed with the following error message : WinRM cannot complete the operation
- You receive a C4226 or a C4236 error message when you compile code to contain the keyword in 32-bit Visual C++(ZZ)
- Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when savin