TLTLWe are using TurboActivate (static lib for C++, VS 2012) in our "extension" product distributed as DLL (that is, the DLL is loaded into platform's address space on clients' servers), latest version (Nov 2013).
The problem we have faced is this: when the client runs out of "activations", the ActivateEx() function freezes and never returns instead of returning an error (does not happen always, on our test servers it runs fine, but we've had a couple of unpleasant occasions on our clients' servers in live environments). Our log data unambiguously shows that it is this function causing the freeze.
Please help us troubleshoot the issue.
It sounds like something on the network is intercepting and accepting the connection ("faking" being the activation servers) and instead just blindly leaves the connection open.
So, the problem is on the customer's end. Tell them to stop blocking/intercepting wyday.com.
We'll put a hard timeout on the next version.
TLTLWyatt, the customer does not seem to have any network blocking/interception issues, because after the frozen program is restarted, ActivateEx() keeps reporting failure properly, without further freezing.
So the issue happens exactly on the first time when a client exceeds their amount of available activations (say, 2 of 2 available activations had been done already, and now client tries to activate the third one).On the first time, the ActivateEx() function freezes.On the second and subsequent tries (after the whole host process is killed and restarted), we receive a proper error from ActivateEx().
Moreover, previous attempts of ActivateEx() were successful on the same server, so network had been working fine (for some reason, the library thinks that server becomes a new machine and requests a separate activation slot which is a nuisance, but manageable one as long as the whole platform does not get frozen upon depletion of free slots. I even think that this "drifting" of unique machine ID might be linked to reasons why the freeze occurs).
Nothing changes in networking environment between the first and the second try, so I suspect the issue has nothing to do with wrong connections or blocked ports.
We'll try to reproduce this. I'll get back to you.
TLTLHello Wyatt.
Have you had a chance to take a look at this?Is there any information (debug logs, error codes) we can supply to help you investigate?
We can't reproduce this. Try using the latest version of TurboActivate (3.4.6) and see if that fixes it.
Can you reproduce this error on other computers?
