Hey Arie,
It just means the data that got received at the server has been mangled by something between your program running and the TFS instance.
Are the versions of the TF Library the latest?
Error with requesting lease from activated Turbo Float ServerSolved
Hi There,
I'm on OSX Sierra, and have installed and activated Turbo Float for Mac (4.0.9). It starts fine on boot, and see all notifications being sent to the log file. I'm using the latest Turbo Float dynamic library in my build as well.
However, when my app requests a license from the serverinstalled on my dev machine, I am getting an error. Each time I try to request a least I'm getting the same errors. See the following:
2017-03-22, 12:38:55 <notification>: New connection from IP: ::ffff:127.0.0.12017-03-22, 12:38:55 <notification>: Failed to clean the client-supplied activation block.2017-03-22, 12:38:55 <notification>: Failed to process the request: basic_ios::clear2017-03-22, 12:38:55 <notification>: New connection from IP: ::ffff:127.0.0.12017-03-22, 12:38:55 <notification>: Failed to clean the client-supplied activation block.2017-03-22, 12:38:55 <notification>: Failed to process the request: basic_ios::clear2017-03-22, 12:39:04 <notification>: New connection from IP: ::ffff:127.0.0.12017-03-22, 12:39:04 <notification>: Failed to clean the client-supplied activation block.2017-03-22, 12:39:04 <notification>: Failed to process the request: basic_ios::clear2017-03-22, 12:39:27 <notification>: New connection from IP: ::ffff:127.0.0.1
So, it seems like TFS is getting a signal from my app, but I'm not sure about what it means about "Failed to clean the client-supplied activation block"
Can you help me out?
Thanks,Arie
Thanks for the quick response, Wyatt! Much appreciated. Yes, I've installed the latest server and the latest library for OSX. Is there a place that would make sense to look to see where my app code could be passing in bad data?
I'm running the TFS server on my local dev machine on port :13 and running my app on the same machine for testing. So the server is 127.0.0.1:13 Will that work for tests?
We're going to look into this and try to reproduce it.
We've found and fixed this issued in 4.0.9.7. Thanks for reporting this.
I know I'm late to respond here, but just wanted to ask if I upgrade to 4.0.9.7, do I also need to upgrade the libraries for compiling? I'm getting the error now, but realized I'm still on 4.0.9.0
I'll get the new server, but please let me know if I should also upgrade the libraries.
Thanks,Arie
The bug fix referenced in this post is to the TurboFloat Server. So upgrading that will fix this bug.
But, as a general rule, yes, you should upgrade the TurboFloat libraries as well, if you can. They also contain bug fixes, improvements, etc.: https://wyday.com/limelm/api/tf-changes/