Service Virtualization

Expand all | Collapse all

User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

  • 1.  User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 11-01-2016 06:20 AM
    • Our DevgTest Registry server is running in remote location(onsite), 
    • We are trying to launch the workstation from offshore by providing remote registry server ip (tcp://<<remote registry server ip>>:2010/Registry)
    • After that, it is asking for credentials and we provide credentials(admin/admin), we are all using default common credentials(admin/admin)
    • After login we are getting  User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]
    • We are able to launch VSE Console in the same offshore machine, but not able to connect the workstation
    • Please help us to resolve this issue , we are struggling with this issue last two weeks

     

    Please find the Offshore work station error Log below

    com.itko.lisa.gui.TestAdmin - Preflighting database
    2016-11-01 09:09:05,604Z (14:39) [Preflighting database] INFO com.itko.lisa.gui.TestAdmin - Database preflight completed
    2016-11-01 09:09:09,406Z (14:39) [ProcDlgThreadCallbk@31c19bee] INFO org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [applicationContext-security.xml]
    2016-11-01 09:09:09,516Z (14:39) [ProcDlgThreadCallbk@31c19bee] INFO org.springframework.context.support.GenericXmlApplicationContext - Refreshing org.springframework.context.support.GenericXmlApplicationContext@2b2012c5: startup date [Tue Nov 01 14:39:09 IST 2016]; root of context hierarchy
    2016-11-01 09:09:11,584Z (14:39) [ProcDlgThreadCallbk@31c19bee] INFO com.itko.lisa.utils.db.ConnectionPoolManager - Created pool named common
    2016-11-01 09:09:11,600Z (14:39) [ProcDlgThreadCallbk@31c19bee] INFO org.eclipse.persistence - EclipseLink, version: Eclipse Persistence Services - 2.3.2.v20111125-r10461
    2016-11-01 09:10:18,649Z (14:40) [ProcDlgThreadCallbk@31c19bee] ERROR com.itko.lisa.acl.utils.AclJpaUtil - Could not configure database persistence for unit: itko-acl
    javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Connections could not be acquired from the underlying database!
    Error Code: 0
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:517)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
    at com.itko.lisa.acl.utils.AclJpaUtil.updateCacheExpirationPolicy(AclJpaUtil.java:1258)
    at com.itko.lisa.acl.utils.AclJpaUtil.setCacheTimeoutMillis(AclJpaUtil.java:1254)
    at com.itko.lisa.acl.utils.AclJpaUtil.<init>(AclJpaUtil.java:145)
    at com.itko.lisa.acl.utils.AclJpaUtil$1.initialValue(AclJpaUtil.java:62)
    at com.itko.lisa.acl.utils.AclJpaUtil$1.initialValue(AclJpaUtil.java:60)
    at java.lang.ThreadLocal.setInitialValue(Unknown Source)
    at java.lang.ThreadLocal.get(Unknown Source)
    at com.itko.lisa.acl.utils.AclJpaUtil.getJpaUtil(AclJpaUtil.java:78)
    at com.itko.lisa.acl.ActivityCache.loadActivities(ActivityCache.java:47)
    at com.itko.lisa.acl.ActivityCache.getInstance(ActivityCache.java:33)
    at com.itko.lisa.acl.RoleActivityCache.loadRoles(RoleActivityCache.java:60)
    at com.itko.lisa.acl.RoleActivityCache.getInstance(RoleActivityCache.java:37)
    at com.ca.dts.security.authentication.RemoteAuthenticationManager.createUser(RemoteAuthenticationManager.java:223)
    at com.ca.dts.security.authentication.RemoteAuthenticationManager.authenticate(RemoteAuthenticationManager.java:183)
    at com.itko.lisa.test.LisaSecurityManager.authenticate(LisaSecurityManager.java:730)
    at com.itko.lisa.test.LisaSecurityManager.authenticateUser(LisaSecurityManager.java:686)
    at com.itko.lisa.test.LisaSecurityManager.authenticateUserFromGUI(LisaSecurityManager.java:928)
    at com.itko.lisa.gui.TestAdmin$1.doCallback(TestAdmin.java:232)
    at com.itko.util.swing.panels.ProcessingDialog$2.run(ProcessingDialog.java:194)
    at java.lang.Thread.run(Unknown Source)
    Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Connections could not be acquired from the underlying database!
    Error Code: 0
    at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:309)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:135)
    at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:330)
    at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:293)
    at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect(DatasourceAccessor.java:418)
    at org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection(ConnectionPool.java:216)
    at org.eclipse.persistence.sessions.server.ConnectionPool.startUp(ConnectionPool.java:504)
    at org.eclipse.persistence.sessions.server.ServerSession.connect(ServerSession.java:484)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:633)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:208)
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
    ... 24 more
    Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
    at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)
    at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:690)
    at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140)
    at com.itko.lisa.utils.db.LisaWrappedDataSource.getConnection(LisaWrappedDataSource.java:38)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:123)
    ... 34 more
    Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
    at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1463)
    at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:639)
    at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:549)
    at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:756)
    at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:683)
    ... 37 more

     

     

    Registry log from server

     

    INFO  com.itko.lisa.coordinator.TestRegistryImpl - adding new live workstation:<<Offshore Devtest Wokstation Host Details>>

    2016-10-25 08:39:25,145Z (01:39) [qtp1143721110-127341] WARN  com.itko.lisa.utils.db.LisaSessionCustomizer - SQL query took a long time (113 ms) : SELECT t1.ACTIVITY_ID, t1.DESCRIPTION, t1.LICENSE_TYPE, t1.ACTIVITY_NAME, t1.PARENT_ACTIVITY_ID, t0.ROLE_ID FROM ACL_ROLES_ACTIVITIES t0, ACL_ACTIVITIES t1 WHERE ((t1.ACTIVITY_ID = t0.ACTIVITY_ID) AND (t0.ROLE_ID IN ?))

    2016-10-25 08:39:25,292Z (01:39) [qtp1143721110-127341] WARN  com.itko.lisa.utils.db.LisaSessionCustomizer - SQL query took a long time (110 ms) : SELECT t1.ACTIVITY_ID, t1.DESCRIPTION, t1.LICENSE_TYPE, t1.ACTIVITY_NAME, t1.PARENT_ACTIVITY_ID, t0.ROLE_ID FROM ACL_ROLES_ACTIVITIES t0, ACL_ACTIVITIES t1 WHERE ((t1.ACTIVITY_ID = t0.ACTIVITY_ID) AND (t0.ROLE_ID IN ?))



  • 2.  Re: User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 11-01-2016 08:47 AM

    It might help us if you can answer any of the following questions:

    - Are you able to remote into the server and successful launch Workstation on the server using 'admin'?

    - Are you certain all of the necessary ports/firewalls are open?  The exception above appears to result from a DB connection timeout error.

    - Which version of DevTest server-side software are you using?  Which version of Workstation are you using?

    - Is the Registry connecting to the DevTest Derby DB or a different DBMS?

    - If using a DBMS other than OOTB Derby, was the database schema created using a national character set of UTF-8 or AL32UTF8?  Normally, if the character set is not configured correctly, you cannot log in to Registry from any console or Workstation.



  • 3.  Re: User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 11-02-2016 05:53 AM

    Many Thanks for your response Joel Nesmith, Please find the answer  below for your question,

    - Are you able to remote into the server and successful launch Workstation on the server using 'admin'?

    (Yes, we are able to launch with admin credentials in remote client box(in onsite), not able to launch only in offshore)

     

    - Are you certain all of the necessary ports/firewalls are open?  The exception above appears to result from a DB connection timeout error.

    (We are using the default ports which is coming under DevTest, Please let me know the list of ports should be enabled from both side(onsite/offshore) )

     

    - Which version of DevTest server-side software are you using?  Which version of Workstation are you using?

    (Yes,we are using the same version from both server/client DevTest8.4.0 )

     

    - Is the Registry connecting to the DevTest Derby DB or a different DBMS?

    (We are using default database that comes with devtest. We don’t have any customize database.)

     

    - If using a DBMS other than OOTB Derby, was the database schema created using a national character set of UTF-8 or AL32UTF8?  Normally, if the character set is not configured correctly, you cannot log in to Registry from any console or Workstation.

    N/A


  • 4.  Re: User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 11-02-2016 10:23 AM

    The ports used by DevTest are documented here:  

    Default Port Numbers - DevTest Solutions - 8.4 - CA Technologies Documentation  

    Check the firewall rules to see if these ports from the Workstation to the Server are open.  

    1505Embedded web serverlisa.webserver.port
    2004VSE Managerlisa.net.9.port
    2005Test Runnerlisa.net.5.port
    2006ServiceManagerlisa.net.11.port
    2009Brokerlisa.pathfinder.broker.port

    2999

     

    8443

    JDBC simulation driver

     

    if embedded SSL is on

    Not applicable

     

    I do not know if Workstation attempts a direct connection to the Derby Database on port 1528.  I have seen this behavior in LISA 7.0.

     

    You might also consider installing a network packet sniffer on your Workstation such as Wireshark.  Use this tool to record the interaction between Workstation and server when you launch the app.  This might shed light as to whether or not a port is failing.  I believe you will see Workstation using TCP protocol.



  • 5.  Re: User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 11-02-2016 11:57 AM

    Yes, a direct database connection is needed for DevTest v8.0 and up (and for DevTest v7.x when ACL is enabled), so a connection on the database port (port 1528 by default) is also required. I added an idea on the community to remove the need for direct database connection Remove the need for direct database connectivity from DevTest Workstation  so please vote this idea up!

     

    Even with the database connection port open, there is still a chance that the embedded instance of Derby just isn't fast enough to service client connection requests. An external database should be used for reliability in all DevTest implementations. See these lines in site.properties:

    ##
    ## Derby is NOT supported in a Distributed Environment. Users must use an
    ## enterprise database in a Distributed Environment
    ##
    #####################################################################################



  • 6.  Re: User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 11-02-2016 12:12 PM

    Yes, We opened the firewalls for the all default ports(1505, 1506, 1507, 1528, 1529, 1530, 2003, 2004, 2005, 2006, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2999, 3128, 3997, 8443, 61617, 1098, 1099, 8080) which is comming under devtest from both side(onsite/offshore),

    still we are facing the same issue

    (User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin])



  • 7.  Re: User does not have permission to use DevTest Workstation with this registry.  Please contact your DevTest administrator. [user=admin]

    Posted 01-13-2017 03:04 PM

    Saravanan,

     

    Are you still having an issue bringing up your Workstation and connecting to a Registry? If so, open up a support case and we can help resolve this issue.