Problem: Source Length is 0

Save up to 50% on our desktop apps during our Year End Sale, including DisplayFusion, ClipboardFusion, FileSeek, LogFusion, TrayStatus, and VoiceBot!

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

<< Discussions Reply

DS1508

37 discussion posts

Hi,
I'm just trying to call Logfusion via Batch file.

Code
Copy
Select All

start "" "C:\Program Files (x86)\LogFusion\LogFusion.exe" "%Logfile%"

But when Logfusion starts, I always get:
An error has occurred while opening this log.
Source length is 0.

I have to close this dialog by clicking on OK. Then the program opens and shows the log.
If Logfusion is running, I don't get the error. Only when the program starts.

Any suggestions how to fix this?

Thx,
Domi

Jun 22, 2016 • #1

When we test here with the same batch file code, it seems to work without throwing that error. If you just create a simple text file with some text and set that as %LogFile%, do you still get this error? I'm wondering if the error is related to the specific log file you're opening.

Jun 23, 2016 • #2

DS1508

37 discussion posts

Just found out, that it also happens, when I start LogFusion via doubleclick from the desktop.
I've set it to open last open logfiles. But these exist (files on lokal HDD). Debug Log does not open again after closing LF.
Closing all logs, then close the program, and restart it from Desktop, also shows this error.
I don't know witch file length is ment.

Jun 24, 2016 • #3

Thanks, that's really strange! Could you backup your LogFusion Settings (Settings > Options > Export) and attach them?

Jun 24, 2016 • #4

DS1508

37 discussion posts

Here's the file. hope it helps.

• Attachment [protected]: LogFusion Backup (2016-06-25 @ 01-01, 4.2.0.0, VENUS).reg [79,046 bytes]

Jun 24, 2016 • #5

Thanks! For some reason, there are a bunch of old logs that don't have a source file name for some reason in the registry. If you exit LogFusion, then delete the registry key below, you shouldn't run into this error any more.

HKEY_CURRENT_USER\SOFTWARE\Binary Fortress Software\LogFusion\LogSources

I've put this on our list as well, as we should be handling that error more gracefully