Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Error creating a Live Meeting RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a problem creating a Live Meeting.

    When I logon to https://<FQDN>/conf/int/login.aspx I'm validated OK, but then I resive the following error:

    Server Error

    A server error has occurred. Please contact the administrator.
    Error Source: System.DirectoryServices
    Error Type: System.Runtime.InteropServices.COMException
    Error Message: An operations error occurred.
    Error Code: -2147016672

     

    When I try to schedule a live meeting from outlook, I get the following error:

     

    Error- Microsoft Live Meeting.

    You do not have the privilege to schedule live meetings; please contact your live meeting administrator.

     

    The Live Meeting logon is successfully verified in Outlook and in the live meeting client, under user accounts.

     

    I can create and join conferences made from outlook, the problem is only related to Live Meetings.

     

    Also it is not possible to start a live meeting from the communicator client. The menu point is there, but nothing happens when you click it, or I have one of the two menupoints that is supposed exists according to the communicator_2007_getting_started_guide picture on page 40.  I only have the one saying: ”Meet now with Microsoft Office Live Meeting (Server)” Missing the one saying: “Meet now with Microsoft Office Live Meeting (Service)”

     

    Kind regards.

    Kenneth

     

    PS: I have installed the Web scheduler and there is assigned a certificate to the IIS server.

    Tuesday, April 10, 2007 9:33 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
     

    Hi

    I had to configure and enable web conferencing. (It was all in the manual *shrug*)

    According to OCS_EnterpriseEditionDeployment.doc page 35 I hadn’t enabled web conferencing.

    Doing this, then rebooted the server, then opened the LM client user accounts and tested the connection again, then the meet now button paired J and I’m now able to create Live Meetings using the communicator client.

    I still get the -2147016672  error when logging on to the website: https://<FQDN>/conf/int/login.aspx

     

    Kind regards

    Kenneth

     

     

    Here is the description from the OCS_EnterpriseEditionDeployment.doc document:

    To configure A/V and Web conferencing

    1.         Click Start, click Control Panel, click Administrative Tools, and then click Office Communications Server 2007.

    2.        Right-click the Forest node, click Properties, and then click Global Properties.

    3.        Click Meetings, and then do one of the following:

    ·         To allow the selected users to organize meetings that include anonymous participants, click Anonymous participants, and then click Allow users to invite anonymous participants.

    ·         To prevent the selected users from organizing meetings that include anonymous participants, click Anonymous participants, and then click Disallow users from inviting anonymous participants.

    ·         To allow only some users to organize meetings that include anonymous participants, click Anonymous participants, and then click Enforce per user. Ensure that you follow the procedures in the “Configure Users” section of this document to enable or disable this feature for individual users.

    Important

    By default, all users are allowed to organize meetings that include anonymous participants.


    4.        In the Policy Definition list, click the name of a policy, and then click Edit.

    5.        In the Edit Policy dialog box, select the Enable Web conferencing check box, and then change any or all of the settings shown in the table above, and then click OK.

    6.        Click Apply.

    7.        After you finish editing the features enabled by each policy, decide which policy to apply to meetings organized by users. Do one of the following:

    ·         To apply the same policy to all users, click Global policy, and then click the name of the policy that defines the features you want to enable for all users.

    ·         To apply different policies to different users, click Global policy, and then click Use per user policy. Ensure that you follow the procedures in the “Configure Users” section of this document to configure the meeting policy for individual users.

    8.        When you are finished, click OK.

    For more information about administering meeting features, refer to Microsoft Office Communications Server Beta 3 Administrator Guide.

    If you expect heavy audio/video traffic in your environment, you can optimize your network interface card settings to accommodate this volume. See Appendix F in this document for more information


    Wednesday, April 18, 2007 10:48 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    ++up++

     

    I have the same problem

     

    >When I logon to https://<FQDN>/conf/int/login.aspx I'm validated OK, but then I resive the following error:

    >Server Error

    >A server error has occurred. Please contact the administrator.
    >Error Source: System.DirectoryServices
    >Error Type: System.Runtime.InteropServices.COMException
    >Error Message: An operations error occurred.
    >Error Code: -2147016672

     

    But not with outlook I have the right permissions to create meeting but it's doesn't work.

     

    When I try to create a meeting whith the meet now option in the live meeting client , it says

    "Live meeting can not connect to the meeting

    Wait a feww moment and the try to join the meeting again

    If you still cannot connect contact your administrator or technical support"

     

    In the PW console I have the folowing line but I have no idea about where it could come from.

    [MC] 09:46:31:872 GMT [THREAD 3852]  Idea Forwarded TCP: Probing server: mocs.exakis.com:442
    [MC] 09:46:31:872 GMT [THREAD 3852]  Idea SSLTunnelStream: Establishing SSL Tunnel Stream to mocs.exakis.com...
    [MC] 09:46:31:872 GMT [THREAD 3852]  Drinks TunnelSocket::connect begin
    [MC] 09:46:31:872 GMT [THREAD 3852]  Drinks SslSocket::connect begin
    [MC] 09:46:32:171 GMT [THREAD 3852]  Idea SSL: connection info
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Protocol:        128
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Cipher:          Id: 0x6801
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Cipher Strength: 128
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Hash:            Id: 0x8003
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Hash Strength:   128
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Exch:            Id: 0x2400
    [MC] 09:46:32:171 GMT [THREAD 3852] SSL: Exch Strength:   1024
    [MC] 09:46:32:171 GMT [THREAD 3852]  Drinks SslSocket::connect end OK
    [MC] 09:46:32:171 GMT [THREAD 3852]  Drinks TunnelSocket::connect ProxyHeader sent.
    [MC] 09:46:32:171 GMT [THREAD 3852]  Idea SSLTunnelStream: Established SSL Tunnel Stream to mocs.exakis.com
    [MC] 09:46:32:171 GMT [THREAD 3852]  Idea Forwarded TCP probe succeeded
    [MC] 09:46:32:171 GMT [THREAD 2724]  Idea Best mode for Client RPC is : 1
    [MC] 09:46:32:171 GMT [THREAD 2724]  Idea Best mode is fwdtls. Reusing stream in probe.
    [MC] 09:46:32:186 GMT [THREAD 4040]  Idea PWS Handshake sent.
    [MC] 09:46:32:265 GMT [THREAD 2668]  Email Error reading data. ErrCode = 10054
    [MC] 09:46:32:265 GMT [THREAD 2668]  Email Socket error while reading.
    [MC] 09:46:32:265 GMT [THREAD 2668]  Email SslSocket::close: socket is not connected
    [MC] 09:46:32:265 GMT [THREAD 2668]  Wilted Flower PWException being thrown: placeware:Stick out tongueWException: Invalid handshake response from server (e:\lcs_se_ls2007_b3r\src\dev\meetingconsole\client\kernel\tcpstream.cpp: placeware::TcpStream::endHandshake(), 102)
    [MC] 09:46:32:265 GMT [THREAD 2668]  [F] placeware::InitializationException: Invalid handshake response from server (e:\lcs_se_ls2007_b3r\src\dev\meetingconsole\client\kernel\tcpstream.cpp: placeware::TcpStream::endHandshake(), 102)
    [MC] 09:46:32:265 GMT [THREAD 2668]  Drinks Dumping connectionReaderStats:  Number reads: 0 Bytes read: 0 Messages created: 0
    [MC] 09:46:32:265 GMT [THREAD 2668]  Idea ConnectionReader shutdown: readerLoop exited
    [MC] 09:46:32:265 GMT [THREAD 2304]  Idea ReconnectManager - got ConnectionEvent:Big Smileisconnected, reason = readerLoop exited
    [MC] 09:46:32:265 GMT [THREAD 2304]  Idea ReconnectManager - not connected, will continue with current state
    [MC] 09:46:32:265 GMT [THREAD 4040]  Idea ConnectionWriter::writerLoop() exiting
    [MC] 09:46:32:265 GMT [THREAD 2668]  Drinks Dumping connectionWriterStats:  Number writes: 1 Bytes written: 2564 Messages handled: 50
    [MC] 09:46:32:265 GMT [THREAD 2304]  Drinks CMeetingInstance:SurprisenLostDataMCUConnectionEvent, reason = readerLoop exited
    [MC] 09:46:32:265 GMT [THREAD 2304]  Drinks CMeetingInstance - still connecting - will not reconnect to Data MCU
    [MC] 09:46:32:265 GMT [THREAD 2668]  Idea ConnectionWrite shutdown: readerLoop exited
    [MC] 09:46:32:265 GMT [THREAD 2304]  Drinks CMeetingInstanceEvent:SurprisenJoinException Setting joinexception event.
    [MC] 09:46:32:265 GMT [THREAD 2668]  Drinks ConnectionReader::readerLoop() exiting
    [MC] 09:46:32:265 GMT [THREAD 2304]  Drinks Channel::close(readerLoop exited)

     

    any Idea ?.

     

    thanks

    Wednesday, April 18, 2007 9:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
     

    Hi

    I had to configure and enable web conferencing. (It was all in the manual *shrug*)

    According to OCS_EnterpriseEditionDeployment.doc page 35 I hadn’t enabled web conferencing.

    Doing this, then rebooted the server, then opened the LM client user accounts and tested the connection again, then the meet now button paired J and I’m now able to create Live Meetings using the communicator client.

    I still get the -2147016672  error when logging on to the website: https://<FQDN>/conf/int/login.aspx

     

    Kind regards

    Kenneth

     

     

    Here is the description from the OCS_EnterpriseEditionDeployment.doc document:

    To configure A/V and Web conferencing

    1.         Click Start, click Control Panel, click Administrative Tools, and then click Office Communications Server 2007.

    2.        Right-click the Forest node, click Properties, and then click Global Properties.

    3.        Click Meetings, and then do one of the following:

    ·         To allow the selected users to organize meetings that include anonymous participants, click Anonymous participants, and then click Allow users to invite anonymous participants.

    ·         To prevent the selected users from organizing meetings that include anonymous participants, click Anonymous participants, and then click Disallow users from inviting anonymous participants.

    ·         To allow only some users to organize meetings that include anonymous participants, click Anonymous participants, and then click Enforce per user. Ensure that you follow the procedures in the “Configure Users” section of this document to enable or disable this feature for individual users.

    Important

    By default, all users are allowed to organize meetings that include anonymous participants.


    4.        In the Policy Definition list, click the name of a policy, and then click Edit.

    5.        In the Edit Policy dialog box, select the Enable Web conferencing check box, and then change any or all of the settings shown in the table above, and then click OK.

    6.        Click Apply.

    7.        After you finish editing the features enabled by each policy, decide which policy to apply to meetings organized by users. Do one of the following:

    ·         To apply the same policy to all users, click Global policy, and then click the name of the policy that defines the features you want to enable for all users.

    ·         To apply different policies to different users, click Global policy, and then click Use per user policy. Ensure that you follow the procedures in the “Configure Users” section of this document to configure the meeting policy for individual users.

    8.        When you are finished, click OK.

    For more information about administering meeting features, refer to Microsoft Office Communications Server Beta 3 Administrator Guide.

    If you expect heavy audio/video traffic in your environment, you can optimize your network interface card settings to accommodate this volume. See Appendix F in this document for more information


    Wednesday, April 18, 2007 10:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi I already do that, that why I have the meet now button in the LMeeting client but when I click on it.

    It's not working .

     

    On the edge server I 've got this message:

     

    Failed to process data received from the client.

     

    Over the past 0 minutes Office Communication Server hs disconnect clients 1 time(s) as a result of invalid data being received on client connections....

     

    Resolution:

    Check and make sure that the connection came from a trustworthy client.

     

    I don't know how to make sure that the connection came from a trustworthy client, or how add one.

    Wednesday, April 18, 2007 1:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Kenneth,

    I just wanted to clarify your current status. Are you able to schedule Live Meetings, start LM from the OC client and use Meet Now, but are still getting this error?

     

    Hi Rol,

    Are you still having these issues? To make sure the connection is trustworthy, verify the certificate presented are trusted. Does the client trust the certificate on the server?

     

    Thursday, April 26, 2007 7:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am experiencing the same problem. I have setup the edge server and it communicates back the front end server. Meeting inside work properly but when an outside user connects I get the same error message. Any ideas what be appreciated.

    Thanks

    Friday, May 4, 2007 12:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello, the same problem

    Error Source: System.DirectoryServices
      Error Type: System.Runtime.InteropServices.COMException
      Error Message: An operations error occurred.

    Error Code: -2147016672

     

    Any ideas?

    Monday, May 7, 2007 9:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi , Thom

     

    I finaly found my mistake the problem com from the time zone.

    The Edge server was at the same date&time of the authers serveur but not the same time zone. (that's cause problems with universal time of course.)

     

    I think I say it in an auther thread with the description of my error.

     

    Thanks

    Thursday, May 10, 2007 7:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I now get this as well after moving to the Release Candidate. All is ok on the Beta 3 implementation, but if it try and login to https://OCSSERVER01/conf/int/Default.aspx type my credentials in and get:-

     

     

    Server Error

    A server error has occurred. Please contact the administrator.
    Error Source: System.DirectoryServices
    Error Type: System.Runtime.InteropServices.COMException
    Error Message: An operations error occurred.
    Error Code: -2147016672

     

    If I try and join a meeting, https://OCSSERVER01/conf/int/Join.aspx

     

    Server Error

    A server error has occurred. Please contact the administrator.
    Error Source: LcWmiConsumer.Managed
    Error Type: Microsoft.Rtc.Internal.Wmi.UnableToDetectMachineFullyQualifiedDnException
    Error Message: Exception of type 'Microsoft.Rtc.Internal.Wmi.UnableToDetectMachineFullyQualifiedDnException' was thrown

     

    Monday, June 25, 2007 6:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Scrub that, I had missed a step:-

     

    LcsCmd.exe /web /action:Activate /role:Meeting /poolname:<pool_name> /User:<user_name> /Password:<password>.

     

    All working now!

    Monday, June 25, 2007 6:51 PM