PDA

View Full Version : Logginf



NewsArchive
08-25-2000, 12:00 AM
I'm aware on how to do this, however I was wondering how to build logging
into the install so that when the user clicks setup.exe and runs it
graphically that logging occurs.
-shawn

Arleen-InstallShield <supportnews@installshield.com> wrote in message
news:39a6d604$1@12.41.20.38...
> Hello Shawn,
>
> To log your installation, you need to type the following at the command
> prompt:
>
> msiexec /i C:\YourProject.msi /L*v c:\Yourlog.log
>
> Please take a look at KB article Q104807 for more information on how to do
> this.
>
> Arleen
>
>
> Shawn Nelson <ShawnN@abctech.com> wrote in message
> news:39a6c25a@12.41.20.38...
> > I need a general purpose logging for my install. Most importantly I
need
> to
> > know what files were installed and where, registry settings and type of
> > install carried through. What is the best way to do this? I searched
the
> > MSI help and found some API calls, so do I have to create a whole VB
> project
> > just to tell it to log? Any help would be really appreciated.
> > -shawn
> >
> >
>
>

NewsArchive
08-26-2000, 12:00 AM
If you're including Setup.exe, you can add "/L*v Your.log" to the CmdLine
line in Setup.ini.

"Shawn Nelson" <ShawnN@abctech.com> wrote in message
news:39a6e646@12.41.20.38...
> I'm aware on how to do this, however I was wondering how to build logging
> into the install so that when the user clicks setup.exe and runs it
> graphically that logging occurs.
> -shawn
[...]

--
Robert M. Dickau
Senior Technical Trainer
InstallShield Software Corp.
www.installshield.com/training

NewsArchive
08-02-2001, 12:00 AM
I'm using this code in a CA that runs Install script code {65600}
"Robert M. Dickau (InstallShield)" <vb@installshield.com> wrote in message
news:3b673673@news.installshield.com...
> What type of custom action do you want to create? The code you received is
C
> code, but with some translation it can be called from InstallScript, if
> that's what you're using...
>
> "Donald Bristol" <donaldb@popkin.com> wrote in message
> news:3b66d41e@news.installshield.com...
> > I'm trying to use the following functions, [MsiCreateRecord,
> > MsiRecordSetString and MsiProcessMessage] . When I turn on the option to
> for
> > logging the text was not added to the log file.
> >
> > Someone suggested the following snippet, however I'm unable to compile
the
> > code.
> >
> > MSIHANDLE hInfo;
> >
> > hinfo= MsiCreateRecord (1);
> >
> > MsiRecordSetString (hinfo,0,"You entered an invalid code");
> >
> > MsiProcessMessage(hInstall, INSTALLMESSAGE_INFO,hinfo);
> >
> > MsiCloseHandle (hinfo);
> >
> >
> >
> > Any help will be greatly appreciated
>
> --
> Robert M. Dickau
> Senior Technical Trainer
> InstallShield Software Corp.
> www.installshield.com/training
>
>

Bulldog
10-31-2001, 07:33 PM
In ISX3.03, how do I log an install? i.e. how do I check what files have been replaced/added/overwritten etc, when an application is installed?

Ian

Maurits Vlasman
11-01-2001, 04:23 AM
Hi Ian,

you should pass parameters to the MSI or the SETUP.EXE when installing.
You can find the correct parameters within the ISX Helpfile, sections MsiExec.exe Command-Line Parameters and Setup.exe Command-Line Parameters.
I am quite sure you cannot set those parameters programmaticaly, other then using PackageForTheWeb for distribution of your install.

Maurits

Chandima
11-02-2001, 09:30 AM
Just in case any one is curious or hasn't found it in the help files yet, it is:

Setup.exe /v"/lv C:\InstallLog.txt"

NOTE: You can run this during an uninstall too (incase your Custom Actions are not launching during uninstall or some other need)

NewsArchive
12-19-2001, 01:00 AM
Thanks for the information.

I am using setup.exe and I created a setup.ini with the line you provided,
but setup.exe doesn't even seem to be reading the ini. Since I have tried
putting invalid cmdline options in the ini, but I don't get any errors. Is
there something I need to do to get setup.exe to read an ini? BTW I am
using a Basic MSI project.

Thanks,
Eric Amodio

"Robert Dickau (InstallShield)" <vb@installshield.com> wrote in message
news:3c1ff524@news.installshield.com...
> My understanding is that you can't enable logging within a running
> installation; instead, only an installation wrapper can initiate logging
for
> a product. According to the MSI Help Library, EnableLog "enables logging
of
> the selected message type ***for all subsequent install sessions*** in the
> current process space."
>
> If you're using Setup.exe, perhaps you could add "/L*v TVCLi.log" in the
> CmdLine= entry in Setup.ini.
>
> "Eric Amodio" <eamodio@artisoft.com> wrote in message
> news:3c1fe33c$1@news.installshield.com...
> > Does EnableLog even work? I have a Basic MSI project and I have a
> VBScript
> > custom action that calls Session.Installer.EnableLog("iwefarucmvp+",
> > sTraceFile) where sTraceFile is the temp folder plus TVCli.log. Even
> though
> > I see nothing wrong with this according to the docs, I don't get any
> > TVCli.log. Any ideas?
>
> --
> Robert Dickau
> InstallShield Software Corp.
>
>