Hi there,

I was wondering if someone could tell me what the time consuming step of 'Calling SRSetRestorePoint API' is/does/means. It's included in this snippet, but can provide the full log if needed for more information.

I know it creates a system restore point, but I'm just wondering why its taking so long on Win 7 (seems to be the case in our testing). The installs were created with Wise Installation Studio so I'm wondering if it could be the way the order for a system restore point is being called. ??

I guess what it comes down to is... Is this an install thing or a system thing? ...

MSI (s) (28:5C) [09:23:41:125]: Running installation inside multi-package transaction C:\Program Files (x86)\MyComp\MyApp80\MyAppserver.msi
MSI (s) (28:5C) [09:23:41:125]: Grabbed execution mutex.
MSI (s) (28:54) [09:23:41:125]: Resetting cached policy values
MSI (s) (28:54) [09:23:41:125]: Machine policy value 'Debug' is 0
MSI (s) (28:54) [09:23:41:125]: ******* RunEngine:
******* Product: C:\Program Files (x86)\MyComp\MyApp80\MyAppserver.msi
******* Action: INSTALL
******* CommandLine: **********
MSI (s) (28:54) [09:23:41:128]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (28:54) [09:23:41:138]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0
MSI (s) (28:54) [09:23:41:138]: Note: 1: 1715 2: MyComp MyApp 8.2 Server
MSI (s) (28:54) [09:23:41:138]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed MyComp MyApp 8.2 Server".
MSI (s) (28:54) [09:29:25:219]: The call to SRSetRestorePoint API succeeded. Returned status: 0, llSequenceNumber: 237.
MSI (s) (28:54) [09:29:25:222]: File will have security applied from OpCode.
MSI (s) (28:54) [09:30:11:011]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files (x86)\MyComp\MyApp80\MyAppserver.msi' against software restriction policy
MSI (s) (28:54) [09:30:11:011]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (28:54) [09:30:11:011]: SOFTWARE RESTRICTION POLICY: C:\Program Files (x86)\MyComp\MyApp80\MyAppserver.msi is not digitally signed
MSI (s) (28:54) [09:30:11:011]: SOFTWARE RESTRICTION POLICY: C:\Program Files (x86)\MyComp\MyApp80\MyAppserver.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (28:54) [09:30:11:011]: End dialog not enabled
MSI (s) (28:54) [09:30:11:011]: Original package ==> C:\Program Files (x86)\MyComp\MyApp80\MyAppserver.msi
MSI (s) (28:54) [09:30:11:011]: Package we're running from ==> C:\Windows\Installer\4445377a.msi
MSI (s) (28:54) [09:30:11:039]: APPCOMPAT: Compatibility mode property overrides found.
MSI (s) (28:54) [09:30:11:049]: APPCOMPAT: looking for appcompat database entry with ProductCode '{3E9CE032-5FC9-44A9-931A-EEA714DBA008}'.
MSI (s) (28:54) [09:30:11:049]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (28:54) [09:30:11:069]: MSCOREE not loaded loading copy from system32
MSI (s) (28:54) [09:30:11:096]: Machine policy value 'TransformsSecure' is 0
MSI (s) (28:54) [09:30:11:096]: User policy value 'TransformsAtSource' is 0
MSI (s) (28:54) [09:30:11:096]: Machine policy value 'DisablePatch' is 0
MSI (s) (28:54) [09:30:11:096]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (28:54) [09:30:11:096]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (28:54) [09:30:11:096]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (28:54) [09:30:11:106]: APPCOMPAT: looking for appcompat database entry with ProductCode '{3E9CE032-5FC9-44A9-931A-EEA714DBA008}'.
MSI (s) (28:54) [09:30:11:106]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (28:54) [09:30:11:106]: Transforms are not secure.
MSI (s) (28:54) [09:30:11:106]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Program Files (x86)\MyComp\MyApp80\install.log'.
MSI (s) (28:54) [09:30:11:106]: Command Line: INSTALLDIR=C:\Program Files (x86)\MyComp\MyApp80\ APP_VALID=********** MyComp_MyApp_7.0=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\MyComp MyApp 7.0\ SOURCEDIR=C:\Program Files (x86)\MyComp\MyApp80\ TARGETDIR=C:\ GAC=C:\ WWWROOT=C:\ INSTALLDIR2=C:\Program Files (x86)\MyComp\ FTS=C:\Program Files (x86)\MyComp\MyApp80\FTS\ USERNAME=johnm COMPANYNAME=Microsoft APP_SERIAL_NUMBER=00110001 APP_NUMBER_OF_SEATS=3 NEWAUTHCODE=7B81D8FA6E9AE0C7B1563B786399A2043DD7FCA240BDBFE29D23A3F47A91DF65 AESEATS=3 DOTNETV2.0.50727=1 NETTWOSP1=#2 MS.8C0C59A0_7DC8_11D2_B95D_006097C4DE24=C:\Windows\SysWOW64\ MS.3207D1B9_80E5_11D2_B95D_006097C4DE24=C:\Windows\SysWOW64\ MS.3207D1B0_80E5_11D2_B95D_006097C4DE24=C:\Windows\SysWOW64\ CURRENTDIRECTORY=C:\Windows\system32 CLIENTUILEVEL=0 CLIENTPROCESSID=5192 ACTION=INSTALL EXECUTEACTION=INSTALL DOTNETCDF=1 DOTNETV3.0=1 DOTNETV3.5=1 DOTNETV4=1 DOTNETV4.0=1 DOTNETFX=1 SECONDSEQUENCE=1 ROOTDRIVE=C:\ ADDLOCAL=Complete ACTION=INSTAL


Any information is greatly appreciated!

Thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I'm just wondering why its taking so long on Win 7It takes as long as it takes :( How long does a manually-triggered SR take? About the same time, I'd guess.

If you want to know what exactly is going on, [snip] will tell you. Can you guess what the missing word is? :-)
Answered 11/03/2010 by: VBScab
Red Belt

Please log in to comment
0
ProcessMonitor?
Answered 11/03/2010 by: Superfreak3
Black Belt

Please log in to comment
0
You might have strung it out a bit...
Answered 11/03/2010 by: VBScab
Red Belt

Please log in to comment
0
28:54) [09:30:11:011]: Note: 1: 2262 2: DigitalSignature 3: -2147287038

there is your answer.

turn the UAC off I suspect the problem will go away. (just for interests sake)
Answered 11/03/2010 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity