Error client to server connection : "Connection to server failed"Solved

Hi,

A customer using a floating license has a problem during connecting client machine to the turbo float server :

They checked the followings for this issue.1. The connection between server and client by ping, and the server port is not used by other applications.2. The server service is running.3. Other client machine does not work well too with same message.

Below is a part from the TFS log file :

2016-09-01, 19:52:28 <warning>: This floating license server is activated, but it failed to verify the activation with the servers. You can still use the app for the duration of the grace period.

2016-09-01, 19:53:13 <error>: Failed to start as a Windows Service (error: 1063).Try `TurboFloatServer -h' for more information.

2016-09-01, 19:54:28 <error>: Not activated (error code: 0x1). You must activate this TurboFloat Server via commandline like this:TurboFloatServer.exe -a="ABCDE-FGHIJ-KLMNO-PQRST"

Please help to get th issue resolved.

Thank you.

Please for your information, customer is Japanese, and used a Japanes OS on the server machine, we used to face many issues with the japanese configurations having the LimeLM activations or floating licenses.

We need to diagnostic from your side and have a solution for this case as soon as possible please.

Thank you.

Well, the server service (the TurboFloat Server instance) is not running. And it's telling you that, and why (because it needs to reverify with the activation servers).

So, the solution is to make sure they actually allow acres to wyday.com from that machine. Or do the activation offline.

Lastly, make sure they're using the latest version of the TurboFloat Server (currently 4.0.2).

Let me know if that helps.

Thank you for your response.

I'll check the access to the website, then the offline activation, and I'll update you.

Hi,

The activation works well by offline activation. However they can use three clients at the same time eventhough the Floating licenses is set to 1.

Could you please give us a help to avoid this situation.

Thank you.

First of all, are you using the latest version of the TurboFloat Server and TurboFloat? (currently 4.0.2). If not, do that: https://wyday.com/limelm/api/#turbofloat

Next, we need a whole lot more information. Do you mean they're running multiple instances of your app in *the same user-session*, and TurboFloat is allowing that? If so, then that's expected behavior. In TurboFloat 4.0.2 we do not currently allow the limiting of process-instances in a user-session. That's up to you to limit.

We do limit how many user-sessions your app can run under. For more information see: https://wyday.com/limelm/help/licensing-types/#floating

Thanks for your response.

The customer uses the version 3.5.6, in next step, by our next app release we need to update bothTurboFloat Server and TurboFloat to the latest you have mentioned 4.0.2.

Back for the issue, the customer is running instances of the app in different separate machines as clients (2 Windows OS machines as clients that are connected to the server, while floating license number is one), it's a strange case, but it happened and want to verify what have leaded to this scenario.

We have no more information, but the log for activation in both client machines shows that the server gives a lease to both at the same time.

It sounds like the customer request a license lease on one computer, stopped the TurboFloat Server, and then requested a license lease on another computer.

This was fixed in TurboFloat Server 4.0.2 (out a week ago). See the changelog here: https://wyday.com/limelm/api/tf-changes/

Now TurboFloat Server remember licenses leases even if it has been stopped, restarted, crashed, etc.

So, upgrade to TurboFloat 4.0. It has a bunch of bug fixes and features.

Reply
Discard post