Tivoli extract failure in custome site only

(imported topic written by DotA)

Weird issue: I create a task that simply copies a directory to the root of C: using the Software Deployment Wizard in my personal “site” and it runs fine, status = Complete. But if I create a custom copy of this task and assign it to a Custom site where others can see and use it, it will fail trying to extract the .tmp file. Log file shows “Unable to extract archive file”. I’ve also tried recreating the task from scratch directly into the Custom site and it still fails at the same point. All other tasks created in my site and copied over to the custom site have had no issues, just this one. Natively the directory is 173 MB, in Tivoli it compresses to 65 MB. Has anyone experienced this before?

(imported comment written by BrianPGreen)

I’m not sure what could be going wrong. How was the archive file created?

(imported comment written by DotA)

The Task was simply created using the Tivoli Endpoint Manager 8.2 Console, Windows Software Distribution Wizard.

prefetch Client-64-prd.tmp sha1:229a19da6a6d83bc37b3ea52709a9d29a5ae770d size:68080100 http://bigfix.company.com:52311/Uploads/229a19da6a6d83bc37b3ea52709a9d29a5ae770d/Client-64-prd.tmp extract Client-64-prd.tmp //Move files to C:\Client move __Download\Client "C:\Client"

fails at the extract line. Log file shows “Unable to extract archive file”.

BTW I have the same task created the same way for distribution to 32 bit OS that does not fail when a custom copy is made and moved to another site.

(imported comment written by sinucus)

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/BFArchive%20Tool

Can you drop into DOS and use the BFArchive tool to extract the package?

(imported comment written by DotA)

Well Bigfix is able to extract it when it’s deployed from my personal site but not from any other sites within the 8.2 console. I’ve tried this on the same PC, when the package is deployed from my personal site the .tmp file extracts and the move command completes but when the same package is deployed from another site to the same PC the extract fails.

Are you suggesting to deploy the package and let it fail, then try using the BF Archive tool to manually try and extract the .tmp file on the PC?

(imported comment written by BrianPGreen)

Are you suggesting to deploy the package and let it fail, then try using the BF Archive tool to manually try and extract the .tmp file on the PC?

Yeah, I agree that you should try that. It’d be interesting to see if BFArchive and extract it successfully, or what happens when it tries.

(imported comment written by DotA)

Update:

It works fine when extracted via the BFArchive.exe tool within the folder named “opsite1”, however, errors when attempting to extract it via the BFArchive.exe tool within the folder named “CustomSite_Custom-3a_opsite2_Windows_-2d_PC”

It’s as we thought, the file path was too long.