Symantec Access Management

Expand all | Collapse all

SM Admin UI error

  • 1.  SM Admin UI error

    Posted 04-21-2014 05:54 AM

    Hi Team,

    I'm trying to register Admin UI with Policy server, but it is throwing following error. Please suggest me here what to do?

    c:\CA\siteminder\bin>XPSRegClient siteminder -adminui-setup -t 60
    [XPSRegClient - XPS Version 12.5.0000.732]
    Log output: XPSRegClient.2014-04-21_151614.log
    Confirm password:
    Initializing system, please wait...
    CA-XPS:LDAP0014(ERROR) : Error occurred during "SearchExt" for "(&(xpsNumber=*)(
    !(xpsTombstone=*)))", text: Unavailable critical extension
    CA-XPS:LDAP0014(ERROR) : Error occurred during "Modify" for "xpsParameter=CA.XPS
    c=com", text: No such attribute
    CA-XPS:XPSIO024(ERROR) : Save Policy Store ID failed.
    CA-XPS:UTIL0005(FATAL) : Unable to initialize the XPS library.

  • 2.  RE: SM Admin UI error

    Posted 04-21-2014 09:20 AM

    sounds like the search is potentially off.

    sounds familliar. maybe a support guru could search their db. might be known.

  • 3.  Re: SM Admin UI error

    Posted 06-17-2014 06:57 AM

    Have a look at this KB atricle: TEC586861, on support site.


    Also you should reindex the below attributes, you can use the below command as it is:


    dsadm reindex -b -t xpsNumber -t xpsValue -t xpsSortKey -t xpsCategory -t xpsParameter -t xpsIndexedObject -t xpsTombstone /opt/LDAP-R12.51 policysvr4


    Once the policy store configuration completes you should reindex the complete netegrity tree.

  • 4.  Re: SM Admin UI error

    Posted 06-19-2014 08:08 PM

    Hi Sandeep,


    Could you clarify few things :

    - What is your policy store ? TEC586861  and the re-indexing command that Vikas provided is applicable only to Oracle Directory Server/SunOne Directory

    - Is your policy server up and running without any errors ? That error indicates that you should have a problem with even Policy server

    - How about other XPS tools like XPSExplorer/XPSConfig etc ? Are they running fine ?


    Depending upon answers to above, we might be able to provide you suitable solution.

    Additionally, you can also check your ldap policy store access/error logs to see what error is thrown when this particular search is run.