Threshold Advisor install on a 64 bit Windows 2008 (Release 1) machine failed due to missing IIS 32 bit registry entries.

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView Infrastructure


    APPLIES TO:

    MainView Infrastructure



    PROBLEM:

     

    Threshold Advisor install on a 64 bit Windows 2008 (Release 1) machine failed with the following errors in the TA install log...

    8-20-2013 09:58:58 -- INFORMATION -- Unable to find the ASPNET key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\Components.
    8-20-2013 09:58:58 -- INFORMATION -- Unable to find the WindowsAuthentication key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\Components.
    8-20-2013 09:58:58 -- INFORMATION -- Unable to find the Metabase key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp\Components.
    8-20-2013 09:58:58 -- INFORMATION -- Checking the state of service: MSMQ
    8-20-2013 09:58:58 -- INFORMATION -- MSMQ service state: Running
    8-20-2013 09:58:59 -- INFORMATION -- Searching for MS .NET Framework 3.5 Service Pack Version
    8-20-2013 09:58:59 -- INFORMATION -- Found the SP key with value: 1
    8-20-2013 09:58:59 -- INFORMATION -- ----- SP1 is present on the system
    8-20-2013 09:58:59 -- INFORMATION -- Searching for the Full MS .NET Framework 4
    8-20-2013 09:58:59 -- SEVERE -- ASP.NET 4.0 is not installed and is required by BMC MainView Threshold Advisor. Please install ASP.NET 4.0 prior to installing BMC MainView Threshold Advisor.
    8-20-2013 09:58:59 -- WARNING -- Windows Authentication is not installed within IIS. Windows Authentication is required to run BMC MainView Threshold Advisor. The installation of BMC MainView Threshold Advisor will continue. After the installation has completed install Windows Authentication within IIS.
    8-20-2013 09:58:59 -- SEVERE -- IIS Metabase is not installed within IIS. BMC MainView Threshold Advisor requires the IIS Metabase component. Please install the IIS Metabase component.
    8-20-2013 09:58:59 -- INFORMATION -- Searching for MS .NET Framework 3.5 Service Pack Version
    8-20-2013 09:58:59 -- INFORMATION -- Searching for the Full MS .NET Framework 4
    8-20-2013 09:58:59 -- INFORMATION -- The Full MS .NET Framework 4 is present on the system
    8-20-2013 10:20:50 -- SEVERE -- Product did not meet requirements...
    8-20-2013 10:20:50 -- SEVERE -- Installation aborted...


     

     


    SOLUTION:

     

    Legacy ID:KA401756

      

    The problem is due to a Microsoft bug where the 32 bit IIS registry entries are not being written.

    This problem dates way back to Windows Vista and Windows 2008 Server. Both Windows Vista and Windows 2008 Server share the same core OS components, and the root of the problem is a technology known as "Registry Reflection" in the core layers. The intention of "RR" was simple yet problematic, as any entries written to the 64-bit Windows registry were supposed to be automatically copied to the same location in the 32-bit registry on the server for 32-bit applications, but that was not always the case. Even though the negative response from the development community was overwhelming, Microsoft never officially acknowledged the issue, but it is discussed in countless "forums" on the web. The issue was eventually resolved with the release of Windows 7 and Windows 2008 Server R2 as both of "these" OS's share the same core OS components. Microsoft "axed" the Registry Reflection technology, and now allows 64-bit and 32-bit application to share the same registry locations without issue. As a side note, Windows 8, and Windows 2012 Server are built on the Windows7/Windows 2008 Server R2 components so this is no longer an issue moving forward.

    Unfortunately the CDB/TA documentation did not properly indicate the 32-bit requirement of Windows 2008 Server (Release 1). As stated above the issue is fixed in Windows 2008 R2 (Release 2).

    This would NOT be a problem in the following Windows versions:

    Windows 2012 Server
    Windows 2008 Server R2
    Windows 2008 Server SP1 or higher (32-bit only)
    Windows 2003 Server R2 SP2 or higher (32-bit only)

    The solution to this issue would be to install Threshold Advisor, CDB Services and CDB Workflow on one of the above Windows OS versions.

      
    Related Products:  
       
    1. MainView Infrastructure

     


    Article Number:

    000088846


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles