Thinapp: Log Monitor Trace Error

Just a quick post about an error I just got when I was trying to generate a text trace report using the Thinapp Log Monitor. The error I received was:

<UNC path to Thinapp Bin>\<trace unique identifier>.trace: Error
– – – – – – – – end of file – – – – – – – – –  

If I then looked at the trace text file it only had a small amount of information, most of the trace information you would expect to see was missing.

The reason for this error was because I was running Thinapp Log Monitor from a network share. 

To fix this problem I copied to a local drive;

  • log_monitor.exe
  • logging.dll
  • setup capture.exe

The trace text report generation now runs as expected.

Simon Long

View Comments

Share
Published by
Simon Long

Recent Posts

Google Cloud VMware Engine @ VMworld 2021

Another VMworld is upon us!!! Sadly, it's only virtual again this year. However, that does…

3 years ago

Google Cloud VMware Engine – Learning Resources

As part of my recent move to Google, I'm working on quickly getting up to…

3 years ago

Hey Google!

I am delighted to announce the next chapter in my career. Today is my first…

3 years ago

EP13 – Defending Remotely

In episode thirteen of The VCDX Podcast, I am joined by two special guests who…

3 years ago

Getting Started With Oracle Cloud VMware Solution (OCVS) – Migrating Workloads Using VMware HCX

In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…

3 years ago

Getting Started With Oracle Cloud VMware Solution (OCVS) – Connecting To An On-Premises Environment

In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…

3 years ago