PDA

View Full Version : Patch error "Error reading setup initialization file"



NewsArchive
05-10-2001, 12:00 AM
I added the msi file in the Release under "Previous Package," compiled & ran
the patch creation wizard again and I still have the same error message.
Any other ideas of what I am doing incorrect?


"Robert M. Dickau (InstallShield)"
<i_wish_i_had_time_to_answer_individual_questions_through_e-mail_but_i_don't
@installshield.com> wrote in message news:3af9b723@12.41.20.38...
> The patch builder does this (includes entire files) if the file keys
> (primary keys in the File table) don't match up between the old and new
> packages. To get the file keys to match up (and therefore create true file
> patches), you can browse for the earlier, pre-patch MSI database in the
> Media Type & Patch Optimization panel of the Release wizard.
>
> "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> news:3af9a3ba$1@12.41.20.38...
> > Has anyone ever received the following error message in the log file
once
> > the Patch creation wizard has completed.
> > (Using InstallShield Professional Windows Installer version 2.01)
> >
> > " Patch API could not create a small patch; using whole upgraded file."
> >
> > Any idea what this means? What am I missing?
> >
> > Thanks,
> > Wendy
>
> --
> Robert M. Dickau
> Senior Technical Trainer
> InstallShield Software Corp.
> www.installshield.com/training
>
>

NewsArchive
05-10-2001, 12:00 AM
No, I'm afraid I don't know what it could be, if you browsed for the earlier
MSI database; were both versions created from the same project? If you open
both databases with Orca, do the file keys in the File table match up?

"Wendy Weber" <wweber@charteroaksystems.com> wrote in message
news:3afaea54$1@12.41.20.38...
> I added the msi file in the Release under "Previous Package," compiled &
ran
> the patch creation wizard again and I still have the same error message.
> Any other ideas of what I am doing incorrect?
>
>
> "Robert M. Dickau (InstallShield)"
> <i> wrote in message news:3af9b723@12.41.20.38...
> > The patch builder does this (includes entire files) if the file keys
> > (primary keys in the File table) don't match up between the old and new
> > packages. To get the file keys to match up (and therefore create true
file
> > patches), you can browse for the earlier, pre-patch MSI database in the
> > Media Type & Patch Optimization panel of the Release wizard.
> >
> > "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> > news:3af9a3ba$1@12.41.20.38...
> > > Has anyone ever received the following error message in the log file
> once
> > > the Patch creation wizard has completed.
> > > (Using InstallShield Professional Windows Installer version 2.01)
> > >
> > > " Patch API could not create a small patch; using whole upgraded
file."
> > >
> > > Any idea what this means? What am I missing?
> > >
> > > Thanks,
> > > Wendy
> >
> > --
> > Robert M. Dickau
> > Senior Technical Trainer
> > InstallShield Software Corp.
> > www.installshield.com/training

NewsArchive
05-14-2001, 12:00 AM
Robert-
The files keys do match up in Orca. I get the same message even if I am
adding new files with the patch.

Patch API could not create a small patch; using whole upgraded file.
Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
Oak\COIS\DiskImages\DISK1\.\Charter Oak\Main.exe';
FTK=F3328_Main.exe; temp location=Family00\00026.FLE.
Patch API could not create a small patch; using whole upgraded file.
Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
Oak\COIS\DiskImages\DISK1\.\Charter Oak\Loader.exe';
FTK=F3363_Loader.exe; temp location=Family00\00027.FLE.
Patch API could not create a small patch; using whole upgraded file.
Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
Oak\COIS\DiskImages\DISK1\.\Charter Oak\LoaderDll.dll';
FTK=F3362_LoaderDll.dll; temp location=Family00\00028.FLE.

Any other suggestions?
Wendy



"Robert M. Dickau (InstallShield)"
<i_wish_i_had_time_to_answer_individual_questions_through_e-mail_but_i_don't
@installshield.com> wrote in message news:3afb2d96@12.41.20.38...
> No, I'm afraid I don't know what it could be, if you browsed for the
earlier
> MSI database; were both versions created from the same project? If you
open
> both databases with Orca, do the file keys in the File table match up?
>
> "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> news:3afaea54$1@12.41.20.38...
> > I added the msi file in the Release under "Previous Package," compiled &
> ran
> > the patch creation wizard again and I still have the same error message.
> > Any other ideas of what I am doing incorrect?
> >
> >
> > "Robert M. Dickau (InstallShield)"
> > <i> wrote in message news:3af9b723@12.41.20.38...
> > > The patch builder does this (includes entire files) if the file keys
> > > (primary keys in the File table) don't match up between the old and
new
> > > packages. To get the file keys to match up (and therefore create true
> file
> > > patches), you can browse for the earlier, pre-patch MSI database in
the
> > > Media Type & Patch Optimization panel of the Release wizard.
> > >
> > > "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> > > news:3af9a3ba$1@12.41.20.38...
> > > > Has anyone ever received the following error message in the log file
> > once
> > > > the Patch creation wizard has completed.
> > > > (Using InstallShield Professional Windows Installer version 2.01)
> > > >
> > > > " Patch API could not create a small patch; using whole upgraded
> file."
> > > >
> > > > Any idea what this means? What am I missing?
> > > >
> > > > Thanks,
> > > > Wendy
> > >
> > > --
> > > Robert M. Dickau
> > > Senior Technical Trainer
> > > InstallShield Software Corp.
> > > www.installshield.com/training
>
>
>
>
>

NewsArchive
05-15-2001, 12:00 AM
What does the rest of the patch-creation log say?

"Wendy Weber" <wweber@charteroaksystems.com> wrote in message
news:3b000833$1@12.41.20.38...
> Robert-
> The files keys do match up in Orca. I get the same message even if I am
> adding new files with the patch.
>
> Patch API could not create a small patch; using whole upgraded file.
> Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
> Oak\COIS\DiskImages\DISK1\.\Charter Oak\Main.exe';
> FTK=F3328_Main.exe; temp location=Family00\00026.FLE.
> Patch API could not create a small patch; using whole upgraded file.
> Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
> Oak\COIS\DiskImages\DISK1\.\Charter Oak\Loader.exe';
> FTK=F3363_Loader.exe; temp location=Family00\00027.FLE.
> Patch API could not create a small patch; using whole upgraded file.
> Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
> Oak\COIS\DiskImages\DISK1\.\Charter Oak\LoaderDll.dll';
> FTK=F3362_LoaderDll.dll; temp location=Family00\00028.FLE.
>
> Any other suggestions?
> Wendy
>
>
>
> "Robert M. Dickau (InstallShield)"
> <i> wrote in message news:3afb2d96@12.41.20.38...
> > No, I'm afraid I don't know what it could be, if you browsed for the
> earlier
> > MSI database; were both versions created from the same project? If you
> open
> > both databases with Orca, do the file keys in the File table match up?
> >
> > "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> > news:3afaea54$1@12.41.20.38...
> > > I added the msi file in the Release under "Previous Package," compiled
&
> > ran
> > > the patch creation wizard again and I still have the same error
message.
> > > Any other ideas of what I am doing incorrect?
> > >
> > >
> > > "Robert M. Dickau (InstallShield)"
> > > <i> wrote in message news:3af9b723@12.41.20.38...
> > > > The patch builder does this (includes entire files) if the file keys
> > > > (primary keys in the File table) don't match up between the old and
> new
> > > > packages. To get the file keys to match up (and therefore create
true
> > file
> > > > patches), you can browse for the earlier, pre-patch MSI database in
> the
> > > > Media Type & Patch Optimization panel of the Release wizard.
> > > >
> > > > "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> > > > news:3af9a3ba$1@12.41.20.38...
> > > > > Has anyone ever received the following error message in the log
file
> > > once
> > > > > the Patch creation wizard has completed.
> > > > > (Using InstallShield Professional Windows Installer version 2.01)
> > > > >
> > > > > " Patch API could not create a small patch; using whole upgraded
> > file."
> > > > >
> > > > > Any idea what this means? What am I missing?
> > > > >
> > > > > Thanks,
> > > > > Wendy
> > > >
> > > > --
> > > > Robert M. Dickau
> > > > Senior Technical Trainer
> > > > InstallShield Software Corp.
> > > > www.installshield.com/training
> >
> >
> >
> >
> >
>
>

NewsArchive
05-16-2001, 12:00 AM
Robert-

Thank you for continuing to assist me with my Patch Hell! I just do not
understand
what I am doing incorrect.

- The new MSI file has been created using the original
- Both MSI files have ALLUSERS=2 in Property Manager
- Both MSI files have REINSTALLMODE = amus
- Changed Package & Product Code in New MSI file
- I added the upgrade code to the Upgrade Power Editor to check for older &
newer versions & defined the Action Properties in
SecureCustomProperties in the Property Manager
- The below log is for files that are being added to the new MSI file.
However, I get the same error if I am attempting
to Patch a newer version of a file

Below is the log generated by the Patch creation wizard.

***** Log starting: 2001-05-16 10:03:33 *****

Input-PCP path = 'E:\Setup\patch.pcp'
Patch-MSP path = 'E:\Setup\patch.msp'
Temp Folder = 'D:\Temp\patch\'
Patch GUID =
'{1DD77327-4A04-11D5-BFF9-0030482141F9}'
ListOfPatchGUIDsToReplace = '<none>'
ListOfTargetProductCodes = '*'
PatchSourceList = 'PatchSourceList'
AllowProductCodeMismatches = '1'
AllowProductVersionMajorMismatches = '1'
OptimizePatchSizeForLargeFiles = '<blank>'
ApiPatchingSymbolFlags = '0x00000000'
MsiFileToUseToCreatePatchTables = '<blank>'
SqlCmdToCreatePatchTable = '<blank>'
SqlCmdToCreatePatchPackageTable = '<blank>'
DontRemoveTempFolderWhenFinished = '0'
IncludeWholeFilesOnly = '0'

Using internal SQL cmd to create 'Patch' table.
Using internal SQL cmd to create 'PatchPackage' table.

Patch API could not create a small patch; using whole upgraded file.
Including entire file: 'E:\Setup\COIS Patch V1.00.0000 to
V1.01.0000\Charter Oak\DiskImages\DISK1\.\Charter Oak Test\Main.exe';
FTK=F2527_Main.exe; temp location=Family00\00026.FLE.
Patch API could not create a small patch; using whole upgraded file.
Including entire file: 'E:\Setup\COIS Patch V1.00.0000 to
V1.01.0000\Charter Oak\DiskImages\DISK1\.\Charter Oak Test\Loader.exe';
FTK=F2558_Loader.exe; temp location=Family00\00027.FLE.
Patch API could not create a small patch; using whole upgraded file.
Including entire file: 'E:\Setup\COIS Patch V1.00.0000 to
V1.01.0000\Charter Oak\DiskImages\DISK1\.\Charter Oak Test\Loader.dll';
FTK=F2559_Loader.dll; temp location=Family00\00028.FLE.




"Robert M. Dickau (InstallShield)"
<i_wish_i_had_time_to_answer_individual_questions_through_e-mail_but_i_don't
@installshield.com> wrote in message news:3b01e7db@12.41.20.38...
> What does the rest of the patch-creation log say?
>
> "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> news:3b000833$1@12.41.20.38...
> > Robert-
> > The files keys do match up in Orca. I get the same message even if I am
> > adding new files with the patch.
> >
> > Patch API could not create a small patch; using whole upgraded file.
> > Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
> > Oak\COIS\DiskImages\DISK1\.\Charter Oak\Main.exe';
> > FTK=F3328_Main.exe; temp location=Family00\00026.FLE.
> > Patch API could not create a small patch; using whole upgraded file.
> > Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
> > Oak\COIS\DiskImages\DISK1\.\Charter Oak\Loader.exe';
> > FTK=F3363_Loader.exe; temp location=Family00\00027.FLE.
> > Patch API could not create a small patch; using whole upgraded file.
> > Including entire file: 'E:\Setup32\Windows Installer\Media\Charter
> > Oak\COIS\DiskImages\DISK1\.\Charter Oak\LoaderDll.dll';
> > FTK=F3362_LoaderDll.dll; temp location=Family00\00028.FLE.
> >
> > Any other suggestions?
> > Wendy
> >
> >
> >
> > "Robert M. Dickau (InstallShield)"
> > <i> wrote in message news:3afb2d96@12.41.20.38...
> > > No, I'm afraid I don't know what it could be, if you browsed for the
> > earlier
> > > MSI database; were both versions created from the same project? If you
> > open
> > > both databases with Orca, do the file keys in the File table match up?
> > >
> > > "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> > > news:3afaea54$1@12.41.20.38...
> > > > I added the msi file in the Release under "Previous Package,"
compiled
> &
> > > ran
> > > > the patch creation wizard again and I still have the same error
> message.
> > > > Any other ideas of what I am doing incorrect?
> > > >
> > > >
> > > > "Robert M. Dickau (InstallShield)"
> > > > <i> wrote in message news:3af9b723@12.41.20.38...
> > > > > The patch builder does this (includes entire files) if the file
keys
> > > > > (primary keys in the File table) don't match up between the old
and
> > new
> > > > > packages. To get the file keys to match up (and therefore create
> true
> > > file
> > > > > patches), you can browse for the earlier, pre-patch MSI database
in
> > the
> > > > > Media Type & Patch Optimization panel of the Release wizard.
> > > > >
> > > > > "Wendy Weber" <wweber@charteroaksystems.com> wrote in message
> > > > > news:3af9a3ba$1@12.41.20.38...
> > > > > > Has anyone ever received the following error message in the log
> file
> > > > once
> > > > > > the Patch creation wizard has completed.
> > > > > > (Using InstallShield Professional Windows Installer version
2.01)
> > > > > >
> > > > > > " Patch API could not create a small patch; using whole upgraded
> > > file."
> > > > > >
> > > > > > Any idea what this means? What am I missing?
> > > > > >
> > > > > > Thanks,
> > > > > > Wendy
> > > > >
> > > > > --
> > > > > Robert M. Dickau
> > > > > Senior Technical Trainer
> > > > > InstallShield Software Corp.
> > > > > www.installshield.com/training
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>
>
>

george
12-13-2001, 03:10 AM
My first attempt at patching after upgrading to Dev 7.1 with a standard project produces the following abnormality. The patch creation seems to go through well, but when I then run the Update.exe it produces the error message “Error reading setup initialization file” in a dialog that does not have a caption nor does the “OK” button have any text on it (I presume that it is the OK button).

Could you tell me what this means? I’m attempting patching to perform upgrades due to the problem with minor upgrades.

Marwan
12-13-2001, 01:12 PM
George,
Is there any errors in the log from creating the patch?
What languages are included in the upgraded package?
Is setup.ini available in the upgraded image directory?

george
01-09-2002, 10:24 AM
Update…
Upgraded to 7.02 but the problem remains. I include only English in my project, the creation log looks good (no errors) and the setup.ini is available in the folder. Further more requesting a log does not produce the log for debugging. It appears to be project related since I managed to create a patch for a test project.

george
01-16-2002, 11:18 AM
Marwan can I draw your attention back to this problem please.

patkwang
01-16-2002, 11:30 AM
Maybe you could try changing your package code under general info/summary info stream.

I had the same problem as you a couple of days ago.

Another area you might want to check is the your previous version is your old versions only, does not contain the newest version.

if you set the condition for product code and upgrade code to be the same, do make sure that both versions are the same.

David Thornley
01-16-2002, 12:42 PM
George,

Can you also post the log that is created when you generated your patch. Out bootstrap exe requires an INI file that contains some information about your setup. This INI file is streamed into update.exe. The error you are getting indicates that there is a problem reading this file.

Additionally, can you run the patch with the -Verboce "C:\Me.log" command line and post the log file that this generates as well.

patkwang
07-31-2002, 11:12 PM
Apologise for misinterpreting the error wrongly.

I have been creating patches with no problem, till now! Creates a number of files and the update.exe gives an error dialog!


Is there any resolution to this?

Thank you!

patkwang
07-31-2002, 11:40 PM
This is the setup.ini created

DavidI
09-13-2002, 09:50 AM
Has anyone found a solution to this problem, I am still experiencing the exact problem described.

I am using ID 7.02 to create a small update patch, i.e. only PackageCode has changed. I select Update.exe, the patch wizard completes the .msp is created as is the update.exe and setup.ini but when I run the Update.exe I get "Error reading setup initialization file"

Any guesses appreciated,
Dave.

(The attachment is .txt as it wouldnt let me attach .ini's!)

patkwang
09-13-2002, 10:30 AM
Hi David,

I am awaiting installshield's reply on this issue. I have sent them my project files for them to work on it. I believe the guys at installshield will not disappoint us. For a work around, I did not release any patch to our customers, we just give them a clean install again.

TechGuy
09-17-2002, 10:29 AM
Hi Patric,


After viewing all the posts I am confused that how are u getting multiple files for the patch. I am creating patches since long time and only created a single file.

Have you created some other patches which gives multiple files? If not then create a sample like this and send me the isms as well as pcp.

I am quite interested in this issue and will try my best to solve it.

patkwang
09-17-2002, 11:38 AM
Hi Tech guy,

I am pleased to see that you are interested in this issue. I have submitted my 2 projects to installshield. With these projects, you can produced multiple files instead of one single file. it is about 20MB in sized and contains some confidential files with regards to our software.

Would like very much to share this with you, I will see if I can reproduced it in a simple installation project.

Will keep you guys posted once I get a reply from installshield.

Once again, appreciate very much.

Patrick

TechGuy
09-19-2002, 09:48 AM
Thanks!

I will wait.

DavidI
09-25-2002, 04:44 AM
Any ideas yet guys. I have a patch deadline approaching and am in desperate need of help. Shipping a complete installation is not feasible, as our product is extremely configurable. Reinstalling and losing customers settings for a one file change would be excessive to say the least.

I can generate a test build with one file, build the project uncompressed without a setup launcher (setup.exe). This acts as my original.

I copy the original project and increment the file version, changre the package code (small update) and again rebuild uncompressed without the setup launcher.

The patch generated from my two test project does indeed generate one Update.exe, the .pcp file and the .log as expected without any errors. This is available to anyone that wants it.

Now when I apply the same steps on my 16 meg msi working project I get the setup initialization error. I can run the .msi file directly but obviously the cmd line argument is not present for it to know which features components to install and this is the whole point of me using the patch wizard.

Can somebody from InstallShield please assist.

One complication is that my project was authored with ISWI2.03 but I am having to use the patch wizard of ID7.0... Having spoken to InstallShield technical staff ISWI2.03 patch wizard had a size limit and crashed with my project of 170 features. Having said this patkwang and George are also having this problem and I doubt they have this complication.

I have tried 7.03 and 7.04.

Thank you.

darrenl
10-17-2002, 06:02 AM
Hi,

Has there been any progress on this issue, I too have the error?.

Darren

TechGuy
10-17-2002, 11:15 AM
Patch can not be used for major upgrade. So do not change the the product code. It should be same in both the releases.

SuXskiz
07-28-2004, 10:02 AM
Hi Guys!
I'm having the same problem now!!!
Have you any suggestions?

I'm using IS7.04 and I've compiled a non compressed release of my product (Base Version) with packagecode A and version 02.01.0000.
So I've generated a new packagecode B, I've updated to 02.01.0001 the version, I've updated some components and I've compiled this release (Newer Version).
Next step is been to generate patch between the two releases mentioned above (Base Version and Newer Version).
The result is that the patch generator tool has created more files instead of the only update.exe :confused:
When I try to run Update.exe I get the "Error Reading Setup Initialization File" error.

Have you any idea about?
Thanks
William