Service Virtualization

 View Only
  • 1.  registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Posted Feb 16, 2024 03:52 AM

    Hello,

    I'm trying to start registry with User schema for DevTest 10.6 version which fails with below pasted ED error. The same works great when installed using admin schema.

    I did give all necessary grant (in admin) and synonyms (in user) permissions. Not sure where it went wrong? please help.

    2024-02-16 08:40:59,661Z (08:40) [main] ERROR com.itko.lisa.coordinator.TestRegistryImpl -

    The Enterprise Dashboard Server at 'https://*********:1506'

    could not be contacted, and no current activation was found in the local

    activation cache for this registry.

    This registry will not be allowed to start until it can be activated by a

    valid Enterprise Dashboard Server.

    Please contact your DevTest System Administrator or contact

    CA Customer Support for more information.

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     -

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - The Enterprise Dashboard Server at 'https://*********:1506'

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - could not be contacted, and no current activation was found in the local

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - activation cache for this registry.

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     -

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - This registry will not be allowed to start until it can be activated by a

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - valid Enterprise Dashboard Server.

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     -

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - Please contact your DevTest System Administrator or contact

    2024-02-16 08:40:59,662Z (08:40) [main] ERROR System.err                     - CA Customer Support for more information.

    2024-02-16 08:40:59,663Z (08:40) [Thread-0] ERROR System.err                     -

    2024-02-16 08:40:59,664Z (08:40) [Thread-9] INFO  com.itko.lisa.net.ActiveMQFactory - Closing AMQ connections



    ------------------------------
    Raji
    ------------------------------


  • 2.  RE: registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Broadcom Employee
    Posted Feb 16, 2024 09:14 AM

    Make sure your Enterprise Dashboard is running. The license might have expired.




  • 3.  RE: registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Posted Feb 16, 2024 09:43 AM

    No, ED license is valid and Registry is all fine with ADMIN schema.



    ------------------------------
    Raji
    ------------------------------



  • 4.  RE: registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Broadcom Employee
    Posted Feb 16, 2024 09:53 AM

    Naga,  looks like  you are trying to connect to  an HTTPS endpoint  : 'https://*********:1506'  for enterprise Dashboard

    can you verify this property in lisa.properties  or local.properties  is set to true ?

    dradis.webserver.https.enabled=true 




  • 5.  RE: registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Posted Feb 16, 2024 09:57 AM

    yes, https is enabled and works fine with same properties files settings with admin schema.  Only just when i switched common pool settings with user schema, it fails.



    ------------------------------
    Raji
    ------------------------------



  • 6.  RE: registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Broadcom Employee
    Posted Feb 16, 2024 10:02 AM

    Naga,  what version of Devtest are you seeing this issue? Please upload the following files :  ED logs , Registry logs,   dradis.properties and site.properties..  You can remove the DB server names from the properties file..  

    if you are on a supported version (10.7.2 and above) ,  please open a ticket with Broadcom support. 




  • 7.  RE: registry not coming up with User schema saying unable to reach ED, where in admin schema works fine

    Posted Feb 16, 2024 10:57 AM

    10.6 and no error on ED and Registry when switched to User schema.



    ------------------------------
    Raji
    ------------------------------