none
Live Meeting Lockup on Windows 7 - Solution

    Question

  • This is just to pass along a discovery I made where my Windows 7 computer was freezing up solid when logging on to Live Meeting.

    The problem appears to have been in the AMD High Definition Audio driver. It looks like the first audio from Live Meeting (e.g., the Welcome sound) was hitting the driver which then hung.

    By disabling the AMD High Definition Audio driver (it is the latest version), I was able to avoid the crash.

    I'm not sure why I even have the AMD driver since there's a Realtek High Definition Audio controller that continues to work.

    Hope this FYI helps someone down the road.

    Ken

     

    Wednesday, October 05, 2011 4:20 PM

All replies

  • Hello,

     

    Then you may need to check if there are any update for the audio driver.

     

    Also check if there are any audio software installed. If so, please uninstall them to check if the issue persists.

     

    Thanks,

    Simon

    Monday, October 10, 2011 9:17 AM
  • We just started testing the May 2011 CU (8.0.6362.202) and also have reports that it now takes up to 50 seconds before Live Meeting is usable.  I reproduced this issue on HP EliteBook 6930p laptops running Windows Vista SP2.  The client hangs and then finally connects.  With v8.0.6362.201, Live Meeting opens and is usable within 15 seconds.

    We are using the latest driver available from HP:

    SoundMax Integrated Digital Audio
    Analog Devices
    - Driver Version: 6.10.1.5880

    Something clearly changed in Live Meeting 8.0.6362.202 that impacts audio.  Is there any release note or KB on this?

    Wednesday, October 12, 2011 1:27 PM
  • We have now confirmed the same issue with the Live Meeting May 2011 CU (8.0.6362.202) on three other PCs running exactly the same Windows Vista version.

    Dell D630 

    HP Elite Book 2530p 

    HP Desktop 8000 SFF and HP DC 7900 SFF

    If anyone has any further information, I would appreciate the feedback. 


    • Edited by PSaunders Thursday, October 13, 2011 9:24 AM
    Thursday, October 13, 2011 9:24 AM
  • Hi Paul,

    On further investigation of this it doesnt seem to be hardware specific, on investigating in the pwconsole-debug40.log the following is polling in the "Hang Period"

    [MC] 12:37:22:250 GMT [PID 1284] [THREAD 4940]  [I] [X-PSOM] placeware::HttpProxy::probeProxy: Probing proxy name for host = nestle.com
    [MC] 12:37:22:275 GMT [PID 1284] [THREAD 4940]  [D] placeware::InetUtils::HttpProxyCallback: Ignoring callback for unrecognized/stale handle = 13369348, expectedHandle = 0 with dwInternetStatus = 60
    [MC] 12:37:22:276 GMT [PID 1284] [THREAD 4940]  [D] placeware::InetUtils::HttpProxyCallback: Ignoring callback for unrecognized/stale handle = 13369352, expectedHandle = 0 with dwInternetStatus = 60
    [MC] 12:37:22:276 GMT [PID 1284] [THREAD 4940]  [D] placeware::InetUtils::GetProxyForHost: HttpSendRequest returned 0, and GetLastError = 997 (Overlapped I/O operation is in progress.) [expected]
    [MC] 12:37:22:276 GMT [PID 1284] [THREAD 4940]  [I] placeware::InetUtils::GetProxyForHost: Waiting 1000000 ms for proxyDetectionDoneEvent to be set...
    [MC] 12:37:22:278 GMT [PID 1284] [THREAD 3036]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 80
    [MC] 12:37:22:355 GMT [PID 1284] [THREAD 3036]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 320
    [MC] 12:37:22:355 GMT [PID 1284] [THREAD 3036]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 10
    [MC] 12:37:22:356 GMT [PID 1284] [THREAD 3036]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 11
    [MC] 12:37:22:356 GMT [PID 1284] [THREAD 3036]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 20
    [MC] 12:37:43:375 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 20
    [MC] 12:37:47:400 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 20
    [MC] 12:37:49:070 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 20
    [MC] 12:38:10:048 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 20
    [MC] 12:38:31:077 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: Callback for expected context = 2844 and expectedHandle = 13369356 with dwInternetStatus = 100
    [MC] 12:38:31:077 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: Got a status which indicates we won't get the proxy info anymore.
    [MC] 12:38:31:077 GMT [PID 1284] [THREAD 1388]  [I] placeware::InetUtils::HttpProxyCallback: proxyDetectionDoneEvent set. SetEvent result = 1
    [MC] 12:38:31:077 GMT [PID 1284] [THREAD 4940]  [I] placeware::InetUtils::GetProxyForHost: Waiting over

    Does anybody know a way or an explanation what is causing this???

     

    Thursday, October 27, 2011 12:40 PM
  • check this link

    http://social.technet.microsoft.com/Forums/en-US/olmexp/thread/7b0dd67f-02af-46d6-bee7-e1d95cc63688

    Monday, April 02, 2012 5:08 PM
  • I had this message in the log as well:

    placeware::InetUtils::GetProxyForHost: Waiting 1000000 ms for proxyDetectionDoneEvent to be set...

    First thing I looked for were the proxy settings, but they were fine.

    But, somehow IE had gone 'offline'. By going online again (just by trying to browse to cnn.com), the Live Meeting came to life!

    Hope this helps someone.

    Monday, November 26, 2012 4:53 PM