Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Meet Now functionality will be ... HIDDEN! RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I get an error message when I try to Test connection.

    "An error occured while executing this command. I this problem persist, please contact your Live Meeting administrator."

     

    Backround:

    If I test the connection and get the error but hit ok anyways, I can start Live Meeting from IM with no problems everything works include A/V. I am manually specifing the server in Live Meeting and using a GPO for Communicator server address.(This is because SIP domain used is our external) We ran Beta release fine even with accessedge servers and no major issue.

    Meeting policy enabled, sign-in SIP URI, pool DNS name registered and resolvable (IM uses it), Web Conferencing Validation succeeds(on server) no issues at all, Web components succeed as well.

     

    I deployed Beta when it was out and I got it working properly even with accessedge servers, so I am familiar we the requirements. We are now using the Volume License software.

     

    Client Log file:

    [MC] 12:33:12:232 GMT [PID 3376] [THREAD 3256]  Angel Log file started: 2007/12/18 12:33:12:232 GMT
    [MC] 12:33:12:232 GMT [PID 3376] [THREAD 3256]  [P] Starting Perf Logger: Measured Qp Frequency = 3579545
    [MC] 12:33:12:232 GMT [PID 3376] [THREAD 3256]  [P] SEQ#2,wWinMain::WinMainTimer start,,,
    [MC] 12:33:12:292 GMT [PID 3376] [THREAD 3256]  [P] SEQ#2,wWinMain::WinMainTimer stop,134,,
    [MC] 12:33:12:292 GMT [PID 3376] [THREAD 3256]  [P] SEQ#3,ConsoleEntryPoint::ConsoleEntryPointTimer start,,,
    [MC] 12:33:12:302 GMT [PID 3376] [THREAD 3256]  [P] SEQ#3,ConsoleEntryPoint::ConsoleEntryPointTimer stop,3159,,
    [MC] 12:33:12:302 GMT [PID 3376] [THREAD 3256]  [P] SEQ#4,placeware::LMClientApp::Run::LMClientAppRunTimer start,,,
    [MC] 12:33:12:302 GMT [PID 3376] [THREAD 3256]  Drinks CPWResources::negotiateLanguage - user default LANGID: 1033
    [MC] 12:33:12:302 GMT [PID 3376] [THREAD 3256]  Drinks CPWResources::Initialize - negotiated LANGID: 1033
    [MC] 12:33:12:302 GMT [PID 3376] [THREAD 3256]  Drinks CPWResources:Tongue TiedetCRTLocale - user default LCID: 1033, Setting language as: ENU ... SUCCESS!
    [MC] 12:33:12:342 GMT [PID 3376] [THREAD 3256]  [P] SEQ#4,placeware::LMClientApp::Run::LMClientAppRunTimer stop,43404,,
    [MC] 12:33:12:372 GMT [PID 3376] [THREAD 3256]  [P] SEQ#5,placeware::ConsoleConfApiB::ConsoleConfApiB::ConfApiInitTimer start,,,
    [MC] 12:33:12:382 GMT [PID 3376] [THREAD 3256]  [P] SEQ#5,placeware::ConsoleConfApiB::ConsoleConfApiB::ConfApiInitTimer stop,10214,,
    [MC] 12:33:12:382 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:12:382 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:12:382 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:12:382 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured service: no
    [MC] 12:33:12:382 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::CPreMeetingDialog::refreshMeetNowDeploymentType Meet Now functionality will be ... HIDDEN    !
    [MC] 12:33:14:255 GMT [PID 3376] [THREAD 3256]  Drinks [X-UI] ToolBar Button Clicked: ID=27173 ToolTip=
    [MC] 12:33:14:255 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:14:255 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::getPreferredDeploymentType User's preferred deployment type is ...  server
    [MC] 12:33:14:255 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::getPreferredDeploymentType User's preferred deployment type is ...  server
    [MC] 12:33:20:425 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:20:425 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:20:425 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured server: no
    [MC] 12:33:20:425 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::ConsoleConfApiB::isConfigured service: no
    [MC] 12:33:20:425 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::CPreMeetingDialog::refreshMeetNowDeploymentType Meet Now functionality will be ... HIDDEN!
    [MC] 12:33:21:807 GMT [PID 3376] [THREAD 3256]  Drinks [X-UI] ToolBar Button Clicked: ID=27132 ToolTip=
    [MC] 12:33:21:807 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::CFrameWrapper:SurprisenCloseClicked
    [MC] 12:33:21:817 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::CFrameWrapper:SurprisenClose
    [MC] 12:33:21:827 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::CFrameClient:Tongue Tiedhutdown
    [MC] 12:33:21:827 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] placeware::CMeetingInstance::UserInitiatedDisconnect
    [MC] 12:33:21:827 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] CMeetingInstance::UserInitiatedDisconnect - starting Disconnect
    [MC] 12:33:21:837 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] CMeetingInstance:Big Smileisconnect begins, graceful = true
    [MC] 12:33:21:837 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] CMeetingInstance:Big Smileisconnect firing disconnect complete event.
    [MC] 12:33:21:857 GMT [PID 3376] [THREAD 3256]  Drinks [X-JE] CMeetingInstance:Big Smileisconnect ends, graceful = true
    [MC] 12:33:21:927 GMT [PID 3376] [THREAD 3256]  Drinks [X-PSOM] MessageQueue::~MessageQueue() - max queue size was 1

     

    Thanks for the assistance.

    Tuesday, December 18, 2007 2:05 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    OK guys, I called Microsoft and they spend sometime going over everything doing all the same tests that I did, collecting logs and all that,,, they found out nothing. Gave me unreleased clients and all. But I final figured it out, with no help from Microsoft and when I asked for a credit for the inicident they wouldn't return my e-mail, I even told them I would give them the answer for future use, but alass they will not respond now. So here is the answer to my issue and I hope it saves someone else many hours of work and maybe a useless incident call.

     

    After narrowing down the failure to the client computer, I found a computer that it worked on (brand new rebuild image) and used another laptop with the standard image that did not work. I ran filemon and regmon and after many lines (many as is hundreds) of comparing and eliminating I found the problem. On the system that didn't work LMclient was looking for msxml3.dll in the "C:\WINDOWS\Downloaded Program Files\" folder and in the one that was working it was looking for and finding msxml3.dll in the "C:\WINDOWS\system32\" folder. So I  "regsvr32 C:\WINDOWS\system32\msxml3.dll"

    and now everything works great. Must have been some kind of software update or push that messed up the location of that DLL.

    So there it is, hope it fixes your issues. Also make sure that the file exists in "C:\WINDOWS\system32\"    ...

    Wednesday, January 2, 2008 1:00 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    OK guys, I called Microsoft and they spend sometime going over everything doing all the same tests that I did, collecting logs and all that,,, they found out nothing. Gave me unreleased clients and all. But I final figured it out, with no help from Microsoft and when I asked for a credit for the inicident they wouldn't return my e-mail, I even told them I would give them the answer for future use, but alass they will not respond now. So here is the answer to my issue and I hope it saves someone else many hours of work and maybe a useless incident call.

     

    After narrowing down the failure to the client computer, I found a computer that it worked on (brand new rebuild image) and used another laptop with the standard image that did not work. I ran filemon and regmon and after many lines (many as is hundreds) of comparing and eliminating I found the problem. On the system that didn't work LMclient was looking for msxml3.dll in the "C:\WINDOWS\Downloaded Program Files\" folder and in the one that was working it was looking for and finding msxml3.dll in the "C:\WINDOWS\system32\" folder. So I  "regsvr32 C:\WINDOWS\system32\msxml3.dll"

    and now everything works great. Must have been some kind of software update or push that messed up the location of that DLL.

    So there it is, hope it fixes your issues. Also make sure that the file exists in "C:\WINDOWS\system32\"    ...

    Wednesday, January 2, 2008 1:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This solution didnt work for me.

    It worked in the lab though, but production environment isnt giving anything.

    i get thesame logs as the one above. wmi settings are right, urls configured and all.

    all i get is an error specifying .......

    "Live meeting can not connect to the meeting.

    Wait a few moments and then try again......."

     

     

    Tuesday, February 5, 2008 4:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Undermine, Thanks!
    Your fix saved the day here! I was having a bad time trying to compare two systems too, one that worked and one that didnt. Thanks again.
    Monday, September 14, 2009 11:43 AM