locked
Live meeting doesn't connect RRS feed

  • Question

  • Hi all,

    This is my first time being here and installing OCS2007 Smile

    Here is my situation, We installed OCS 2007, and web scheduler, (the name of the server is Communicator) i activiated it and so far so good. i was able to connect to the web interface to schedule a meeting, a notification has been sent to users. I downloaded the console for live meeting. I clicked on the "click here" in the email that i got to attendent the meeting, it launches the MS Live meeting console, asks me for my name, i put it in, but it keeps giving me an error:

     

    "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"

     

    I looked at the logs, i see 2 errors

     

    Under Application log, i see

     

    Event Type: Error
    Event Source: LiveMeeting
    Event Category: None
    Event ID: 1015
    Date:  5/10/2007
    Time:  8:12:29 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    LiveMeeting failed to connect to server lcs.mycompnay.local (192.128.28.56) on port 79 due to error 10060.  The server is not listening on the port in question, the service is not running on this machine, the service is not responsive, or network connectivity doesn't exist.
     
     Resolution:
     Please make sure that your workstation has network connectivity.  If you are using manual configuration, please double-check the configuration.  The network administrator should make sure that the service is running on port 79 on server
    lcs.mycompnay.local (192.128.28.56)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    NOTE: lcs.mycompnay.local (192.128.28.56) is a LCS 2005, i installed it last year but i didn't finish all the setup. So i don't know why it is taking this path? it should take the ie: communicator.mycompany.local. I looked in the registry of the OCS 2007 (communicator) to see if there is an entry for lcs or 192.128.28.56 with no luck.

     

    The second error is from Office Communication Server log

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61030
    Date:  5/10/2007
    Time:  9:00:47 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process RtcHost(5028) did not receive a certificate from the client.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    I don't know what to do here. Sad

    Please help.

     

    Rami


    Thursday, May 10, 2007 1:04 PM

Answers

  • Hi Rami,

     

    As you mentioned that you are using OCS Standard Edition, your naming is perfectly valid. Running OCS SE will always lead to the same name on the OCS pool and the machine. My remark regarding pool naming was only valid for Enterprise Edition.

     

    Regarding the problem with the certificate, I have to tell you that you cannot use a SelfSSL issued certificate for OCS. Please either use an internal Certificate Authority or obtain a certificate from one of the public CAs.

     

    More information regarding certificate requirements can be found here:

    - OCS_Planning_Guide.doc

    - OCS_StandardEditionDeployment.doc

    - OCS_EdgeServerDeploy.doc

     

    In case you need additional certificate information on LCS 2005 SP1, please check the "Live Communications Server 2005 Certificate Configuration" document.

     

    Thanks

    Bernd

     

     

    Monday, May 21, 2007 2:55 PM

All replies

  • Hi Rami,

     

    I am assuming that lcs.mycompnay.local is just a typo and should be lcs.mycompany.local.

     

    Did you check, whether there are any remainders in DNS that might refer to lcs.mycompany.local?

    LMConsole writes a log file to %temp%\pwconsole-debugXX.txt. Did you check this file for errors and warnings?

    On which port does your Live Meeting Service listen? Is it port 79?

     

    Thanks

    Bernd

     

     

     

     

    Monday, May 14, 2007 11:59 AM
  • Bernd,

    Thanks for your reply...

    Ya, it was a typo.

    I decided last week to remove lcs 2005, and reinstall ocs2007..... now i'm getting different errors, I can't start "Office Communications server Front-End.

     

    Below is my installation summary:

     

    Installation Path: D:\Program Files (x86)\Office Communications Server 2007\
    Main service account name: RTCService (password: mycompany)
    Conferencing service account name: RTCComponentService (password: mycompany)
    Internal web farm FQDN: Communicator.mycompany.local
    External web farm FQDN: <Empty>
    User database path: D:\LC Data\
    User database log path: D:\LC Log\
    Transient user database path: D:\LC Data\
    Transient user database log path: D:\LC Log\

    Pool Information
            Pool Name: Communicator.mycompany.local
    Global SIP domains:
            mycompany.local
    Client automatic logon: True
    This server or pool is a director for client automatic logon: True
    SIP domains for client automatic logon:
            mycompany.local
    Ready to configure edge topology and routing: False

     

     

    below is what i'm getting from the event logs:

     

    Event Type: Error
    Event Source: OCS Protocol Stack
    Event Category: (1001)
    Event ID: 14517
    Date:  5/14/2007
    Time:  8:39:23 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The server configuration validation mechanism detected some serious problems.

    10 errors and 0 warnings were detected.

    ERRORS:
    Two server roles at FQDN [Communicator.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {D648481A-E235-874F-911E-8F667C6BD874} and role 'Conferencing Server' (option is set). Second server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (option is not set).
    Two server roles at FQDN [Communicator.mycompany.local] have different server version numbers. First server has GUID {D648481A-E235-874F-911E-8F667C6BD874} and role 'Conferencing Server' (version 3). Second server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (version 0).
    Two server roles at FQDN [Communicator.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {F56D2552-7982-0141-A2AF-00A2C99F9F97} and role 'Conferencing Server' (option is set). Second server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (option is not set).
    Two server roles at FQDN [Communicator.mycompany.local] have different server version numbers. First server has GUID {F56D2552-7982-0141-A2AF-00A2C99F9F97} and role 'Conferencing Server' (version 3). Second server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (version 0).
    Two server roles at FQDN [Communicator.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {A49E05C0-E3AA-934F-B3B4-4386B9EC16AB} and role 'Conferencing Server' (option is set). Second server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (option is not set).
    Two server roles at FQDN [Communicator.mycompany.local] have different server version numbers. First server has GUID {A49E05C0-E3AA-934F-B3B4-4386B9EC16AB} and role 'Conferencing Server' (version 3). Second server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (version 0).
    Two server roles at FQDN [Communicator.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (option is not set). Second server has GUID {EBC0E3CC-E4E1-ED4E-9A2A-FF68CE1CA446} and role 'Conferencing Server' (option is set).
    Two server roles at FQDN [Communicator.mycompany.local] have different server version numbers. First server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (version 0). Second server has GUID {EBC0E3CC-E4E1-ED4E-9A2A-FF68CE1CA446} and role 'Conferencing Server' (version 3).
    Two server roles at FQDN [Communicator.mycompany.local] have different 'Treat As Authenticated' options. First server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (option is not set). Second server has GUID {C5E4FEF0-EC10-374A-B86E-6AE9D5A260E3} and role 'Enterprise Edition' (option is set).
    Two server roles at FQDN [Communicator.mycompany.local] have different server version numbers. First server has GUID {BC60C3C7-C163-5942-8664-9C7016417337} and role 'A/V Authentication Service' (version 0). Second server has GUID {C5E4FEF0-EC10-374A-B86E-6AE9D5A260E3} and role 'Enterprise Edition' (version 3).

    WARNINGS:
    No warnings

    Cause: The configuration is invalid and the server might not behave as expected.
    Resolution:
    Review and correct the errors listed above. You also wish to review any warnings present.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    ---------------------

     

    Event Type: Error
    Event Source: OCS Protocol Stack
    Event Category: (1001)
    Event ID: 14497
    Date:  5/14/2007
    Time:  8:39:23 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    One or more configuration errors were detected at startup.

    Cause: There are serious problems with the server configuration that prevented it from starting up.
    Resolution:
    Review the previous event log entries to identify failures. Alter the server configuration as required. If problems persist, contact product support.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    -----------------

     

    Event Type: Error
    Event Source: OCS Protocol Stack
    Event Category: (1001)
    Event ID: 14352
    Date:  5/14/2007
    Time:  8:39:23 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    Unable to start the stack.

    Error: 0x0xC3E93C47 (No Message Text Found).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    ----------------

     

    Event Type: Error
    Event Source: OCS Server
    Event Category: (1000)
    Event ID: 12326
    Date:  5/14/2007
    Time:  8:39:23 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    Failed starting the protocol stack. The service has to stop

    Error code is:0xC3E93C47 (No Message Text Found).
    Cause: Check the previous entries in the event log for the failure reason.
    Resolution:
    Try restarting the server after resolving the failures listed in the previous event log entries.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    --------------

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/14/2007
    Time:  8:40:51 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process AcpMcuSvc(3184) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/14/2007 8:39:51 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    -----------------

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/14/2007
    Time:  8:40:57 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process IMMcuSvc(3408) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/14/2007 8:39:57 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    ----------------

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/14/2007
    Time:  8:41:09 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process DataMCUSvc(3608) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/14/2007 8:40:09 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

     

    -----------------

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/14/2007
    Time:  8:41:19 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process AVMCUSvc(1392) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/14/2007 8:40:19 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    -----------

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/14/2007
    Time:  8:43:05 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process AcpMcuSvc(3184) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 14, since 5/14/2007 8:39:51 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    ----------

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/14/2007
    Time:  8:43:12 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process IMMcuSvc(3408) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 14, since 5/14/2007 8:39:57 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

    Thanks to all.

     

    Rami

     

    Monday, May 14, 2007 12:56 PM
  • Hi Rami,

     

    The Event 14517 indicates that there are still remainders of a previous LCS/OCS installation in Active Directory under CN=RTC Service,CN=Microsoft,CN=System,DC=<your context>. Did you successfully remove all previous installations, before running OCS setup the last time?

     

    From my perspective, the fastest solution will be

    - Uninstalling OCS

    - Removing the "RTC Service" container from AD

    - Reinstalling OCS

     

    You could also try to find the GUIDs that are mentioned in Event 14517 in the "RTC Service" container and check which entries are related to your current installation with communicator.mycompany.local and which GUIDs refer to lcs.mycompany.local. You could identify which GUID belongs to which server by checking the attribute msRTCSIP-TrustedServerFQDN and msRTCSIP-TrustedServerVersion in adsiedit.msc or with ldp.exe.

     

    Nevertheless, removing the wrong GUID entries from AD does not guarantee that there are still other old entries and settings left. That's why I would prefer to uninstall OCS, clean AD and then reinstall OCS.

     

    Thanks

    Bernd

    Wednesday, May 16, 2007 10:47 AM
  • ok, here is what i did

    1) uninstalled ocs 2007

    2) uninstalled sql 2005

    3) rebooted the server

    4) went to AD (users), deleted "RTCService" and "RTCComponetService"

    5) Ran through the list (Deploy Server, Configure Server, Configure Certificate, verify replication )

    6) Clicked on Run (Start Services), everythings started except the front server Sad

     

    Here what i'm getting

     

    Service Name: RTCSRV
    Descriptive Name: Office Communications Server Front-End
    Service Status: Error
      Failure
    [0xC3EC79E6] Service failed to start as requested.


    In the event log (Office Communications server)

     

    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/16/2007
    Time:  8:05:03 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process AcpMcuSvc(2624) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/16/2007 8:04:03 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/16/2007
    Time:  8:05:10 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process IMMcuSvc(2396) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/16/2007 8:04:10 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     


    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/16/2007
    Time:  8:05:24 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process DataMCUSvc(1020) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/16/2007 8:04:24 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Error
    Event Source: OCS MCU Infrastructure
    Event Category: (1022)
    Event ID: 61013
    Date:  5/16/2007
    Time:  8:05:35 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The process AVMCUSvc(3036) failed to send health notifications to the MCU factory at https://Communicator.mycompany.local:444/LiveServer/MCUFactory/.
    Failure occurrences: 5, since 5/16/2007 8:04:35 AM.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    In the event log (system log)

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7024
    Date:  5/16/2007
    Time:  8:03:44 AM
    User:  N/A
    Computer: COMMUNICATOR
    Description:
    The Office Communications Server Front-End service terminated with service-specific error 3286842439 (0xC3E93C47).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

     

     

    Help please.

     

    Thanks

    Rami

    Wednesday, May 16, 2007 12:17 PM
  • Hi Rami,

     

    So we fixed the problem with Event 14517 .

     

    In your last post, you mentioned that you uninstalled SQL2005. Does that mean you are running Enterprise Edition? We recommend running SQL on a different box than OCS.

     

    I also saw that your pool name seems to be identical to the machine name (communicator). The pool name has to be different from the machine name.

     

    The remaining error [0xC3EC79E6] points to a certificate problem. If I am choosing an invalid certificate on my OCS EE box, I get the same Events 61013, you posted in your last reply. Please check the certificate you are using and/or request a new certificate from your CA, after making sure your pool name does not match your machine name. (Please see "OCS_EnterpriseEditionDeployment.doc" Section 3.6)

     

    Thanks

    Bernd

    Wednesday, May 16, 2007 1:11 PM
  • Bernd,

    thanks man for all your help.

    no, i'm still using the standard edition, but when i installed ocs 2007, it detected that sql is not installed and installed it for me on the same machine... we are around 12-15 people who works here, so i don't think it is going to matter, is it?

     

    About the pool, is there a way to change the name of the pool without reinstalling the whole thing? i reinstalled this thing for like 5 times now... i'm an expert Smile

     

    Thanks

     

    Rami

    Wednesday, May 16, 2007 5:53 PM
  • and about the certificate, i'm using the SelfSSL. I'm creating my own certificate, then go to IIS, export it, then import it into OCS2007

    what should it match? should it be like communicator.mycompany.local? or communicator.mycompany.com? or communicator?

     

    thanks agian

    Rami

    Wednesday, May 16, 2007 5:59 PM
  • Hi Rami,

     

    As you mentioned that you are using OCS Standard Edition, your naming is perfectly valid. Running OCS SE will always lead to the same name on the OCS pool and the machine. My remark regarding pool naming was only valid for Enterprise Edition.

     

    Regarding the problem with the certificate, I have to tell you that you cannot use a SelfSSL issued certificate for OCS. Please either use an internal Certificate Authority or obtain a certificate from one of the public CAs.

     

    More information regarding certificate requirements can be found here:

    - OCS_Planning_Guide.doc

    - OCS_StandardEditionDeployment.doc

    - OCS_EdgeServerDeploy.doc

     

    In case you need additional certificate information on LCS 2005 SP1, please check the "Live Communications Server 2005 Certificate Configuration" document.

     

    Thanks

    Bernd

     

     

    Monday, May 21, 2007 2:55 PM
  • Hi Rami, I just got solve the same problem that you are experiencing, I did the following procedure:

     

    Go To OCS Console-Expand Domains-YourServername-Properties-FrontEnd Properties-HostAuthorization, here you will remove the FQDN related with your server and add again but using the server IP Address, after that restart all services and it should work.

     

    Good Luck

     

    Let me know if this procedures solved your problem.

     

    Regards,


    Dirk

    Tuesday, May 22, 2007 7:29 AM
  • Dirk,

    THanks man for your input... did you use the SelfSSL? becuase now i'm having a problem it. As soon as i can solve the cert issue, i will try your solution.

     

    Thanks again.

     

    Rami

    Tuesday, May 22, 2007 1:42 PM
  • We created a new domain and joined OCS2007 to that domain... everything started from the first try... so i think there is something in the other AD that is messing with it.

     

    Any help would be appreciated.

     

    Thanks

     

    Rami

    Friday, June 1, 2007 3:27 PM