This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PSPICE-FOR-TI: [PSPICE-FOR-TI] Unable to valid licenses

Guru 52871 points
Part Number: PSPICE-FOR-TI

Hi 

Would you please resolve this license issue ? 

-Eric Lee

  • Hi Eric,

    Could you please open the following URL in your browser: https://cdsplicwc.cadence.com/chws/test/connection.html

    If it dos not say "Successful Connection," then there is an issue with your internet connection and you should contact IT. If it does say "Successful connection," would you please send us the installation log, cdsPspiceTIlog.txt, in location %appdata%\Cadence\PSpiceTIInstall

    Do not post your license.txt file, but please check that it exists. It is stored at:  %appdata%\Cadence\VBL\TI_PSpice_174\license

    Regards,

    David

  • Hello David 

    It says 'Successful Connection'.

     

    7142.license.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    #
    # This email has been sent by an automated
    # process. Please do not reply to this email.
    ##
    #
    ########################################################################
    # COSLITE INFORMATION
    ########################################################################
    #
    # PLEASE NOTE: Your license file may contain COSLITE product depending on
    # your entitlement. This license will allow some digital tools to access
    # support.cadence.com content (via CadenceHelp) without requiring login.
    # This is a zero cost license and will be active as long as the primary tool
    # license is active. More information is available at
    # https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000009Mns6UAC
    # For any further questions, please use the feedback option in the
    # https://support.cadence.com site and someone from the product team will get
    # back to you.
    #
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    -Eric Lee

  • Hi Eric,

    Please try the steps listed in the linked thread

    Your code is different, but it may all be related.

    David