AccessViolationException when running TF on same machineSolved

Hi,

I have done an implementation of TurboFloat (TF) in one of my application for testing. I'm running into an network issue when I try to run it.

I'm hosting the license server on the same machine I do dev on. I set up the server to use port 9999. I can see the server running fine in task manager.

When I run the application and try to connect it with the server using the IP address of the computer I get an error that the server cannot be reached. That's expected and handled properly. I then tried using the loopback address 127.0.0.1 and instead of an error like before, the application stops with an AccessViolationException in TurboFloat.cs at line 301 "int ret = Native.TF_RequestLease(handle);".

Would you have any idea why?

Would you have any idea why?

No, I don't, but I do know it shouldn't do that.

First, try re-downloading the TurboActivate.dat from your version page in LimeLM. Then replace the existing TurboActivate.dat file. Does that fix it?

Have you tested our example C# app? Change the GUID, plop the TurboFloat.dll in the Debug folder alongside your TurboActivate.dat file and then run the app. Do you get the same exception there?

Hi,

I did try to re-download the TurboActivate.dat. Actually I had to, otherwise I couldn't even start the server.

I'll try the demo and let you know.

Hi,

Tried the demo, same exception...

I was using the 64bit version of the server, restarted with the 32bit. Same exception.

The demo tries to get a lease first, then when that fails pops the server dialog. It crashed on the first call to RequestLease (never sees the server dialog). My app uses SaveServer first with info from the config file then call RequestLease. I thought that was the issue since I had configured to use the loopback. I do not get that exception if I use the actual IP address of the computer. Does TurboFloat use the loopback address as default the first time it calls RequestLease ?

Btw, my computer is running Win7 64. if that has any weight.

The AccessViolationException doesn't have anything to do with the server or port (it just means our library tried to write to memory it shouldn't have written to). Can you send me the following at wyatt@wyday.com:

  1. Your version GUID
  2. Your TurboActivate.dat file.
  3. A product key for TurboFloat Server (it just needs to have 1 concurrent user, and after I'm finished with it you can delete it).
  4. The server address you're using (127.0.0.1, right?)
  5. The port you're using (9999, right?)
  6. Are you using the 32-bit or 64-bit version of TurboFloat?

We'll test it on our computers. If we can't reproduce it here then I'll send you a debug build with instructions on how to get the memory dump so we can debug and fix the problem.

I sent the info.

Thanks, I'll take a look at it later tonight.

TurboFloat 3.5.1 is out. This bug has been fixed.

Yes, it works now. Thank you!

Reply
Discard post