Forum Discussion

jshu's avatar
jshu
Occasional Contributor
8 years ago
Solved

License key renewal issue

Sorry to bother, our group used to use SoapUI Pro 5.1.2 and we decided to use Ready!API1.5.0, we've got the new license keys from you and applied, all license keys worked fine, however, some guys have an issue that after they close the Ready!API1.5.0 and reopen it, it pops again asking for reactivating license key, we follow the same renewal procedure and we don't know why we have different result, do you have any solution for the reactivating issue please?

 

Thanks again for help

 

Jerry

  • jshu's avatar
    jshu
    8 years ago

    We figured out where the problem was, there's a network issue, the license was registered successfully on your server but didn't save correctly on some of colleagues' machine, anyway, we are ok now

     

    Thanks again

     

    Jerry

2 Replies

Sort By
  • jshu's avatar
    jshu
    Occasional Contributor
    8 years ago

    Here's the details

     

    We used to use SoapUI Pro 5.1.2 before, when we started to use Ready!API1.5.0 about 4 months ago, it used our SoapUI Pro5.1.2's license and everything worked fine, last week our SoapUI Pro5.1.2's licenses expired and our company renewed licenses with SoapUI, today we started renewal process, some guys updated the license directly in Ready!API1.5.0 and were successful, they don't have any further issue, others UNINSTALLED SoapUI Pro 5.1.2 and UNINSTALLED Ready!API1.5.0, and then reinstalled Ready!API1.5.0 and applied license, they got successful in updating license but when they closed the window and reopened it, it prompted again for activating new license

     

    Do you think uninstall and reinstall would cause this issue please?

     

    Thanks again

     

    Jerry

    • jshu's avatar
      jshu
      Occasional Contributor
      8 years ago

      We figured out where the problem was, there's a network issue, the license was registered successfully on your server but didn't save correctly on some of colleagues' machine, anyway, we are ok now

       

      Thanks again

       

      Jerry