Unable to find Dynamic Shared Object section. Unable to add "LoadModule".
search cancel

Unable to find Dynamic Shared Object section. Unable to add "LoadModule".


Article ID: 109903


Updated On:


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


While trying to configure SiteMinder agent on Apache webserver , the following error is seen. Installation was successfull with 0 errors, getting below error only at the end of configuration part.

Installing... ------------- [==================|==================|==================|==================]
[ Unable to find Dynamic Shared Object section. Unable to add "LoadModule". Please see the installation guide for how to manually configure the httpd.conf file.


Release: Applicable to all the supported CA Siteminder WebAgents.
Component: SMAPC


WebAgent Configuration Wizard configures the Apache web server based on the comments only.

It is because, Configuration Wizard identifies the type (Ex: module, alias etc) of the elements in the 'httpd.conf' file by reading those comments only. 

Based on the comments, Configuration Wizard add/modify/delete a particular element in the 'httpd.conf' file. 

Ex: If we need a module (Ex: mod_foo.so) to be loaded; Configuration wizard identifies where all other modules are being loaded and add the same at the identified location based on the comments. The same way, aliases and directories also will be configured. 

There are two commented lines in each of two sections that the installer looks for. 

These are marked below with an arrow `->'; 


-># Dynamic Shared Object (DSO) Support 

# To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. 
# Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. 

# Example: 
-># LoadModule foo_module modules/mod_foo.so 


-> # AddHandler allows you to map certain file extensions to "handlers": 
# actions unrelated to filetype. These can be either built into the server 
# or added with the Action directive (see below) 

# To use CGI scripts outside of ScriptAliased directories: 
# (You will also need to add "ExecCGI" to the "Options" directive.) 

-> #AddHandler cgi-script .cgi 

# For type maps (negotiated resources): 
#AddHandler type-map var 

# Filters allow you to process content before it is sent to the client. 

# To parse .shtml files for server-side includes (SSI): 
# (You will also need to add "Includes" to the "Options" directive.) 

#AddType text/html .shtml 
#AddOutputFilter INCLUDES .shtml 

Adding the above in httpd.conf should result in a successful configuration of the agent.