Test Data Manager

  • 1.  CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES

    Posted Aug 31, 2017 12:00 PM

    HI ALL

    I'm getting the error: FAILED TO GET THE LIST PROFILES on the CA TDM PORTAL  4.1 .... when I click on Configuration --> Connection Profiles
    Does anyone know why? On Gtdatamaker the connection profiles are working well!

     

    thx

    Carlos 



  • 2.  Re: CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES

    Posted Aug 31, 2017 12:08 PM

    Hi Carlos, jupca01

     

    One resolution is to restart the TDM Portal service. 

     

    Can you please try that and let us know if you are still experiencing the issue?

     

    Best regards,

    Taylor



  • 3.  Re: CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES

    Posted Sep 07, 2017 06:32 PM

    HI All

    Please, Sorry for the delay in responding .. From the moment the connections were defined as DNS-LESS, it worked without problems

    Thx



  • 4.  Re: CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES
    Best Answer

    Broadcom Employee
    Posted Sep 04, 2017 02:40 AM

    Hi Carlos,

     

    The connections create in Datamaker are only available in the portal when the connection is a DNS-less ODBC connection (jdbc). Connections created in the portal are listed in both Datamaker and portal.

     

    Best regards,

    Peter



  • 5.  Re: CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES

    Broadcom Employee
    Posted Sep 05, 2017 12:58 PM

    Hi Carlos,

     

    Have you been able to resolve this?  Did either of the suggestions help?  If you resolved it, how?

     

    Cheers!
    Les.



  • 6.  Re: CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES

    Posted Sep 07, 2017 06:31 PM

    HI All

    Please, I am  for the delay in responding ..

    From the moment the connections were defined as DNS-LESS, it worked without problems

    Thx



  • 7.  Re: CA TDM PORTAL 4.1 - FAILED TO GET THE LIST PROFILES

    Posted Sep 07, 2017 06:29 PM

    HI All

    Please, Sorry for the delay in responding .. 

    From the moment the connections were defined as DNS-LESS, it worked without problems.

    Thx