MSI and Non-Versioned filed
Nick Woloszyn
versioned files once the client/end-user has modified it.
Hence changing it from it's original state. In my case, it
is usually an ini file. Once in a while it will include
another non-versioned file it wants to over-write, but
mainly one particular modified .ini file. Any help would
be appriciated. Here is the message...
FileCopy
(SourceName=CITA.INI,SourceCabKey=F222673_CITA.INI,DestName
=CITA.INI,Attributes=8192,FileSize=152,PerTick=32768,,Verif
yMedia=1,,,,SecurityDescriptor=BinaryData,CheckCRC=0,,,Inst
allMode=58982400,HashOptions=0,HashPart
1=-
22369308,HashPart2=691084311,HashPart3=2003087898,HashPart4
=5928725,)
MSI (s) (90:A4): File: C:\Program
Files\CH2CW\Data\RTData\CITA.INI; Overwrite; No patch;
Existing file is unversioned and unmodified - hash doesn't
match source file
Adam Semel
I am not sure you clearly stated your problem. The unversioned file will
not be getting overwritten by design. We consider this file be a changed
file, thus possibly containg data. Since it has changed and it is
unversioned we don't patch it. If you want to overwrite the file anyway,
there are several things you can do. Try passing the "a" switch to the
REINSTALLMODE property, and that will override the no patch behavior.
Adam Semel
Windows Installer Team
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Kallely Sajan
In my case it was an xls file.
--
Regards,
Sajan.
PS: Please don't send me emails, use the news room, so that others also will
be benefited.
"Adam Semel" <ase...@online.microsoft.com> wrote in message
news:Tkl6QY#ODHA...@cpmsftngxa06.phx.gbl...
Nick Wilson
Thanks for the response. I understand the was WI is designed not
to overwrite user files, but what I'm saying is that...it's overwriting
user files. Let me step through the sequence of events:
1 - A patch is generated to update client machines.(As ususal)
2 - The patch is distributed.
3 - Client runs patch
4 - Patch sees that an .ini file has been changed (ie. is newer than the
original)
5 - Patch knows it is a non-versioned file.
6 - Patch tries to "fix" the changed .ini file.
7 - Patch cannot find the source of the original installation.
8 - Patch rolls back all actions.
9 - Updates to client workstations NOT successful.
There are ways to work around the problem. But I need to know WHY this
is happening. More thought on the matter is appriciated.
Nick
In article <Tkl6QY#ODHA...@cpmsftngxa06.phx.gbl>,
ase...@online.microsoft.com says...
Nick Woloszyn
Thanks for the response. I understand the design of WI not to
overwrite an unversioned file, but what I may not have stated clearly is
that... it's happening. The sequence is as follows:
1 - Install .ini file (amongst other files) via .msi package
2 - User modifies file
3 - Patch is installed to update dll's (or other changed versioned
files)
4 - Patch notices .ini file has changed
5 - Patch wants to "fix" .ini file
6 - Patch looks for origninal .msi
7 - Patch cannot find original .msi
8 - Patch fails, rollback initiated
9 - .dll's not updated
The step method of explanation is not meant to sound/look condescending,
it is merely an attempt to show, in simplest form, the problem at hand.
Once the .ini file is modified, the goal is NOT to overwrite the file.
Any ideas?
Nick
In article <Tkl6QY#ODHA...@cpmsftngxa06.phx.gbl>,
ase...@online.microsoft.com says...
Adam Semel
first installation? It sounds like the installer is trying to path the .ini
file. Can you past the part of the verbose log file into a post so I can
see why the file is getting patched?
Nick Woloszyn
Are you looking for something other than what was in the original post
for this thread? Because the rest of the log file has the usual stuff in
it except for this .ini file. Let me know.
Nick
In article <5TLUMk0P...@cpmsftngxa09.phx.gbl>,
ase...@online.microsoft.com says...
Adam Semel
are not going to patch the file.
Kallely Sajan
says that hash does not match, and file is not modified. But the file is
actually modified.
----------------------------------------------------------------------------
-------------------------
MSI (s) (A4:60): File:
C:\MyCompanyMyProductServer\MyCompanyMyProduct12.1\WorkspaceLibraries\Datash
eets\summary.xls; Won't Overwrite; No patch; Existing file is unversioned
and unmodified - hash matches source file
MSI (s) (A4:60): Executing op: FileCopy(SourceName=VESSEL~1.XLS|Vessel
Equipment List.xls,SourceCabKey=Vessel_Equipment_List.xls,DestName=Vessel
Equipment
List.xls,Attributes=16384,FileSize=222720,PerTick=32768,,VerifyMedia=1,,,,,C
heckCRC=0,,,InstallMode=
58982400,HashOptions=0,HashPart1=1140649134,HashPart2=701967939,HashPart3=16
19673053,HashPart4=-174908666,)
MSI (s) (A4:60): File:
C:\MyCompanyMyProductServer\MyCompanyMyProduct12.1\WorkspaceLibraries\Datash
eets\Vessel Equipment List.xls; Won't Overwrite; No patch; Existing file
is unversioned and unmodified - hash matches source file
MSI (s) (A4:60): Executing op: FileCopy(SourceName=VESSEL~2.XLS|Vessel
Process
Specification.xls,SourceCabKey=Vessel_Process_Specification1,DestName=Vessel
Process
Specification.xls,Attributes=16384,FileSize=211456,PerTick=32768,,VerifyMedi
a=1,,,,,CheckCR
C=0,,,InstallMode=58982400,HashOptions=0,HashPart1=-73634442,HashPart2=14238
49288,HashPart3=-1905861745,HashPart4=-2144917002,)
MSI (s) (A4:60): File:
C:\MyCompanyMyProductServer\MyCompanyMyProduct12.1\WorkspaceLibraries\Datash
eets\Vessel Process Specification.xls; Overwrite; No patch; Existing file
is unversioned and unmodified - hash doesn't match source file
MSI (s) (A4:60): Resolving source.
MSI (s) (A4:60): User policy value 'SearchOrder' is 'nmu'
MSI (s) (A4:60): User policy value 'DisableMedia' is 0
MSI (s) (A4:60): Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (A4:60): SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (A4:60): SOURCEMGMT: Looking for sourcelist for product
{C6D79961-7E90-4E4A-8E9F-F7055C123E44}
MSI (s) (A4:60): SOURCEMGMT: Adding {C6D79961-7E90-4E4A-8E9F-F7055C123E44};
to potential sourcelist list (pcode;disk;relpath).
MSI (s) (A4:60): SOURCEMGMT: Now checking product
{C6D79961-7E90-4E4A-8E9F-F7055C123E44}
MSI (s) (A4:60): SOURCEMGMT: Media is enabled for product.
MSI (s) (A4:60): SOURCEMGMT: Attempting to use LastUsedSource from source
list.
MSI (s) (A4:60): Note: 1: 2203 2: 3: -2147287037
MSI (s) (A4:60): SOURCEMGMT: Source is invalid due to missing/inaccessible
package.
MSI (s) (A4:60): Note: 1: 1706 2: -2147483647 3: MyCompany MyProduct
12.1.msi
MSI (s) (A4:60): SOURCEMGMT: Processing net source list.
MSI (s) (A4:60): Note: 1: 1402 2: UNKNOWN\Net 3: 2
MSI (s) (A4:60): Note: 1: 1706 2: -2147483647 3: MyCompany MyProduct
12.1.msi
MSI (s) (A4:60): SOURCEMGMT: Processing media source list.
MSI (s) (A4:60): Note: 1: 1706 2: -2147483647 3: MyCompany MyProduct
12.1.msi
MSI (s) (A4:60): SOURCEMGMT: Processing URL source list.
MSI (s) (A4:60): Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (A4:60): Note: 1: 1706 2: -2147483647 3: MyCompany MyProduct
12.1.msi
MSI (s) (A4:60): Note: 1: 1706 2: 3: MyCompany MyProduct 12.1.msi
MSI (s) (A4:60): SOURCEMGMT: Failed to resolve source
Error 1706.No valid source could be found for product MyCompany MyProduct
12.1. The Windows Installer cannot continue.
MSI (s) (A4:60): Product: MyCompany MyProduct 12.1 -- Error 1706.No valid
source could be found for product MyCompany MyProduct 12.1. The Windows
Installer cannot continue.
----------------------------------------------------------------------------
-------------------------
--
Regards,
Sajan.
PS: Please don't send me direct emails, use the newsroom.
"Adam Semel" <ase...@online.microsoft.com> wrote in message
news:JNxbHUOQ...@cpmsftngxa09.phx.gbl...