I have a problem where a suite package fails to unpackage any packages.
This has occurred with some customer's systems, and with a system in Custom service (tech support). It does not occur on all systems.
I have tried replicating the problem on my system, but all attempts are successful. I have compared logs from a successful process and one that fails, but there is nothing to indicate what the problem can be other than the line: Stage parcel status: 8007007b
On a successful attempt the status value is 0.
We have tried downloading the files again, and the package size looks good. We have tried moving the 'setup.exe' file from the downloads directory to a new directory off of the system drive. Our command line typically looks like this
"C:\\setup.exe" /stage_only ISRootPath="C:\
This command line will work for me but not for one of the tech support people and on some customer's systems. Here is a sample of the log file for the relevant bits:
11-18-2014[11:49:23 AM]: Stage parcel {1F23896A-A487-C52D-A108-F3691BBE59C7}, parcel action: 1 11-18-2014[11:49:23 AM]: Engine: property 'ISParcelStatus' value now 'SAP Crystal Reports runtime engine for .NET Framework 4 (32-bit)' 11-18-2014[11:49:23 AM]: This stage path: ”C:\installers\Staging”\{1F23896A-A487-C52D-A108-F3691BBE59C7}\ 11-18-2014[11:49:23 AM]: Stage parcel status: 8007007b
For the tech support system, if we do not create the target folder manually first, then it works for him. I do not know why targeting a pre-created folder works for me but not for tech support.
