When I try to deactivate the key in the Dashboard I receive the following message "The activation you're looking for wasn't found. Either it never existed or you don't have access to it".
That's a bug. We'll fix that ASAP.
Hi again,
I'm trying to deactivate a floating license product key that was activated using TF server. It seems the server exe itself has no option for that. When I try to deactivate the key in the Dashboard I receive the following message "The activation you're looking for wasn't found. Either it never existed or you don't have access to it". Yet, the dashboard reports it as activated (Yes,1). How should I proceed to deactivate a product key?
Thanks.
When I try to deactivate the key in the Dashboard I receive the following message "The activation you're looking for wasn't found. Either it never existed or you don't have access to it".
That's a bug. We'll fix that ASAP.
This has been fixed, sorry about that.
Does this mean that the only way to deactivate the product key from the server is through the dashboard? I'd prefer not to have to deal with a customer when they need to change the floating license server from one machine to another. How can I go about doing that without having to interact with the customer.
Thanks,Arie
No, TFS 4.0 you'll be able to deactivate using commandline. We didn't include it in TFS 3.x because we didn't (at the time) have the ability to limit or prevent deactivations server-side.
Is the date for 4.0 coming soon? Is there any way to get a pre-release version?
--Arie
TA, TF, and TFS 4.0 are all coming before Christmas this year. We're not releasing any more pre-release versions of 4.0.
Nice Christmas present, thanks for letting us know. If I have the TurboFloat Server 4.0 running on a server machine and a user is still running my app which uses the current version of TF (3.5.6), will that app still be able to "talk" to the 4.0 version of TFS?
Thanks,Arie
Yes, your app, using an old version of TurboFloat Library will be able to talk to newer versions of the TFS (unless you use a feature of the TFS that requires a new TF Library).
The reverse is not true. A new version of TurboFloat Library requires the TFS to be the latest.