Symantec Access Management

 View Only
  • 1.  Unable to restart weabgent

    Posted Apr 16, 2019 02:04 AM

    While restarting webagent I am getting below error. WebAgent was working fine but now it's throwing below error.


    [13548/11460][Tue Apr 16 2019 11:10:54][LLAWorkerProcess.cpp:1531][INFO][sm-AgentFramework-00680] LLAWP: Initialization complete.
    [13548/8156][Tue Apr 16 2019 11:10:54][LLAWPMsgBus.cpp:419][INFO][sm-AgentFramework-00660] LLAWP: Message bus initialized.
    [6268/12640][Tue Apr 16 2019 11:10:55][CSmLowLevelAgent.cpp:5206][INFO][sm-AgentFramework-00510] LLA: Logging initialized.
    [6268/12640][Tue Apr 16 2019 11:10:55][CSmPluginManager.cpp:187][ERROR][sm-AgentFramework-00120] ADMIN: SmDSOLoadLibrary failed to load plugin 'C:\Program Files\CA\webagent\win64\bin\HttpPlugin.dll'.
    [6268/12640][Tue Apr 16 2019 11:10:55][CSmPluginManager.cpp:96][ERROR][sm-AgentFramework-00110] ADMIN: Unable to load plugin 'C:\Program Files\CA\webagent\win64\bin\HttpPlugin.dll'.
    [6268/12640][Tue Apr 16 2019 11:10:55][CSmAdminManager.cpp:190][ERROR][sm-AgentFramework-00270] ADMIN: Unable to get plugin context from the Plugin Manager.
    [6268/12640][Tue Apr 16 2019 11:10:55][CSmHighLevelAgent.cpp:122][ERROR][sm-AgentFramework-00400] HLA: Failed to initialize 'Administration Manager'.


    From logs I could see that its not able to load HttpPlugin.dll , but I didn't modify anything.



    Vivek Thakur

  • 2.  Re: Unable to restart weabgent

    Posted Apr 17, 2019 04:21 PM


    With this agent on windows, are there any messages in the event viewer?

    What the OS version and web server (IIS?) version? 

    What is the version of the web agent?

    I'm just looking to confirm for compatibility. 


    James Atchley
    Principal Support Engineer  - SSO 
    CA a Broadcom Company 

  • 3.  Re: Unable to restart weabgent

    Posted Apr 22, 2019 01:36 AM

    Hello James,


    Please find the details below.


    OS Version : Windows 8.1

    IIS Version : 6.2

    WebAgent Version : 12.52 (Full Version : FullVersion=


    Error Log in event viewer Logs:


    SiteMinder agent has encountered initialization errors and will not service requests.


    And While accessing the resource protected by siteminder we are getting 500: Server Error




  • 4.  Re: Unable to restart weabgent

    Posted Apr 23, 2019 03:17 AM

    Hello James Atchley,


    Any Update.




  • 5.  Re: Unable to restart weabgent

    Posted Apr 24, 2019 05:58 PM


    While you might be able to get this working on the OS that your working with, it's not a supported use case.

    The supported Windows OS's would be...

    The 500 is occurring do the agent not starting properly. 


    The agent not starting could be a number of issue even if we rule out the OS Release. 


    What could try is to attempt to start the agent via command line. 
    From the agent install, naviagte to the /CA/webagent/win64/bin

    Run LLAWP without any switches. 

    You will see the command requirements. 


    llawp <configfile> -<Web Platform> <-a> <-c>
    <configfile> : Path to valid WebAgent.conf file.
    <Web Platform>: -APACHE20, -APACHE22, -APACHE24, -ISAPI60, -IIS70, -IIS75, -IIS80, -IIS100 -SPS60, -SPAGENT, -SUNONE.
    <-a> : Automatic shutdown - Shutdown when the LLAWP clientlist goes to 0.
    <-c> : Cache Client - LLAWP attaches to caches without attempting to create them
    <-shutdown> : Shutdown the running worker process associated with a WebAgent.conf file.
    NOTE: Configuration filenames and version strings that contain spaces
    should be surrounded by quotes. Example: "value with spaces"

    So you command would something like ... 

    llawp %PathTo%\webagent.conf -IIS70. 

    If the prompt generates a 'rolling' message, the agent started. 
    If you configured logs in the ACO, those should be generated. 

    If the command, just drops to the next line, then the agent didn't start. 

    If it does start and there are logs, then the issue is within the configuration or capability of the release of IIS. 
    If it doesnn't start at all, then the issue might be with the installation, general configuration of the agent or the overall support of the OS. 

    Even if you go through all that and get it to work, then you will still not be in a supported configuration and unable to work with SSO Support going forward. 


    Therefore,  let's start with a support OS and work forward from there. 

    If you still have the same issue, we would need to review the event viewer log and the SMPS Logs to see if we can get a better take on the issue. 

    You might want to create a formal case with Broadcom SSO Support if needed.