Red Hat Bugzilla – Bug 1294626
Path too long error on unzipping the patch using Extract All on Windows Server 2008 R2
Last modified: 2017-10-02 13:21:51 EDT
Created attachment 1110138 [details]
Description of problem:
Tried to unzip the patch on Windows Server 2008 R2 using Extract All and specified "C:\" directory as extraction root dir.
While extracting, it shows path too long error for file 'CallTimeDataConverterValidator.class'. Please refer the attached screenshot.
Version-Release number of selected component (if applicable):
OS: Windows server 20008 R2
Build: JON 3.3.5 DR01 build
Steps to Reproduce:
1) Download the JON 3.3.5 DR01 patch from:
2) On Windows 2008 R2, try to unzip jon-server-patch-3.3.0.GA.zip using Extract All
3) Specify "C:\" directory as extraction root dir.
4) It shows the path too long error for file 'CallTimeDataConverterValidator.class'.
Path too long error for file 'CallTimeDataConverterValidator.class' while extracting the patch.
Adding some more info:
This issue exists in JON3.3.4 as well if we use Extract All to unzip the patch.
If we use cygwin unzip, the issue does not exist in JON3.3.4 and JON3.3.5DR01 and unzip works without error.
Some windows compression tools have problems with file path names longer than 256 characters (probably general problem for all tools using MAX_PATH - https://support.microsoft.com/en-us/kb/177665)
Tested tools which are affected:
- winrar 4.20
- winzip 20
- integrated windows explorer in Windowns server 2008 R2
Tested tools which are not affected:
Could it be related to this: https://support.microsoft.com/en-us/kb/2891362 ?
If so, there is Hotfix for Windows Server 2008 R2.
Moving to ON_QA as available for test with the following binary:
*NOTE Build represents JON 3.3.9 DR01 build.
Please report issues as you encounter them.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.