Wyatt O'Day (Wyatt) has made 7771 posts.
Things should work now. We improved our DDoS protection earlier today and FastSpring incorrectly got…
Post on Jul 22, 2016Hey Matt, We'll look into it. Can you try again right now? Are you still getting the error?
Please try again. If you're still getting the error, try clearing the cache in your browser, and t…
Shoot me an email and I'll send you a link to a test version 3.4.7 which has the new networking code…
Post on Jul 20, 2016>> "We also have a large number of users in Australia and New Zealand that have encountered th…
Post on Jul 9, 2016>> "1)TurboActivate tries to read info from the socket and gets an error (socket closed, EOF, …
You need to use the correct wyUpdate version for your app and/or make sure the correct .NET framewor…
>> "2)The licensing system is not 100% reliable when it comes to lost activations" We're sig…
Post on Jul 19, 2016Short answer: don't do this. Longer answer: don't do this because it gives malicious customers the…
Post on Jul 17, 2016The customer can do it themselves: http://wyday.com/limelm/help/activations/#deactivate And you ca…
Hey Josh, A lot more information is needed. Starting with the product key (or product keys) that t…
Hey Jim, Short answer: yes, you can use TurboActivate and TurboFloat with Advanced Installer (and …
You said you're using the TurboActivate API to generate the activation request. That's the problem. …
Post on Jul 14, 2016We're improving the error code. Instead of "Can't activate a TurboFloat key." it will say: "Can't ac…
IsActivated() returns TA_FAIL (i.e. 1) in the case of not being activated. IsActivtaed() return TA…
Hmmm... it sounds like that particular distro you're running on doesn't have the proper libraries in…
Hey Todd, What you're describing is basically the textbook use of floating licensing: http://wyday…
Are you using the correct DLL? A screenshot would be best. Both of the DLL you added to the project,…
Hey Alessandro, >> "1) is it this architecture feasible (or must TFS be unique in the local …
We're going to look into this. We'll get back to you.