Hi,
On the forums I've seen it mentioned a turbo float server version 4 should be backwards compatible with clients using turbofloat library 3. However I'm experiencing the opposite.
Client versions: 3.5.5.2 & 4.0.9.5Server versions: 3.5.6.0 (linux) & v4.0.9.0 (linux) & v4.0.9.3 (win)
I expected client version 3.5 to work with a server version 4.0, however the software cannot connect to the server. Switching the dll to version 4 solves the problem so the connection to the server is ok.
This makes updating the floating licenses very difficult because everything need to be upgraded at the same time.
Can you confirm these versions are not compatible with each other?
Best regards,Wouter
Hey Wouter,
The TurboFloat Server can understand requests from older library versions, except in the case where you're using new TurboFloat Server features. For example if you're using "per-seat licensing", then the client cannot understand what is coming from the server: https://wyday.com/limelm/help/licensing-types/#named-user
Can you give us a snapshot of the TurboFloat Server log when the library that is failing is making a request?
GuestHi Wyatt,
Thanks for your response.
TurboFloat server Windows v4.0.9.32017-02-07, 09:40:30 <notification>: New connection from IP: ::ffff:127.0.0.12017-02-07, 09:40:30 <notification>: Failed to clean the client-supplied activation block.2017-02-07, 09:40:30 <notification>: Failed to process the request: ios_base::failbit set: iostream stream error
TurboFloat server Linux v4.0.9.02017-02-07, 08:33:30 <notification>: Activated successfully.2017-02-07, 08:33:30 <notification>: Auto-detected 4 CPU cores; creating a thread pool that large.2017-02-07, 08:34:24 <notification>: New connection from IP: ::ffff:10.0.2.22017-02-07, 08:34:25 <notification>: Failed to clean the client-supplied activation block.2017-02-07, 08:34:25 <notification>: Failed to process the request: basic_ios::clear: iostream error
In both cases the client library is version 3.5.5.2.
We're going to look into this and see if we can reproduce it.
Did you have any luck reproducing this error? If not, is there anything I can help you with?
We can reproduce this and it will be fixed in the next version of the TurboFloat Server. In the meantime the solution is to set the log-level to anything "lower" than notification.
This was fixed years ago in TFS 4.0.9.7.
Always use the latest TFS. It will always be backwards compatible with old version of the TF library.
After upgrading the TFS also upgrade the TF library.
