Package extract issue

Content Authoring
1

(imported topic written by SystemAdmin)

Hello,

I am experiencing a very strange errors on a fixlet that I am creating. The fixlet downloads and extracts a package and should move & install it. I used the Software Distribution Wizard to upload it and generate the download & extract code for me, and just added a few lines of code to copy it to a different location and run the installation:

download http:
//168.74.26.100:52311/Uploads/1a85e3e2d492075dc540f49e137442828e16dd7e/CPS45_EN_W2K3.tmp 

continue 

if 
{(size of it = 290988685 AND sha1 of it = 
"1a85e3e2d492075dc540f49e137442828e16dd7e") of file 
"CPS45_EN_W2K3.tmp" of folder 
"__Download"
}   waithidden 
"{pathname of system folder & "\cmd.exe
"}" /C 

if not exist 
"{(value of variable "windir
" of environment) & "\Temp\CPS45_EN_W2K3
"}" md 
"{(value of variable "windir
" of environment) & "\Temp\CPS45_EN_W2K3
"}" extract CPS45_EN_W2K3.tmp   waithidden 
"{pathname of system folder & "\cmd.exe
"}" /C xcopy /s 
"{(pathname of client folder of current site) & "\__Download
"}" 
"{(value of variable "windir
" of environment) & "\Temp\CPS45_EN_W2K3
"}"   waithidden 
"{pathname of system folder & "\cmd.exe
"}" /C cd  
"{(value of variable "windir
" of environment) & "\Temp\CPS45_EN_W2K3
"}" & CitrixBigFix32.bat

When the fixlet is ran it produces the following error:

At 15:10:49 -0400 - ActionLogMessage: (action 210319 ) starting action At 15:10:53 -0400 - CustomSite_MGTI-2dESM (http:
//168.74.26.100:52311/cgi-bin/bfgather.exe/CustomSite_MGTI-2dESM) Command succeeded (Using download manager collected file) download http:
//168.74.26.100:52311/Uploads/377331eb759515c71ce14ecaa4bac26e323a212a/CPS45_EN_W2K3.tmp (fixlet 210319) At 15:12:31 -0400 - GatherHashMV command received. Already have 

this version of site. At 15:13:23 -0400 - CustomSite_MGTI-2dESM (http:
//168.74.26.100:52311/cgi-bin/bfgather.exe/CustomSite_MGTI-2dESM) Command succeeded (evaluated 

true) 

continue 

if 
{(size of it = 290987243 AND sha1 of it = 
"377331eb759515c71ce14ecaa4bac26e323a212a") of file 
"CPS45_EN_W2K3.tmp" of folder 
"__Download"
} (fixlet 210319) At 15:14:00 -0400 - CustomSite_MGTI-2dESM (http:
//168.74.26.100:52311/cgi-bin/bfgather.exe/CustomSite_MGTI-2dESM) Command failed (Unable to extract archive file.) extract CPS45_EN_W2K3.tmp (fixlet 210319) At 15:14:14 -0400 - CustomSite_MGTI-2dESM (http:
//168.74.26.100:52311/cgi-bin/bfgather.exe/CustomSite_MGTI-2dESM) Relevant - test (fixlet:210318) At 15:14:14 -0400 - ActionLogMessage: (action 210319 ) ending action At 15:14:14 -0400 - actionsite (http:
//168.74.26.100:52311/cgi-bin/bfgather.exe/actionsite) Not Relevant - test (fixlet:210319)

The weird part of it is that most of the files were successfully extracted in the site’s __Download folder. I did some basic comparison between the files of the original package and the files that made it across and it seems that the problem starts at a specific folder depth, so I am wondering if there’s some kind of path length limitation? (everything above the following path is present but a bunch of files underneath are missing “C:\Program Files\BigFix Enterprise\BES Client__BESData\CustomSite_MGTI-2dWindows__Download\Support\SqlExpress_2005_SP1\SqlExpress\setup”)

Thank you.

Angel

2

(imported comment written by BenKus)

Hi Angel,

Is it possible that you ran out of disk space? It is a pretty big package so perhaps you only have a couple hundred MB left and it couldn’t extract all the way…

Ben

3

(imported comment written by SystemAdmin)

Hi Ben,

No disk space was not an issue, the machine had about 40 gb free. However, I did try to remove the deeper folders that were causing the issue and repackaged the fixlet and that worked fine, which I think confirms my theory that the length of the path is the problem.

Thanks,

Angel

4

(imported comment written by jessewk)

Hi Angel,

Is it possible you can create a package that reproduces the issue and either post it here or send it to me in an email?

If we can reproduce the issue in-house I will file a bug.

Jesse

5

(imported comment written by SystemAdmin)

I was able to pinpoint the root cause with the help of Support, so I wanted to share in case someone else sees this strange issue. In my case, McAfee was detecting some of the files from the package as dangerous and deleting them as they were being extracted which was causing the errors.