Microsoft KB Archive/938770

= The Windows-based Live Meeting 2005 console does not load after a successful installation =

Article ID: 938770

Article Last Modified on 11/12/2007

-

APPLIES TO


 * Microsoft Office Live Meeting 2005

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario. When you try to join a Microsoft Office Live Meeting 2005 session, you are prompted to install the Microsoft Windows-based Live Meeting 2005 console. You have permissions to install programs on the computer. Then, you perform a successfully installation of the Windows-based Live Meeting 2005 console. However, when you try to rejoin the meeting, you are prompted to install the Live Meeting 2005 console again. In this scenario, if you click No to cancel the installation, you are prompted to join the meeting by using the Web-based Live Meeting 2005 console.

Additionally, when other users who experience this issue try to log on to the domain by using your computer, the users can successfully install the Windows-based Live Meeting 2005 console on the computer and then join the meeting. Similarly, you can log on to any of the affected computers and successfully install the Windows-based Live Meeting 2005 console on the computer and then join the meeting.



CAUSE
This issue occurs if the Live Meeting 2005 console registry entries for the current user include pointers to an invalid directory path.

This issue may occur if registry entries of an earlier version of the Windows-based Live Meeting console are not overwritten when you updated to a later version of the Windows-based Live Meeting console.

This issue affects only the current user. Other users who log on to affected computer do not experience this issue.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, follow these steps:  Remove the Windows-based Live Meeting 2005 console from the computer if the program is included in the list of installed programs. Download the Windows-based Live Meeting console, and then save it locally on the affected computer. To download the Windows-based Live Meeting 2005 console, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=ba25749f-ca2f-451b-a20f-205896a79e60&displaylang=en

 At the command prompt, type the following command to install the Live Meeting console:

.msi /l*v \ .txt

Note This command also outputs verbose logging to the .txt log file. is the path where the Live Meeting console program is stored locally. is the path where you want to store the .txt log file. After the Live Meeting console installation is complete, download the Microsoft Product Support (MPS) Reporting Tool, and then run the MPS Reporting Tool. To download the MPS Reporting Tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f-88b7-f9c79b7306c0&displaylang=en

Note Make sure that you are logged on to the affected computer. Have a second user download the MPS Reporting Tool and then run the MPS Reporting Tool on a computer that is not experiencing this issue. Export the  registry subkey on the affected computer to a text file.</li> Extract the two MPS reports to separate directories.</li> In Event Viewer, import the other user's system event log.</li> Click User, click Filter on the View menu, and then make sure that only the Error check box is selected.</li> In the Event source list, click DCOM, and then click OK.</li> In the filtered list, double-click the items, and then locate an entry that resembles the following:

Unable to start a DCOM Server: { }.

The error: &quot;The system cannot find the file specified.&quot; Happened while starting this command: &quot;C:\PROGRA~1\MICROS~4\LIVEME~2\Console\701503~1.28\LM7LAU~1.EXE&quot; -Embedding

Note { } is the CLSID for the Live Meeting 7 launcher. The error means that a registry entry on the affected user profile is pointing to the wrong directory location for the Lm7launcher.exe file.</li> To determine the current version of the Live Meeting launcher, search the local hard disk drive for files that contain the { }. If more than one file is found, each file will be in a directory that is stored with a version number. The highest numbered directory holds the current version of the Live Meeting launcher.</li> Start Registry Editor, and then locate the following registry key:

</li> Export the { } subkey to a text file. You may want to restore this registry subkey, if it is necessary.</li> Right-click the { } subkey, and then click Delete. Click Yes when you are prompted to confirm the deletion.</li> Verify that you can successfully join a test Live Meeting session.</li></ol>

Additional query words: 1003 registry damaged missing directory console does not load

Keywords: kbtshoot kbexpertisebeginner KB938770

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.