Activation issue on TFS build server

Posted by: mabrown on 10 September 2017, 3:46 am EST

    • Post Options:
    • Link

    Posted 10 September 2017, 3:46 am EST

    We are upgrading C1 Studio on a TFS build server. The installation went fine; however, when attempting to activate the license (the same serial number used to activate on my developer workstation), we are getting an activation failure message. The serial number has only been used on my workstation, so it should be available for use on the build server, correct?

    Due to problems with a component in the upgraded suite, I was forced to downgrade to an older version on my workstation but have since reinstalled the new version. Is this perhaps the cause of my issue? How can I go about freeing up one of my activations so that the build server and my workstation are both good?

    Thanks, Marc

  • Posted 10 September 2017, 3:46 am EST

    Hi Marc,

    One serial key can be used to activate the license on three machines at a point of time. If you already activated the license on three machines and you will try to activate it on fourth, the error will occur.

    In order to activate the license on a new machine, you would need to deactivate it from one of your existing machines. This can be done by:

    1. Run C1LicenseDeActivation utility from the following location on your machine:

      C:\Program Files\ComponentOne\C1StartMenu

    2. Enter the required details and follow the instructions to finish the process.

    Thanks,

    Pragati

  • Posted 22 October 2017, 5:53 pm EST

    Hi Support.

    Same problem with a new license.

    License is activated on my work computer and my home computer.

    But on TFS server I cannot activate it.

    Until years it was possible to activate a license on three (3) computers.

    It seems that now we can only activate it on two (2) computers :frowning:

    https://www.grapecity.com/en/licensing/componentone

    In january I’v a mail from C1 saying that I can activate the product on 3 computers, not now.

    End-User license has changed … without information.

    This will be a big problem for developpers.

    Claude

  • Posted 24 October 2017, 9:22 pm EST

    Hi Claude,

    I am sorry for the inconvenience caused to you. Actually, there was a change in activation from 2017 v1 onwards and the correct number of activations per license is TWO now. For the licenses prior to this version, the limit is still three. But, for all the keys from 2017 v1, it has been revised to two as mentioned in the EULA and on the website.

    Thanks,

    Pragati

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels