Web agent configuration wizard cannot find installed Apache web server.
search cancel

Web agent configuration wizard cannot find installed Apache web server.


Article ID: 53707


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On


Web agent configuration wizard does not display a checkbox for the installed Apache web server despite the fact the web server been installed on the system and is functioning normally.


Component: SMAPC


IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to create back up of the registry and ensure that you understand how to restore the registry if a problem may occur.
For more information about how to back up, restore, and edit the registry, please review the relevant Microsoft Knowledge Base articles on support.microsoft.com.

The web agent configuration wizard uses the Windows registry to locate the Apache servers root directory.

To do this the configuration agents code tries to directly access HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache and look for supported version numbers in the registry. Because it utilizes this method several potential problems can arise:

  1. The registry path could be invalid

    By default the code looks in HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache or HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Apache if path doesn't exist the configuration wizard won't find the servers.

    This could happen through either:
    • An Administrator deleting the registry branch.

    • An alternate name been used for this registry branch.

  2. The ServerRoot registry entry could be missing

    If the ServerRoot registry entry has been renamed, or is missing the configuration wizard will be unable to determine Apache's location.

  3. The ServerRoot registry entry could be pointing to an invalid path

    If the Apache web server root has been moved without updating the value stored in ServerRoot Siteminder will detect the path is invalid and subsequently ignore it.

To resolve these problems, create the following registry entries:

Create new key called Apache Group under HKEY_LOCAL_MACHINE\SOFTWARE\

Under the Apache Group key you just created create a new key named after the Apache version number (for example 2.0.63 for 2.0.63).

Under the version numbered key you just created add a dword value called shared the value should be 1.

Under the version numbered key you just created add a string value called ServerRoot the value should contain the full path of the Apache server root, for example C:\Program Files\Apache Group\Apache2\

After making these changes attempt to run the web agent configuration wizard again, no server restart is necessary.


For 12.52 SP1 CR11 , please see the following KB --> https://knowledge.broadcom.com/external/article?articleId=206180

Additional Information

Once Web agent configuration is done, see also the below article.
Article ID: 28710 - SiteMinder WA 12.5x + Apache 2.4/2.2 (x64) support on Windows