TurboFloat error 0xc0000417 (for ancient version of TF)

Hi,

One of our customers can't seem to be able to get a lease from their TF server (the TF server looks to be running fine). Our application crash stating an exception 0xc0000417 in TurboFloat64.dll, version: 3.5.5.2.

The exception error code seems to indicate an invalid parameter, according to certain sources. This possibly indicates an invalid/missing C/C++ runtime DLL.

From other threads I believe that only dynamic linking was supported prior to 4.1 (correct me if I'm wrong) so TF would be looking for a runtime DLL.

Question, what is the C/C++ runtime version required to run TF 3.5.5.2?

Note that that customer can use activation w/o issue using 4.0.9.6. Only TF64 fails.

Hey Francois,

That version is over 5 years old. A ton of bug fixes have been made over the last half-decade. Use the latest version (currently 4.1.8.0) with the latest TFS.

>> "This possibly indicates an invalid/missing C/C++ runtime DLL."

Possibly. Or a bug in a 3rd party library we used at the time. At any rate, use the latest version.

>> "From other threads I believe that only dynamic linking was supported prior to 4.1 (correct me if I'm wrong) so TF would be looking for a runtime DLL."

No, we've had static linking for a while. And all of the dynamic build build-in the C++ dependencies required (so no MSVC++ dependencies need to be installed on the system).

>> "Question, what is the C/C++ runtime version required to run TF 3.5.5.2?"

None. It's built into the dlls.

>> "Note that that customer can use activation w/o issue using 4.0.9.6. "

More information is needed. Use TFS 4.1.8.0. If the customer is getting errors, please provide enough information so we can actually help: https://wyday.com/limelm/help/faq/#useful-reports

Ok, thanks for the info. Considering how old it is, we've had surprisingly little issues. But yes, we have to try the newest. Is it just a drop-in replacement? We should expect things to work w/o changes to the code?

I also saw you are planning a hosted TFS server? That sounds really great, do you have an ETA?

>> "Is it just a drop-in replacement?"

We recommend using the latest header and doing a recompile. It *should* work without a recompile, but it's not recommended.

>> "We should expect things to work w/o changes to the code?"

Yes. There are new error codes, however, so if you show human-readable errors to your users (recommended) then you'll need to account for the new error codes.

>> "I also saw you are planning a hosted TFS server? That sounds really great, do you have an ETA?"

Very soon. No hard date, but we're in the final stretch. We'll have a blog post about it over here once it's released: https://wyday.com/blog/