Symantec Access Management

 View Only
  • 1.  arcotadmin error

    Posted May 28, 2018 08:21 AM
      |   view attached

    Hi all,


    What would be the cause of the error message below:

    "ERROR: admin.managers.RiskFortConfigurationUtil"

  • 2.  Re: arcotadmin error

    Posted May 31, 2018 06:47 AM

    Hi Neo,


    When are you getting this NullPointerException?

    Is this error coming only during specific operation or for all the operations?

    Is this error coming for all the administrator or only for Unauthorized administrator?

    Is this error coming in all the envs?




  • 3.  Re: arcotadmin error

    Posted Jun 06, 2018 02:17 AM

    Hi Sharana,

    The error occurs almost every minute.

    I believe that the error does not need activity on the Admin console for it to come up, because from the logs it has been occurring during midnight and we had no one working on the Admin console at the time.

    I do not think that the error is caused by administrators.

    No the error is only occurring in PRODUCTION, but on only one RiskMinder instance.





  • 4.  Re: arcotadmin error

    Posted Jun 05, 2018 03:45 PM

    Is this the error shown on browser console or in the logs ?

  • 5.  Re: arcotadmin error

    Posted Jun 06, 2018 02:19 AM

    The error is shown in the arcotadmin.log

  • 6.  Re: arcotadmin error
    Best Answer

    Broadcom Employee
    Posted Jun 07, 2018 05:01 PM

    Hi Neo, Please try restarting your case management server if this does not help also try recreating and then re-deploying the new arcotadmin.war ? 




  • 7.  Re: arcotadmin error

    Posted Jun 11, 2018 05:45 AM

    Hi Neo,


    Did you try to restart case management server as mentioned by Awijit?

    Did you try to re-deploy the working war file?



  • 8.  Re: arcotadmin error

    Posted Jun 12, 2018 08:41 AM


    I will try the above solution suggestions after hours when there is little traffic because the issue is happening on PRODUCTION.




  • 9.  Re: arcotadmin error

    Posted Jun 13, 2018 08:20 AM


    It looks like restarting the case management server did help  thanks.