Author Topic: Invalid Authorization Code  (Read 846 times)

Offline campbesj

  • Newcomer
  • Posts: 4
Invalid Authorization Code
« on: 2019 March 25 11:08:15 »
I am currently running on a trial license but plan to upgrade later this week.

I tried to start the app yesterday but it failed because my Internet connection was briefly down.
I got my connection restored but PixInsight fails with Invalid Authorization Code every time I try to run it.

I requested and got a reactivation code, uninstalled and reinstalled the app but I get the same error before I can enter the new credentials.

So I went ahead and installed the app on an old (and inadequate) laptop with the new credentials and they worked.
What impact will this have on upgrading my license on the desired laptop?
Is there a fix?

By the way I am thrilled with how good my images looked while it was still working.

Offline campbesj

  • Newcomer
  • Posts: 4
Re: Invalid Authorization Code
« Reply #1 on: 2019 March 25 18:00:39 »
I finally got it to work.
I deleted the Pleiades folder in AppData\Roaming
Uninstalled and reinstalled
Requested a reactivation

That did the trick

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Invalid Authorization Code
« Reply #2 on: 2019 March 26 02:02:35 »
Your license file has been damaged or corrupted, which happens sometimes because of communication problems with our server. Some virus protection softwares may also cause these problems on Windows by tampering with the encrypted data shared with our server during the license verification process.

See FAQ 2.23 to know how to solve these problems:

https://pixinsight.com/faq/
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline campbesj

  • Newcomer
  • Posts: 4
Re: Invalid Authorization Code
« Reply #3 on: 2019 March 26 05:08:47 »
Thanks, as I said I go it to work.  I'm hugely impressed with your product and plan to buy a license (in next month's budget!)
If I might make a suggestion, if you could reference the FAQ in the error message, or at least make it a little more descriptive it would be a big help to anyone having this problem in the future.