Layer7 Access Management

Expand all | Collapse all

Multiple LLAWP Process in SM WA Login Server

Jump to Best Answer
  • 1.  Multiple LLAWP Process in SM WA Login Server

    Posted 06-27-2016 11:24 PM

    In our Production SiteMinder login server (Windows Server 2008 R2 SP1) (CA SM Web Agent Version=12.52 ), suddenly both the LLAWP32.exe *32 and the LLAWP processes are running, and I can see the below event viewer errors and information.

     

    Event Viewer Logs:

    Event ID: 3 (Error)

    Unable to load SiteMinder host configuration object or host configuration file.

    D:\Program Files\CA\webagent\win64\config\SmHost.conf

    Event ID: 21 (Error)

    Failed to initialize the configuration manager.

    LLAWP unable to get configuration, exiting.

     

    And then, the recent log is,

     

    Event ID: 22 (Information)

    The description for Event ID 22 from source SiteMinder Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Duplicate LLAWP processes not allowed, exiting.

    the message resource is present but the message is not found in the string/message table

     

    Please give some suggestions. Thank you all.



  • 2.  Re: Multiple LLAWP Process in SM WA Login Server

    Posted 06-28-2016 01:02 PM

    Any CR?



  • 3.  Re: Multiple LLAWP Process in SM WA Login Server
    Best Answer

    Posted 07-06-2016 01:44 AM

    Hi Praveenkumar Ravichandran,

     

    One of the issue which would result in duplicate LLAWP has been fixed in 12.52 SP1 CR2. see details below :

    71834 Agent on IIS 7.5 continuously restarts after second web site is added to the web server.

     

    Detailed list of issue fixes on CR2 can be seen here :

    SSO Web Agent r12.52 Defect Fixes History

     

    So, if you are using web agent version prior to 12.52 SP1 CR2 , I would suggest to upgrade to CR2 at minimum and see if that resolves your issue.

     

    Cheers,

    Ujwol

    Ujwol's Single Sign-On Blog