Installation is one of the first places in which help may be required if an error occurs. When seemingly silent failures occur during installation, activation, or preparation steps during deployment, installation information is the first place to look.
Direct from the Source: Diagnosing Setup failures
Nirav Kamdar
Principal Development Lead, Office Communications Server
Setup logs are located under %TEMP% and have either the .log (for Microsoft Installer [MSI] logs) or .html extension (for activation/prep failures). In MSI logs, look for the phrase value 3 (MSI errors are cryptic, and this is a quick method to locate them). The HTML logs are self explanatory and can be expanded to the point of the failure. LcsCmd’s CheckXXState is usually also helpful. For example, to check whether the A/V multipoint control unit (MCU) is activated, you can run LcsCmd /mcu /action:CheckLcServerState /role:AVMCU.
As explained earlier, the setup operation will generate an accompanying HTML file. Occasionally, the following question is asked: What happens during schema prep, forest prep, or similar setup operations? If you have the HTML file that has the respective setup operations, all the information you need is there.
Another frequently asked question is: How do I find the root cause for setup failure? One way to research the problem is to open the HTML logs in Internet Explorer and expand the contents of the file. Scroll to the bottom of the file and start moving up. After you see the first occurrence of the issue, you are at the right starting point. Carefully analyze the action information and execution result for this issue because both can provide valuable troubleshooting information and hints.
18.217.15.45