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;
The trace text report generation now runs as expected.
Another VMworld is upon us!!! Sadly, it's only virtual again this year. However, that does…
As part of my recent move to Google, I'm working on quickly getting up to…
I am delighted to announce the next chapter in my career. Today is my first…
In episode thirteen of The VCDX Podcast, I am joined by two special guests who…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…
View Comments
I see the bureaucloud banner on the right side. Are they a sponsor?
Also, I've seen that if you map a drive to the network share hosting LogMon, that will fix the issue as well.