Upgrading to Primalscript 7.0.53_102614_x64 broke my license

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 9 years and 4 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
TCCDesktopOps
Posts: 18
Last visit: Sun Nov 19, 2023 7:05 pm

Upgrading to Primalscript 7.0.53_102614_x64 broke my license

Post by TCCDesktopOps »

I had a working version of Primalscript 7.0.22_032614_x64, upgraded to Version 7.0.53_102614_x64 and now can't use the software.
Primalscript says i now have a trial version with 0 days remaining. My serial is not accepted.
My account says i have a license key asociated with a subscription and to "click here" to retrieve this license key - the link doesn't work - tried IE11 and firefox 25, no change.
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by davidc »

You must enter your subscription number (starts with 9) and username/ password to unlock the software.

Please refer to the following blog article:

http://www.sapien.com/blog/2014/03/25/a ... scription/

Without the error message it is hard to tell what the exact problem is.

David
David
SAPIEN Technologies, Inc.
User avatar
J A Reif
Posts: 241
Last visit: Fri Mar 22, 2024 8:12 am
Answers: 1
Has voted: 1 time
Been upvoted: 1 time

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by J A Reif »

Hello,

Regarding the license key - the 'click here' link does work as it simply scrolls your page up to the top where your subscriptions are listed along with associated license keys (except for Productivity Pack keys, which are accessible from the Productivity Pack button next to the associated subscription). The specific license key being referenced on your account is for the Productivity Pack Key associated with your subscription ending in 4675.

Also, please note that since this is a PrimalScript specific question, it really should be posted in the PrimalScript forum. I will move it there for you so that our PrimalScript experts can view and help resolve your issue.
June Alane Reif
SAPIEN Technologies, Inc.
User avatar
TCCDesktopOps
Posts: 18
Last visit: Sun Nov 19, 2023 7:05 pm

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by TCCDesktopOps »

When I enter the sapien ID, password and put my subscription number (ending in 4675) into the field that asks for a "Licence No", I get the following message

---------------------------
PrimalScript
---------------------------
This subscription is not for this product. Please contact sales@sapien.com to purchase a subscription for this product
---------------------------
OK
---------------------------
User avatar
TCCDesktopOps
Posts: 18
Last visit: Sun Nov 19, 2023 7:05 pm

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by TCCDesktopOps »

I also tried the productivity pack key (ending in DABB8) and received the following message

---------------------------
PrimalScript
---------------------------
This license key has expired. Please contact sales@sapien.com to obtain a valid key for this product
---------------------------
OK
---------------------------
User avatar
TCCDesktopOps
Posts: 18
Last visit: Sun Nov 19, 2023 7:05 pm

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by TCCDesktopOps »

Not sure if it was clear from my original post, but Primalscript was working fine before I upgraded.

Also, maybe the comment above re "Regarding the license key - the 'click here' link does work " indicates the issue as there are no license keys listed, only a subscription key.

this is the information on the page I am looking at

"You have a license key associated with a subscription. Please scroll to the Subscriptions section at the top of the screen or click here to retrieve this license key. "
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by Alexander Riedel »

I did a quick test with your account and the subscription number ending in 4675. PrimalScript 7.0.53 activated without any problems.
I have of course removed the activation again.

Please take a screenshot of the license dialog before you hit activate
and email it to support@sapien.com

That way our web people can trace the activation request as you enter it through our system.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
TCCDesktopOps
Posts: 18
Last visit: Sun Nov 19, 2023 7:05 pm

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by TCCDesktopOps »

SS sent as requested
User avatar
TCCDesktopOps
Posts: 18
Last visit: Sun Nov 19, 2023 7:05 pm

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by TCCDesktopOps »

Stand Down - Thankyou for the assistance. Primalscript is now working.
For anyone else with the issue, I just redid the installation -

I uninstalled, restarted, reinstalled the new version and then restarted again.
Prior to the second restart, Primalscript started, but under "about" it said registered to "temp". All good after that second reboot with my details showing under "registered to"

I didn't need to enter any details, they were automatically found.
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Upgrading to Primalscript 7.0.53_102614_x64 broke my lic

Post by davidc »

Re-install was not necessary. Using "Run as Administrator" would have resolved the issue.

David
David
SAPIEN Technologies, Inc.
This topic is 9 years and 4 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.