J
jfbradfo
[COLOR=rgba(85, 85, 85, 1)]I have an issue with extracting a tar file with relatively long paths (~120+ chars) into a folder structure that is also relatively long (130 chars), as some of the file names are long enough they exceed the 260 character limit for path names. We have enabled the Enable Win32 long paths policy, as well as ensured that the LongPathsEnabled registry value is set to 1, and the servers were rebooted after the change. I'm using 7-Zip v19.00 to do the extracts and have used both TAR and ZIP files to ensure that the format doesn't play a part.
On a Windows Server 2016 instance, the extract works correctly with no errors. However, on a Windows Server 2019 instance, using the same TAR and ZIP files and the same target path to extract (130 chars), several files fail to extract, apparently because the paths are longer than 260 characters. We validated this by shortening the extract target path slightly, which allowed all files to extract without error.
We are able to make this work with the 7-Zip GUI and with WinZip, but the command line fails consistently on Server 2019. [/COLOR]
The one server configuration difference we noticed was that the Server 2016 box has .NET 4.7 and the Server 2019 box has .NET 4.7.2.
[COLOR=rgba(85, 85, 85, 1)]What differences in long path handling have we missed in Server 2019 vs 2016?
Thanks in advance![/COLOR]
Continue reading...
On a Windows Server 2016 instance, the extract works correctly with no errors. However, on a Windows Server 2019 instance, using the same TAR and ZIP files and the same target path to extract (130 chars), several files fail to extract, apparently because the paths are longer than 260 characters. We validated this by shortening the extract target path slightly, which allowed all files to extract without error.
We are able to make this work with the 7-Zip GUI and with WinZip, but the command line fails consistently on Server 2019. [/COLOR]
The one server configuration difference we noticed was that the Server 2016 box has .NET 4.7 and the Server 2019 box has .NET 4.7.2.
[COLOR=rgba(85, 85, 85, 1)]What differences in long path handling have we missed in Server 2019 vs 2016?
Thanks in advance![/COLOR]
Continue reading...