LogViewPlus Support

Unzipping Files with Long Filenames Not Working

https://www.logviewplus.com/forum/Topic2232.aspx

By StefanBu - 14 Aug 2024

Hello Support Team,

When I add a Zip file with a long name to LogViewPlus using drag and drop, the blue progress bar keeps moving endlessly, and nothing happens. However, if I shorten the name of the same Zip file, it works flawlessly.

Here is an example:

Does not work:
MM.Wfs.Prepress.Imposer.App.Console(1)_Auxiliary_2024-07-20T071451030Z.csv.zip

Works:
Console(1)_Imposer_2_2024-08-07T055652708Z.csv.zip

Best regards,
Stefan
By LogViewPlus Support - 10 Sep 2024

Hi Stefan,

Apologies for the slow reply. Our forum software identified this message as spam and it was only just discovered.

I tested with the log file name suggested and the zip file opened successfully on my machine.  Are you using the latest version of LogViewPlus?  Maybe the full path to the file exceeds 255 characters?

Thanks,

Toby
By StefanBu - 11 Sep 2024

Hi Toby

Yes I am using the latest version.
I did some more testing and found out that not only the name of the zip file has an influence but also the name of the csv file inside the zip.

I have tested the following names:

Not working:
MM.Wfs.Prepress.Imposer.App.Console(1)_Imposer_2_2024-09-11T115854504Z.zip
contains:  MM.Wfs.Prepress.Imposer.App.Console(1)_Imposer_2_2024-09-11T115854504Z.csv

Working:
MM.Wfs.Prepress.Imposer.App.Console(1)_Imposer_2_2024-09-11T115854504Z.zip
contains: a.csv

I have also put the not working zip file to c:\temp to have a short full path. But it's also not working.

Regards Stefan
By LogViewPlus Support - 11 Sep 2024

Hi Stefan,

Thanks for the update.  I was able to recreate the issue locally.

The problem is that the full path to the target file is exceeding the 260 character limit.  When you open a zip file in LogViewPlus, the application extracts the file contents to a temporary directory such as:
C:\\Users\\[USER]\\AppData\\Local\\Temp\\LogViewPlus\\-3473765059386909220

In this case, LogViewPlus is appending the zip file, a staging folder, and the target file as:
\\MM.Wfs.Prepress.Imposer.App.Console(1)_Auxiliary_2024-07-20T071451030Z.zip\\MM.Wfs.Prepress.Imposer.App.Console(1)_Auxiliary_2024-07-20T071451030Z\\MM.Wfs.Prepress.Imposer.App.Console(1)_Auxiliary_2024-07-20T071451030Z.log

The result is a string that is approximately 280 characters - exceeding the limit.

The 260 character limit is a legacy issue and we really should support longer paths in LogViewPlus. I can work around the issue for the zip file, but other aspects of the program fail to adapt to the extended path length.  More testing is needed.  I will take a closer look and see what we can do for the next release.

Thanks again,

Toby
By LogViewPlus Support - 3 Dec 2024

Hi Stefan,

I just wanted to let you know that we have now released LogViewPlus v3.1.16 as a BETA release.

This release addresses the issue with long file path names discussed above.  For this to work, you will need to enable log path names in Windows by setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled = 1

Thanks again for bringing this issue to our attention. Please do let me know if you have any further questions or issues.

Toby