Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Error 1328


10 replies to this topic

aarthi_m

aarthi_m
  • Full Members
  • 65 posts

Posted 07 June 2007 - 09:42

When i try to apply a patch, i get error 1328 for 2 files saying that they have been upgraded by other means.

These 2 files are non-versioned files. The create modified date of the files are the same , ie.. the file has not been modified. However, on upgrade it gives error 1328.
These files come from 2 different components and one of it is a key file. Also, these files have changed between the 2 versions.

Any idea why this happens and how it can be fixed?


Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 08 June 2007 - 09:42

What system error number do you get in the 1328 error message (or log)?
Is your MsiFileHash table populated properly?

aarthi_m

aarthi_m
  • Full Members
  • 65 posts

Posted 08 June 2007 - 09:51

The system error number is "-1072807676".
How can i check if msi filehash is getting populated properly?

Am attaching the errors seen in the log file,

PatchApply(PatchName=RT.JAR.2DA786B9_56F1_4FBC_B649_5C7711252559,TargetName=C:\Program Files\Myappl\app\jre\lib\rt.jar,PatchSize=7787406,TargetSize=41207200,PerTick=0,,FileAttributes=16384,PatchAttributes=0,CheckCRC=0)
PatchFiles: File: rt.jar, Directory: C:\Program Files\Myappl\app\jre\lib\, Size: 41207200
MSI (s) (F8:30) [01:26:57:921]: Re-applying security from existing file.
MSI (s) (F8:30) [01:26:57:921]: Note: 1: 2318 2: C:\Config.Msi\PF2AF4.tmp
MSI (s) (F8:30) [01:26:58:062]: Note: 1: 2302 2: 0
MSI (s) (F8:30) [01:26:58:203]: Note: 1: 2302 2: 32768
MSI (s) (F8:30) [01:26:58:203]: Note: 1: 2302 2: 98304
MSI (s) (F8:30) [01:26:58:203]: Note: 1: 2302 2: 131072
MSI (s) (F8:30) [01:26:58:203]: Note: 1: 2302 2: 163840
MSI (s) (F8:30) [01:26:58:203]: Note: 1: 2302 2: 196608

<Some more messages like this>

MSI (s) (F8:30) [01:26:58:968]: Note: 1: 2302 2: 41123840
MSI (s) (F8:30) [01:26:58:968]: Note: 1: 2302 2: 41189376
MSI (s) (F8:30) [01:27:03:609]: Note: 1: 1328 2: C:\Program Files\Myappl\app\jre\lib\rt.jar 3: -1072807676
MSI © (FC:64) [01:27:03:625]: Transforming table Binary.

MSI © (FC:64) [01:27:03:625]: Transforming table Binary.

MSI © (FC:64) [01:27:03:640]: Note: 1: 2262 2: Binary 3: -2147287038
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1328.Error applying patch to file C:\Program Files\MyAppl\app\jre\lib\rt.jar. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor. System Error: -1072807676

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 08 June 2007 - 10:01

Unfortunately that error number is unknown to my errlookup tool. Maybe start by doing a binary comparison of the existing file on target machine and the new file in your patch. Also compare the two msi files (old and new) to see if the hashes for this file are identical. You could also try to "include whole file" for this file in the patch, instead of the binary difference.

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 08 June 2007 - 10:05

There a KB article with these error codes. Maybe it can give you some idea:
http://support.micro...om/?kbid=308490

aarthi_m

aarthi_m
  • Full Members
  • 65 posts

Posted 08 June 2007 - 10:12

Thanks Stefan.

I looked at that link previously. According to that,

The default Windows Installer log file generates useful information for troubleshooting this issue. The log file reveals that the update is unable to update the file Outllib.dll. Some of the reasons that the Windows Installer is having this problem may include the following:
• The file is damaged (corrupted).
• The file was updated with a more recent update.
• There are incorrect permissions on the file.
• The file is in use by another program.

In this case, the file is not damanged/updated. It has the same permissions as any other file and not other program is using that file.

So, am confused why this error comes up.

Also, i have another application similar to this which has this file (rt.jar) change. The patch created for that works with the same change.


aarthi_m

aarthi_m
  • Full Members
  • 65 posts

Posted 11 June 2007 - 07:30

I tried creating a patch with IncludeWholeFiles=1 (not a binary patch) and the upgrade succeeds.

The patch created with IncludeWholeFiles=0 fails with error code 1328 on upgrade.

Does it mean that, the differential bits of the file generated from the 2 versions is not correct? Is this the reason why the patch upgrade fails?


akerl

akerl
  • Full Members
  • 104 posts

Posted 11 June 2007 - 12:14

When you create a binary patch, the file patch can apply only, when the file is unmodified. You write that the file was modified by a second application. Thats the problem. The patching engine use a hash to identify if the file is changed by another application or setup. If the file was change, the byte level patch can't apply and the patching process terminates. This was a big problem before MSI 3.0 comes. For MSI 2.0 you must include both file versions (the original and the modified file by app2).
With MSI 3.0 everything wirks better, because this version use a baseline cache. Ok, when you update your second application by a MSI Patch, a copy of the unmodified file is stored at the baseline cache. Now, when you update teh other apllication, MSI checks is the file patch is applicable. If false, MSI looks into the baseline cache and use this file.
This works only, when both updates are using MSI patches. The patching scenario is described http://www.microsoft...&displaylang=en.

Andreas Kerl

Inside Windows Installer 4.5
ISBN 3-86645-431-7


Gareth at Serif

Gareth at Serif
  • Full Members
  • 85 posts

Posted 11 June 2007 - 14:26

This looks very much like an issue I had a while back, here:
http://forum.install...showtopic=16662

The results of the linked nabble forum thread is that we think the MsiMsp.exe has a bug in creating large binary differences.

Regards,
Gareth

aarthi_m

aarthi_m
  • Full Members
  • 65 posts

Posted 13 June 2007 - 09:05

Thanks for those inputs. It really helped.

The difference in file size between the 2 versions is almost 8 MB.

There is another application, which has a similar size difference between the 2 versions of the same file. Patch upgrade works there. This is something i am not able to understand.

Is this bug seen consistently for all files with over 4MB size variation? Also, can someone point me to any Microsoft documentation on this.


aarthi_m

aarthi_m
  • Full Members
  • 65 posts

Posted 18 June 2007 - 08:08

Using latest Microsoft SDK (Vista SDK) helps. The msimsp utility v4.0.0 that comes with this SDK has the fix. Also, the time for generating the patch has reduced.