Skip to main content
Y
yugor8127233
Participant
May 10, 2017
Resuelto

After updating Creative Cloud 2015 until 2017 no program is being activated.

  • May 10, 2017
  • 4 respuestas
  • 629 visualizaciones

Hello. I work at the People  Friendship University of Russian

After updating Creative Cloud 2015 until 2017 no program is being activated.

Successfully completed the test https://ims-na1.adobelogin.com/renga-idprovider/resources/img/logos.png

Successfully https://lm.licenses.adobe.com/vact/ping

Successfully Limited Access Repair Tool in admin mode and checking the hosts

Convinced that can connect to secure sites.

Fulfilled All and activation no

    Este tema ha sido cerrado para respuestas.
    Mejor respuesta de jeromeg12249766

    Hi,

    I have the same problem since Monday 9 May.

    The checks were carried out:

    Successfully completed the test https://ims-na1.adobelogin.com/renga-idprovider/resources/img/logos.png

    Successfully https://lm.licenses.adobe.com/vact/ping

    Successfully Limited Access Repair Tool in admin mode and checking the hosts

    When I delete a license on a PC, uninstall the adobe suite, I restart the station.
    A license appears in my license pool in the admin interface.

    I create a new package with the deployment tool, the installation runs correctly.

    In the admin interface, the previously released license is assigned to the new installation

    But, if I run adobe suite software, I am asked to renew the license.

    The probleme is the same on windows 7 64 bits and Mac OSX 10.10.

    4 respuestas

    Y
    yugor8127233Autor
    Participant
    May 15, 2017

    I had a chat with Adobe support.

    All happened when they made me a license file for your instrument.

    After running this file it worked.

    The file size differs from the created by me using the deployment tool.

    Probably they will fix it, but so far we have to go to chat support

    J
    jeromeg12249766
    Participant
    May 15, 2017

    Problem solved by my reseller with Adobe support, It was a problem with the anniversary date.

    I do not have any more precision

    J
    jeromeg12249766Respuesta
    Participant
    May 11, 2017

    Hi,

    I have the same problem since Monday 9 May.

    The checks were carried out:

    Successfully completed the test https://ims-na1.adobelogin.com/renga-idprovider/resources/img/logos.png

    Successfully https://lm.licenses.adobe.com/vact/ping

    Successfully Limited Access Repair Tool in admin mode and checking the hosts

    When I delete a license on a PC, uninstall the adobe suite, I restart the station.
    A license appears in my license pool in the admin interface.

    I create a new package with the deployment tool, the installation runs correctly.

    In the admin interface, the previously released license is assigned to the new installation

    But, if I run adobe suite software, I am asked to renew the license.

    The probleme is the same on windows 7 64 bits and Mac OSX 10.10.

    arij2010
    arij2010
    Inspiring
    May 10, 2017

    Hi,

    In this case you can use the trials already installed and activate them by creating a license pack as explained in the doc of previous message .

    arij2010
    arij2010
    Inspiring
    May 10, 2017

    Hi,

    Normally if you are a university ,you have a device licenses .

    If you make a normal update without a package ,it's normal that your installed versions convert to trial .

    To verify which type of license you have ,go to team console on the Adobe portal and check under device licenses .

    To activate your products in the case it's  a device licenses ,create a license package and run it as Admin on the concerned machine :

    https://helpx.adobe.com/creative-cloud/packager/create-license-file.html

    Y
    yugor8127233Autor
    Participant
    May 10, 2017

    I created a new package for Creative Cloud 2017 and tried to install it on the computer but nothing out.

    Installed on windows 7 64 bit after uninstalling Creative Cloud 2015 and the new windows 7 the result of one-

    instalation failed.

    I created a package 2017 twice , and a year ago created packages 2015 for windows and for MacOs.

    Unfortunately, in the PDApp.log the reasons are not found

    Términos y condicionesAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices