This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Not understanding repair functionality or?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 18, 2009
04:31 AM
Not understanding repair functionality or?
Problem:
When installation is performed with a system account (SCCM, psexec, etc) files located in any user profile folder (for example - [AppDataFolder]) are not repaired if the user is a member of the administrators group.
I've been struggling with this for some time now and still unable to find a solution.
Has someone encountered the same problem?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 08, 2011
08:54 AM
Just a bit more of a detailed explanation:
Your suggestions will be very much appreciated.
Intro:
I have doubts that this is the right place to ask about this, since this issue has existed for me on many windows platforms, please suggest where this should be forwarded if this is an inappropriate place to ask.
Please do not be confused by the directory paths for XP, this issue is also true for Windows 7.
Description:
Windows Installer does not repair files in per-user directories, such as [AppDataFolder], when initial installation is performed using system account (for example - distributing the package through SCCM or using psexec) and repairing under a user with administrative privileges (limited user repair works fine).
Example.
.msi installation installs a custom .xml configuration file to "[AppDataFolder]". We're installing .msi by using psexec /s. log output:
MSI (s) (D8:F0) [15:19:01:214]: Executing op: FileCopy(SourceName=SETTIN~2.CON|customXML,SourceCabKey=customXML,DestName=customXML,Attributes=16384,FileSize=2633,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=-1992414570,HashPart2=1238809189,HashPart3=-80616146,HashPart4=146746036,,)
MSI (s) (D8:F0) [15:19:01:214]: File: c:\WINDOWS\system32\config\systemprofile\Application Data\customXML;
To be installed; Won't patch;
No existing file
MSI (s) (D8:F0) [15:19:01:214]: Source for file 'customXML' is compressed
MSI (s) (D8:F0) [15:19:01:230]: Note: 1: 2318 2: c:\WINDOWS\system32\config\systemprofile\Application Data\customXML
When a user with administrative credentials accesses the advertised shortcut repair is run on the component that has the .xml configuration file, event viewer has an entry about this.
The verbose repair log file shows the following entry:
MSI (s) (D8:E4) [15:22:27:667]: Executing op: FileCopy(SourceName=SETTIN~2.CON|customXML,SourceCabKey=customXML,DestName=customXML,Attributes=16384,FileSize=2633,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=16908288,HashOptions=0,HashPart1=-1992414570,HashPart2=1238809189,HashPart3=-80616146,HashPart4=146746036,,)
MSI (s) (D8:E4) [15:22:27:667]: File: c:\WINDOWS\system32\config\systemprofile\Application Data\customXML;
Won't Overwrite; Won't patch;
Existing file is unversioned and unmodified - hash matches source file
Limited user repair log reads:
MSI (s) (78:8C) [15:26:27:406]: Executing op: FileCopy(SourceName=SETTIN~2.CON|customXML,SourceCabKey=customXML,DestName=customXML,Attributes=16384,FileSize=2633,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=16908288,HashOptions=0,HashPart1=-1992414570,HashPart2=1238809189,HashPart3=-80616146,HashPart4=146746036,,)
MSI (s) (78:8C) [15:26:27:406]: File: c:\Documents and Settings\test\Application Data\customXML;
To be installed; Won't patch;
No existing file
Your suggestions will be very much appreciated.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 18, 2012
08:33 AM
Quote:
Problem:
When installation is performed with a system account (SCCM, psexec, etc) files located in any user profile folder (for example - [AppDataFolder]) are not repaired if the user is a member of the administrators group.
I've been struggling with this for some time now and still unable to find a solution.
Has someone encountered the same problem?
I have ran into
MSI (s) (78:8C) [15:26:27:406]: File: c:\Documents and Settings\test\Application Data\customXML;
To be installed; Won't patch;
No existing file
Only it comes from the installed Cache location.
Problem:
When installation is performed with a system account (SCCM, psexec, etc) files located in any user profile folder (for example - [AppDataFolder]) are not repaired if the user is a member of the administrators group.
I've been struggling with this for some time now and still unable to find a solution.
Has someone encountered the same problem?
I have ran into
MSI (s) (78:8C) [15:26:27:406]: File: c:\Documents and Settings\test\Application Data\customXML;
To be installed; Won't patch;
No existing file
Only it comes from the installed Cache location.