IA10.10 Patch Error: the file cannot be found in cabinetfile

[Frank Jona]

Hi,

this error still occurs in IA 10.10. I've done a lot of testing (LONGCOMPONENTS=TRUE, NOHARDLINKS=TRUE etc.) and at the end the patch build has a problem with files where the file names are exatly 56 characters. In a former post I've read that someone has problems with 16 characters. The 16 character problem went away after setting LONGCOMPONENTS=TRUE.
So there is still the 56 character problem.
Any help or fixing is highly appreciated

Frank

[giaviv]

Dear Frank,

Which file in your architecture contains 56 characters?

[Frank Jona]

Hi,
I've done some more tests and I come to the following results:
It seems to me that this error has something to do with the filename itself.
These one doesn't work:
xboundActFurtherProcessingStructuredExport.resources.dll to $TARGETDIR$
xboundActFurtherProcessingStructuredExport.resource1.dll to $TARGETDIR$
x1oundActFurtherProcessingStructuredExport.resources.dll to $TARGETDIR$

This one works:
x11oundActFurtherProcessingStructuredExport.resources.dll to $TARGETDIR$
1234567891123456789212345678931234567894123456789512.dll to $TARGETDIR$


As you can see, the file 1234567891123456789212345678931234567894123456789512.dll contains 56 characters but it works. x1oundActFurtherProcessingStructuredExport.resources.dll has 56 characters as well but it doesn't work.

I found in the log file that files that does'nt work have no extension (looks like a hash) at the end
Excerpt:
INFO File Key: xbound7e17cxboundIPSLib.dll24PE8A9DA9C_124 is newly added
INFO File Key: xbound7e17cxboundActFurtherProcessingStructuredExport.resources. is newly added
INFO File Key: xbound7e17cxboundActFurtherProcessingStructuredExport.resource1. is newly added
INFO File Key: x11oun7e17cx11oundActFurtherProcessingStructuredExport.resources is newly added
INFO File Key: ID_1234567e17c12345678911234567892123456789312345678941234567895 is newly added

The content and size of the file doesn't matter.


Any idea?
Frank

[giaviv]

Dear Frank,

Could you please send the project you are testing with that demonstrates this problem to support at installaware.com?
I want to test this with different versions of IA / OS.

[Frank Jona]

Hi ,
I've attached my test setup. For testing the patch you have to copy the files in directory \InterneObjekte3\OldVersions into \InterneObjekte3\AlwaysInstall and create version 1 (save the files before override). Install version 1 and activate the original version (the original versions are the newer ones), create version 2 and try to patch.

The file that creates the error is xboundActFurtherProcessingStructuredExport.resources.dll. I've added some more files to show you that it depends exactly on this specific file name.

Cheers
Frank

[giaviv]

Dear Frank,

This problem is very interesting! It looks like there is an issue what how the actual cabinet file is being created.
Is it possible for you to use a different file name in that case?

[Frank Jona]

Hi,
Most of our files names are stored in a repository on our customer site. To change this name means to write an update program. This is an extra effort wich we want to avoid.
B.t.w. I encountered the same bevavoir with the name XBOUNDIPSLIB.DLL. After setting LONGCOMPONENTS = TRUE the patch was OK.

Cheers
Frank

[giaviv]

Dear Frank,

I sincerely apologize for this. Perhaps we can think of a way to work around this? What about changing the names and then renaming them after the installation?

[giaviv]

Dear Frank,

Are you sure that in ALL your version the LONGCOMPNENTS is set to TRUE?