Patching with New File to Install, Error in Cabinet File

jtoledano · Postby **jtoledano** » Mon Mar 16, 2015 1:38 pm

I am trying to Patch my older installation but get an error during the patch installation. Error is that the file cannot be installed because the file cannot be found in the cabinet file.

This is correct, the file that it flags was not part of the original, older installation. It is a new file to be added to my application. Currently, I am on Patch 5, the previous 4 patches installed with no errors. Only now with this latest patch, when I try to add a new file does it error.

The patch compiled without errors specifying the base install and the 4 subsequent installations. This last one having the one new file.

I am using InstallAware Studio 18.

James

Postby **FrancescoT** » Mon Mar 16, 2015 2:48 pm

Dear James,

Instead I suppose the error is caused by the new file that seems to be not present with the cabinet.

did you try to generate a log of the patch?
setup.exe /l=<logfilepath>

Regards

jtoledano · Postby **jtoledano** » Mon Mar 16, 2015 7:37 pm

Francisco,

Attached is the relevant part of the log file where the error occurs with the file: chaincluster.exe. After this point the patch install reverts back to the base install.

Correct, I am trying to install a new file that was not in the base installation and not in the cabinet file. However, I created another patch as a test that did not include the above file, but did include two other new files, although not exe's, that were not in the base installation and the patch ran OK, and installed these two new files.

Does the log show anything that could provide a clue as to why this one file won't patch?

Thanks,

Postby **FrancescoT** » Tue Mar 17, 2015 12:37 pm

Dear James,

for what I see by your log the "ChainCluster.exe" is not part of the patch build you are trying to install.

Are you able to replicate the issue with any machine?
If yes, you may verify if there is something strange during the patch build. I suggest you to re-build your patch with enabling the "Leave Debug files" flag available in patch options (Press SHIFT+CTRL+F11 then select the "patch" node from the left tree pane).

In this way you could verify if the file have been effectively included with the current patch build (the debug files will be available under the Patch output folder).

Regards

jtoledano · Postby **jtoledano** » Wed Mar 18, 2015 12:19 pm

Thanks for all those tips. I did create another patch with Leave Debug Files. Attached is the log.

The file is being included with the patch, as shown in the log, along with the other two new files. They are shown immediately before the chaincluster.exe file in the log. And the file is in the folder Upgraded Package. But the patch still fails with the same error message. If I do a complete install, the file in question does install.Just not from the patch.

James

Postby **FrancescoT** » Wed Mar 18, 2015 2:20 pm

Let me check your files and I'll be back to you.

BTW, you missed to answer my previous question.
Are you able to replicate the issue with any machine?

and then,
If you install your base package and then your latest patch (the one that seems to fail), do you still receive the error?

In addition;
are all projects, the Base project and each single Patch project, have been built with the "Always Cache Setup Sources" checked (not filled)?

"This three-state check-box lets you control setup source caching. When the box is filled, the default source caching option (as described above for each build type) is in effect. When cleared, setup sources are never cached. When checked, setup sources are always cached."

Regards

jtoledano · Postby **jtoledano** » Wed Mar 18, 2015 2:44 pm

Good questions.

Yes, I can replicate with any machine. I did install the base version and tried the patch on this version, and it failed. I also tried to patch different versions, same error. By different versions I mean different base versions.

Yes, the option to always cached was always checked, not filled. I made this mistake years ago and I know not to make it again.

Thanks again.

Postby **FrancescoT** » Thu Mar 19, 2015 1:16 pm

Dear James,

unfortunately I am not able to identify the possible error.

If you have any chance to share with me your projects, I can try to verify what happens.
In this case I need to receive at least the base project and your latest patch project (along with all the used files).

Regards

jtoledano · Postby **jtoledano** » Thu Mar 19, 2015 3:03 pm

Thanks Francisco,

I'm doing more tests, renaming the file, adding different exe's, etc. If I can't resolve I'll figure out a way to send you the files. They are large so I will need to be through ftp.

I'll be in touch.

jtoledano · Postby **jtoledano** » Tue Mar 01, 2016 12:00 pm

Francisco,

A followup to this earlier post. The solution I came up last year with was just to rename the file and it patched without a problem. However, I am now on Patch 12 and I am getting the same error with another file.

But I see now there is a common thread, that both these files at one point were in the original installation, removed in a later patch, and then later put back into a later patch to be installed. The question would be how can I tell InstallAware to ignore what is in its history and simply install the file?

I'm using Studio XE3.

James

Postby **FrancescoT** » Tue Mar 01, 2016 2:15 pm

Dear James,

unfortunately, you cannot!
It's not possible to to ignore what is the file's history in a patch ... otherwise, it's not a patch.

I don't know if you are including such file as a single file (eg. Install Files x:\path\myfile.ext) or if this is included along some other files from a source folder (eg. Install Files x:\path\*.*). If it's true the second case, you may try to include such file with a single Install file command.

I am sure you already know, but Please consider that Patches have to be used to deploy minimal updates only ...and for what I see, you are already on version 12 with your patch.

Regards

jtoledano · Postby **jtoledano** » Tue Mar 01, 2016 3:35 pm

All good points. I'll try the install file within the patch script. Didn't think of that. Thanks for the tips.

James

jtoledano · Postby **jtoledano** » Wed Nov 30, 2016 4:05 pm

Hi Francisco,

I am having similar problems with a different patch for the same application. I could not resolve my problem from earlier in the years, so I created an entirely new build and distributed it to our customers. From this new build I am having the similar Error in Cabinet File when I try to install a patch to this new build.

I started getting this error from the get go for this first patch I am building, for the last two weeks. Through testing I have narrowed it down to 4 files. When I exclude these files the patch works. When I include these files the patch fails. These are four new files to the app. It is not due to them not being in the original application build as I have other files in another folder that are new and install correctly.

I have attached the log file from the patch fail. The four files that will not patch are named:

ndvi.sm0
ndvi.sm1
ndvi.sm2
ndvi.smt

Any insight would be helpful.

James