cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Saturn5
Level 2

Wrong file dates on file installed after reboot

The Bad Result:

A file gets installed, overwriting the previous copy. It now has the created date from the previous copy. The modified date is, properly, the new file's actual build date. This is a "corrupt" condition.

Because these dates differ, future upgrades will, properly, not overwrite this file, though it needs to be overwritten.

Replication:

During a major upgrade, the install log reports file "is being held in use", and "Must reboot to complete operation". Installation completes; recommends reboot; and I reboot. On reboot, which is silent regarding any installer messages or logs, the Bad Result is seen.

The next upgrade gives the dreaded

 

Won't Overwrite; Won't patch;    Existing file is unversioned but modified

 

We never saw this behavior with "small" upgrades. In fact, the file did not get held, and no reboot occurred.

This major upgrade is a late uninstall upgrade, having RemoveExistingProducts sequenced after InstallFinalize. This is an unversioned file. I made a workaround, but I feel I need to understand what's wrong here.

Here is the log of the file getting held for install after reboot:

 

MSI (s) (CC:2C) [14:08:48:575]: File: C:\Program Files\MDI\iTRUST Enterprise\z9\lib\z9-1.0-SNAPSHOT.jar;    Overwrite;  Won't patch;    Existing file is unversioned and unmodified - hash doesn't match source file
MSI (s) (CC:2C) [14:08:48:575]: Source for file '_C7680EB77342823FE55058B9787F76C5' is compressed
InstallFiles: File: z9-1.0-SNAPSHOT.jar,  Directory: C:\Program Files\MDI\iTRUST Enterprise\z9\lib\,  Size: 20043123
MSI (s) (CC:2C) [14:08:48:579]: Re-applying security from existing file.
Info 1603. The file C:\Program Files\MDI\iTRUST Enterprise\z9\lib\z9-1.0-SNAPSHOT.jar is being held in use.  Close that application and retry.
MSI (s) (CC:2C) [14:08:48:585]: Verifying accessibility of file: z9-1.0-SNAPSHOT.jar
MSI (s) (CC:2C) [14:08:48:585]: Verifying accessibility of file: z9-1.0-SNAPSHOT.jar
MSI (s) (CC:2C) [14:08:48:585]: Using source file security for destination.
MSI (s) (CC:2C) [14:08:48:585]: Note: 1: 2318 2: C:\Config.Msi\38d75.rbf 
MSI (s) (CC:2C) [14:08:48:587]: Note: 1: 2318 2: C:\Config.Msi\38d75.rbf 
MSI (s) (CC:2C) [14:08:48:667]: Note: 1: 2329 2: 32 3: C:\Program Files\MDI\iTRUST Enterprise\z9\lib\z9-1.0-SNAPSHOT.jar 
MSI (s) (CC:2C) [14:08:48:667]: Verifying accessibility of file: z9-1.0-SNAPSHOT.jar
Info 1903. Scheduling reboot operation: Deleting file C:\Program Files\MDI\iTRUST Enterprise\z9\lib\z9-1.0-SNAPSHOT.jar. Must reboot to complete operation.

 

Labels (1)
0 Kudos
(1) Reply
Saturn5
Level 2

I've been asked before if I write to this file during operation. No, it is a static library (Java JAR).

0 Kudos