Contact the company that develops the software you're using (that's not us). We develop the licensing for other software products. We cannot provide support for their software.
TurboFloat.dll errorLocked
DavidPWe have an Outlook add-in that uses your Licensing software. We have a client who is experiencing Outlook crashes intermittently citing turbofloat.dll. The behaviour is as follows:
Outlook quits at the splash screen with the following two appcrashes present in Windows application log. Sometimes Outlook will eventually just start up, more often though starting Outlook in safe mode.
Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 29/04/2019 Time: 09:15:46 User: N/A Computer: ****Description: Faulting application name: OUTLOOK.EXE, version: 14.0.7229.5000, time stamp: 0x5c465847 Faulting module name: TurboFloat.dll, version: 4.0.9.6, time stamp: 0x58e656e7 Exception code: 0xc0000005 Fault offset: 0x0001133d Faulting process id: 0x202c Faulting application start time: 0x01d4fe63b9959193 Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE Faulting module path: C:\Program Files (x86)\DocsExpert\ThreadPrint\TurboFloat.dll Report Id: e4520d02-1cf2-40e9-ad01-619868d53340 Faulting package full name: Faulting package-relative application ID:
Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 29/04/2019 Time: 09:14:59 User: N/A Computer: ****Description: Faulting application name: OUTLOOK.EXE, version: 14.0.7229.5000, time stamp: 0x5c465847 Faulting module name: KERNELBASE.dll, version: 10.0.17134.441, time stamp: 0x3da51fd0 Exception code: 0xe0434352 Fault offset: 0x00111812 Faulting process id: 0x21bc Faulting application start time: 0x01d4fe639dd5afe7 Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 70db2ed4-c3a9-4355-bebf-8c6eb4852362 Faulting package full name: Faulting package-relative application ID:
We have got the client testing with an additional Turbo Float Server on the local machine as this seems to prevent the issue. We suspect there is something up with their network and the connection to the Turbo Float Server but have you had anyone else experience this or know why a crash is happening rather than an error message?