Forum Discussion

thatsthat's avatar
thatsthat
Contributor
1 month ago
Solved

Unable to authenticate license in Ready API Login button unresponsive

Ughhh! 3 hours wasted now. Uninstalled the latest Ready API and reinstalled.

3 days in a row now I have had to login to activate my ready api license.

Today the button Login DOES NOT WORK ..so I am completely locked out of the application.

The login button is completely unresponsive. No window opens to login.

I am expecting a browser to open up and to login .. but nothing happens. 

Any suggestions / alternate paths to get authenticated?

 

  • Solved after a callwith Smartbear .. i had to delete 3 .dat files from my users / ready api directory

7 Replies

  • Solved after a callwith Smartbear .. i had to delete 3 .dat files from my users / ready api directory

    • Dino's avatar
      Dino
      Occasional Contributor

      Hi there, What are the files you deleted pls ?

  • Dino's avatar
    Dino
    Occasional Contributor

    The files to delete are : license-info.dat, client-info.dat, authorization.dat

    • thatsthat's avatar
      thatsthat
      Contributor

      That is correct .. those are the 3 i deleted then restarted the application.

  • esoysal's avatar
    esoysal
    Occasional Contributor

    I've been having the same issue lately. I cannot count how many times I deleted those .dat files or the entire .readyapi folder. The issue comes back after you restart your computer couple of days later. Please let us know if your fix persists. Also give us more detail about the solution so we can follow your steps.  

    • thatsthat's avatar
      thatsthat
      Contributor

      It is as simple as deleting these 3 files from your users/readyapi directory:

      license-info.dat, client-info.dat, authorization.dat

      1. Shut down ready api
      2. Delete those 3 files
      3. Start up ready api 

      Done. Hopefully the problem goes away after that.

    • thatsthat's avatar
      thatsthat
      Contributor

      Just had to do it the once and it held .. no issues since I originally reported this ..recommend you log an official support request if it persists over and over