Patching: Files cannot be found in cabinet file

Ryan · Post by **Ryan** » Tue Aug 04, 2009 1:17 pm

I am getting an error during my patch upgrade process. The file '' cannot be installed because the file cannot be found in cabinet file ''

I have followed the white paper about patching exactly. What are some causes for this error? I know it has nothing to do with our network or package as the error suggests

Thanks

MichaelNesmith · Post by **MichaelNesmith** » Tue Aug 04, 2009 2:32 pm

I would try logging the setup as recommended on our support policy page:
http://www.installaware.com/support-service-options.htm

Ryan · Post by **Ryan** » Tue Aug 04, 2009 3:36 pm

It looks like the installer is having problems with the file Index_Chunk1.xml which is a new file that was added since 2.0.0.7

MSI (s) (BC:84) [16:27:15:621]: Executing op: FileCopy(SourceName=Index_~1|Index_Chunk1.xml,SourceCabKey=Index_7e17cIndex_Chunk1.,DestName=Index_Chunk1.xml,Attributes=4096,FileSize=28222,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,,,,,,,)
MSI (s) (BC:84) [16:27:15:652]: File: C:\\Program Files (x86)\\SourceFiles\\help\\Data\\Index_Chunk1.xml; To be installed; Won't patch; No existing file
MSI (s) (BC:84) [16:27:15:677]: Source for file 'Index_7e17cIndex_Chunk1.' is compressed
MSI (s) (BC:84) [16:27:15:689]: SOFTWARE RESTRICTION POLICY: Verifying object --> 'C:\\Windows\\Installer\\4eb19a6.msp' against software restriction policy
MSI (s) (BC:84) [16:27:15:895]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (BC:84) [16:27:16:011]: SOFTWARE RESTRICTION POLICY: C:\\Windows\\Installer\\4eb19a6.msp is not digitally signed
MSI (s) (BC:84) [16:27:16:124]: SOFTWARE RESTRICTION POLICY: C:\\Windows\\Installer\\4eb19a6.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (BC:84) [16:27:16:188]: Note: 1: 2318 2: C:\\Program Files (x86)\\SourceFiles\\help\\Data\\Index_Chunk1.xml
MSI (s) (BC:84) [16:27:16:208]: Note: 1: 1334 2: Index_7e17cIndex_Chunk1. 3: PCW_CAB_711F8470
MSI (s) (BC:84) [16:27:16:227]: Note: 1: 2205 2: 3: Error
MSI (s) (BC:84) [16:27:16:235]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1334
Error 1334. The file 'Index_7e17cIndex_Chunk1.' cannot be installed because the file cannot be found in cabinet file 'PCW_CAB_711F8470'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
MSI (s) (BC:84) [16:27:22:008]: Note: 1: 2205 2: 3: Error
MSI (s) (BC:84) [16:27:22:032]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (BC:84) [16:27:22:056]: Product: -- Error 1334. The file 'Index_7e17cIndex_Chunk1.' cannot be installed because the file cannot be found in cabinet file 'PCW_CAB_711F8470'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

Ryan · Post by **Ryan** » Wed Aug 05, 2009 7:19 am

MichaelNesmith,

Where do i go from here for troubleshooting? I have lots of other new files that where added without problems.

Do I need to create the full install for 2.0.0.8. Add that patch reference and then create my 2.0.0.8 patch?

I was thinking I could just add patch 2.0.0.7 and then change the install version to 2.0.0.8, and it would build the patch with any new files that it found that were added since 2.0.0.7.

Thanks

MichaelNesmith · Post by **MichaelNesmith** » Wed Aug 05, 2009 8:38 am

If its just this one file, in your patch build, I'd recommend copying this file directly over using Call DLL Function on CopyFileA in kernel32.dll through $SUPPORTDIR$.

Ryan · Post by **Ryan** » Wed Aug 05, 2009 9:30 am

Its several hundred files.

I just created 2.0.0.8 and added that to the patch references and then tried to build patch 2.0.0.8 and still get the same error.

MichaelNesmith · Post by **MichaelNesmith** » Wed Aug 05, 2009 10:07 am

You don't add the same base version as the patch reference, this could cause problems. Please re-read the patching whitepaper and make sure you digest the concepts therein. I think you might be mistakenly understanding the patch reference idea.

Ryan · Post by **Ryan** » Wed Aug 05, 2009 10:13 am

Michael,

I didnt think I was supposed to as the white paper didnt, but the whitepaper's example only modified an existing file also and didnt have the patch add any new files.

I am just really trying to get this solved and figured while I was waiting for other ideas, I would try it out.

*Edit*

1) What about the log file that I sent you?
2) Finding every single file that is different and having to code the installer to copy over these files is something the patch is supposed to do.

MichaelNesmith · Post by **MichaelNesmith** » Wed Aug 05, 2009 10:40 am

Pop Quiz:

What is a patch reference?
How is the installer built in patch mode?