Tickstory.exe crash on Volante database (Win Server 2022) – need help clearing corrupted DB

[andres042986]

Hello,

I’m running Tickstory 1.9.8.7 on Windows Server 2022 and immediately see an unhandled exception in Volante.Impl.LruObjectCache (InvalidOperationException) every time I launch the app.

What I’ve tried so far:

• Reset WinHTTP proxy to direct access
  Enabled TLS 1.2+ and .NET strong-crypto registry flags
  Uninstalled/reinstalled Tickstory as Administrator
  Cleared %APPDATA%\Tickstory and %LOCALAPPDATA%\Tickstory
  Used ProcMon/Process Explorer to locate and delete any Volante DB files (no obvious .vdb or .dat in profile or install folders)

Despite all this, the same crash in the database finalizer persists.

What might help:

• Guidance on the exact location(s) where Tickstory stores its Volante database on Windows Server 2022
  Any tool or procedure to fully clear or rebuild the embedded DB
  A portable ZIP or patched build that can bypass or repair the corrupted Volante store

Thank you for your assistance!
—I’m happy to provide additional logs or crash dumps if needed.

[tickstory]

Hi Andres042986,

I'm not sure where this error is from as Tickstory does not use a Volante database. I would suggest installing the software on a clean build and making sure .NET 4.8 (specifically this version) is installed on the machine (if it's already installed, it might be worth selecting 'Repair' on the installer to ensure there are no corrupted files).

Hope this helps.

[andres042986]

Hello again,

Thanks for your suggestions. Unfortunately the problem persists. When I launch Tickstory under the new Windows Server 2022 user, the UI immediately shows:

Could not contact servers. Please check your internet connection.

and then it crashes. In Event Viewer I see this .NET error:


---------------
Application: Tickstory.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.WeakReference.set_Target(System.Object)
at Volante.Impl.LruObjectCache+Entry.clear()
at Volante.Impl.LruObjectCache.ClearDirty(Int32)
------------------------

So far I’ve:

Reset WinHTTP proxy to direct access
Enabled TLS 1.2 and .NET strong-crypto flags
Repaired .NET 4.8 and run DISM/SFC
Fully uninstalled and reinstalled Tickstory as Administrator
Cleared all Tickstory folders under %APPDATA% and %LOCALAPPDATA%
Searched for and removed any stray .vdb/.dat files with ProcMon

I’m a bit stuck—could you please help me identify where Tickstory keeps its local cache or data files on Server 2022? Any guidance on how to clear or rebuild that store would be much appreciated. If there’s a portable ZIP or debug-logging build I could try, that might help isolate the issue as well.

Thanks again for your assistance,

[tickstory]

Hi Andres,

Do note that Windows Server 2022 has many different configurations, some which do not fully support UI-based applications. That said, we have taken the time to install the software on a basic installation of Windows Server 2022 (Desktop Experience) and the software is working correctly. No additional software needed to be installed nor any modification of base configurations.

The "Volante database" error is a misdirection to the actual cause of the problem. A fatal error before the software can even start usually indicates that a Windows component is either corrupted or missing. You can try uninstall .NET 4.8 and reinstall it and see if that helps (as opposed to a 'Repair').

Finally, check that Tickstory has the ability to connect to the internet and that there is nothing blocking its operation. If your internet connection is functional and Tickstory says it isn't, this means that something like a firewall is stopping it. There may be other restrictions on your Windows box that might also be causing the issue.

If possible, the best way forward would be to use another machine with a full, unmodified installation of Windows on it.

Hope this helps.