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.
Log file question
Started by
spdygnlz
, Nov 28 2006 19:40
6 replies to this topic
Posted 28 November 2006 - 19:40
I love the log file feature in the MSI projects and the included viewer is great. My problem is that there are 3 sections that never get any information: Feature States, Component States, and File Actions. These would be really helpful, but I can't figure out how to get that information in the log. I've looked around for information to enable these, but I think part of my problem is I don't know quite what to look for. Can anyone help? Thanks!
-- spdygnlz --
Posted 29 November 2006 - 14:09
Did your install complete successfully? If not it may not have run to the point where it writes feature state to the log.
Stefan Krüger
InstallSite.org twitter facebook
Posted 29 November 2006 - 17:31
Yes, they always finish correctly. It always finishes with a value of "0". Could there be something I'm missing in the command line? This is what I'm using:
/l*v "C:\Installation.log"
/l*v "C:\Installation.log"
-- spdygnlz --
Posted 30 November 2006 - 18:48
That's looking good. If you open the log file with a text eidtor do you see deature states? And which version of MSI runtime are you using, and which version InstallShield?
Stefan Krüger
InstallSite.org twitter facebook
Posted 30 November 2006 - 20:00
Yes, I do see that info in there:
CODE |
MSI (s) (A8:58) [16:16:23:519]: Feature: TestDM; Installed: Absent; Request: Local; Action: Local MSI (s) (A8:58) [16:16:23:519]: Feature: WebDisplay; Installed: Absent; Request: Local; Action: Local MSI (s) (A8:58) [16:16:23:519]: Component: GenericObject.ocx; Installed: Absent; Request: Local; Action: Local MSI (s) (A8:58) [16:16:23:519]: Component: RodPositionMonitor.ocx; Installed: Absent; Request: Local; Action: Local . . . InstallFiles: C:\Program Files\My Company\MyProject\RodPositionMonitor.ocx SIZE: 450560 bytes MSI (s) (A8:58) [16:16:42:995]: Note: 1: 2318 2: C:\Program Files\My Company\MyProject\RodPositionMonitor.ocx MSI (s) (A8:58) [16:16:43:026]: Executing op: FileCopy(SourceName=PROJDS~1.DLL|projDSManager.dll,SourceCabKey=projdsmanager.dll,DestName=projDSManager.dll,Attributes=8192,FileSize=684032,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,Version=6.12.0.0,Language=1033,InstallMode=58982400,,,,,,,) MSI (s) (A8:58) [16:16:43:026]: File: C:\Program Files\My Company\MyProject\projDSManager.dll; To be installed; Won't patch; No existing file MSI (s) (A8:58) [16:16:43:026]: Source for file 'projDSManager.dll' is uncompressed, at 'C:\Documents and Settings\username\Desktop\DISK1\program files\My Company\MyProject\'. |
I'm using the Windows Installer 3.1 and InstallShield Premier 12.
So, I don't know how clearly I stated my problem before... I don't see the information in the MSI Log Analyzer. I suppose I could use the straight text file if I had to, but the thing is about 30MB. Not looking forward to reading that monster in notepad.
Could it be a problem with the extension? The log viewer by default wants a .wil file. Should I be making the .log a .wil instead or is that something different?
Edited by spdygnlz, 30 November 2006 - 20:06.
-- spdygnlz --
Posted 30 November 2006 - 23:14
Looks like the log viewer doesn't understand the MSI 3 log file format, maybe because of the time stamps. It works proeprly with MSI 2 logs.
Stefan Krüger
InstallSite.org twitter facebook
Posted 30 November 2006 - 23:31
Ah. Bummer. Thanks for looking into it. I think I might ask Installshield about their plans to fix it.
-- spdygnlz --