FlasherActually, not sure about the "netbook" part, screenshot may have just looked small on the huge screen I am currently on. The customer's screen is 1280 x 800 pixels.
Activation not working for a customer...Solved
FlasherSomeone has bought my software, but for some reason can't seem to get the key to activate. The key says 0/1 activations on here. They are internet connected, and say they have used the key and nothing happens. They are on windows. 7 or Vista I think, it also appears to be a netbook from the resolution of the screenshot. I have given keys to other people and none of them have had this problem. Any idea on what might be going on or how to resolve it?
I am the person who is using it in Flash Pro BTW.
FlasherFlasher*update* I told him to try installing it on another computer if he has one. That didn't work for him either.
What was the error that happened? How are you using the code (that is, do you show errors to the user or are they eaten?)
FlasherI don't believe he got an error, or didn't say anything about one.
I *think* the code should be there to set the PKey window's lblErr textField to an error via the ShowError() function. It is my own porting of the flex example code though... It may be of some help once the 3.0 is out with the Flash pro example so that there isn't the possibility of breakage porting the code from the Flex example.
Also I think he may have just reinstalled it on the same computer, not installed on another one, judging from his last email.
Unfortunately there's not enough information to know what happened. TurboActivate has no problem with netbooks, so that shouldn't be the issue.
A good way to test to see if your errors are showing correctly is to unplug your ethernet (or your wireless) then try to activate on your computer. It should show an error about the internet connection.
If the errors *are* showing correctly, then you'll need the customer to give you that error.
This problem should be fixed with TurboActivate 3.0 coming in about a week.
FlasherThanks, It's good to know it will be fixed.
How can I get my software working for my customer while awaiting 3.0? He was in the middle of working on something and is really upset that he cant use the program.
When trying to test trial extensions, I get the "Failed to extend trial." error when I test it on my computer. I created an online trial extension code for testing and that is what happend when I tried using it.
Did you use UseTrial() before in your code? If the user is not activated you should call that on every start of your app.
I'll look into this -- it should work fine. Have you tried both online & offline trial extensions? Do both fail?
FlasherI get the same error when trying to do an offline trial extension.
Do I need to rebuild the program with an updated TurboActivate.dat? Because I don't know how it would know there is a new offline extension available, being offline with no access to the server.
The "ExtendTrial()" function takes in a string like "FEGX-VBVD-6DSH-67BE-TFHI-EFAJ-9SXT". So you call:
So, in Adobe AIR, this might look like:
ta.ExtendTrial(txtTrialExt.text);Where "txtTrialExt" is a textbox where the user entered their trial extension (e.g. "FEGX-VBVD-6DSH-67BE-TFHI-EFAJ-9SXT").
Does this make sense?
FlasherI have found a mistake I made where ExtendTrial() was not reading the right string to it. After fixing it, the extension worked for my customer and he is relieved.
Now just awaiting TurboActivate 3.0 for a permanent fix, thanks.
As for the question about the offline trial extension. I was curious, when you create an offline extension on the site, how does the program on the customers desktop know said extension exists, since it would presumably be offline and can't communicate with the server?
As for the question about the offline trial extension. I was curious, when you create an offline extension on the site, how does the program on the customers desktop know said extension exists, since it would presumably be offline and can't communicate with the server?
You have to send the offline trial extension to the user somehow (email, morse code, smoke signal, etc.). Then, on the client side, the trial extension details are encrypted in that long text block.
CWell, I tried making a build with the updated TurboActivate that was supposed to fix the issue and it still continues to be broken and the customer is pissed.
Can I just make a trial extension with and absured value like 1,000,000 days? I don't want to be accused of cheating the system to effectively get an uncounted activation, but there needs to be a timely, permanent solution for this customer who has been wait for a fix forever.
We've fixed all known problems with activation in TA 3.0 -- it sounds like the customer is running into something different. Try using CheckAndSavePKey() with the TA_SYSTEM flag. For example:
ta.CheckAndSavePKey(pkeyWin.txtPkey.text, TurboActivate.TA_SYSTEM);If that doesn't work then we're going to need to remotely fix this problem on the customer's computer because there's not nearly enough information. Give us some times the customer is free.
CHow difficult is it to fix the problem remotely? What does the task involve? Would it expose the workings of the licensing system if you walk him thru how to fix it remotely?
I am quite burnt out from all the tedious packaging of builds to try to work around this problem, and I don't know that I necessarily want to make the activation "system wide" on multi-user systems, which is what I think that flag does.
So I might like it if you did the remote fix and I could give you their email and the name of the program. But first I am curious as to the questions above. I wouldn't want the remote fix process to expose how to crack the system to the customer, as I am sort of suspicious of this customer to be honest. I know he legitimately purchased the key and his key is valid, but I do think there is a chance he could be looking to crack the program. If you want more details on why I'm suspicious, just say so, and I will figure out how to PM you.
If you want more details on why I'm suspicious, just say so, and I will figure out how to PM you.
Sure, email me at wyatt@wyday.com.
How difficult is it to fix the problem remotely? What does the task involve? Would it expose the workings of the licensing system if you walk him thru how to fix it remotely?
Mostly it involves seeing where the process fails. If I were to guess it sounds like a user configuration error (bungled group policy editor, registry that has been "optimized" a.k.a. ruined, etc.). We don't expose any of our source code. We can get a lot of information just by watching the process (because we understand the internals of what has to happen).