14 replies to this topic

[jagdishprabhu]

After installation is complete, is there a built-in function which would create a log that contains information about files that were installed , replaced, shared locked version nos...etc?

[Taco Bell]

Sorry, but there's nothing built in to automatically do logging, and as far as I know, no such file information is readily available from IS.

I do have logging setup in my IS projects for debugging/troubleshooting purposes, but it's own my own custom code and is mainly a series of debug messages to know what transpired.

[Ozone]

Provided that you have Logging ENABLED, the file you seek is [drive]:\Program Files\InstallShield Installation Information\{Your GUID here}\setup.ilg

It is in a hidden folder.

You can view the contents using the appropriate version of the InstallShield Utility 'Log File Viewer'. (ISLogVu.exe)

[Taco Bell]

Wow, I knew about that file, but not the viewer, so it was basically meaningless up until now. Thanks for the info Ozone.

Edited by Taco Bell, 22 September 2003 - 23:58.

[jagdishprabhu]

Log file is required by customers to whom i'm deploying the setup so can i convert this mentioned file to .txt file and copy it to specified folder. The utility u mentioned requires series of ocx to be registered which is not feasible. Is there any other way for this? Please help.

[Ozone]

I have an Install that writes a custom text log file for our Customer Support Dept.
It logs the file name, date, and time attributes of every file ‘moved’ – installed. I added script to the Move Data – Installing File event.
The function LOG_File_Create(); opens the log file in append mode. You will have to write your own function to open and append to the file.

This script does not do all that you requested, but maybe it is a starting point.

[jagdishprabhu]

Would definately try it out and let u know. thnxs ozone.

[Taco Bell]

I'm curious Ozone. Where does the file parameter come from? You say its called with each component, but how exactly?

[Ozone]

The ‘File’ argument is provided by InstallShield’s default script in obevents.rul and Events.rul. Exactly which .dll file this function is in, is unknown to me. Below is the default code. I assume that IS loops through this function for each file installed, because that is the behavior that I have observed.

The same argument is in the default function OnUninstallingFile(File).

//////////////////////////////////////////////////////////////////////////////
//
// FUNCTION: OnInstallingFile
//
// EVENT: Installing File event is sent before a file that is being installed
//
// ARGUMENTS: File - full path of file being installed
//
///////////////////////////////////////////////////////////////////////////////
function OnInstallingFile(File)
begin
end;

[Taco Bell]

Okay, thanks Ozone.

[jagdishprabhu]

Ozone, ur solution did work for dlls and exe that went into my application directory but for files that go into system32 directory are not captured. Probably becoz of condition
if(File%TARGETDIR).
Can this problem be overcomed? Can i give if(File%TARGETDIR | File%WINSYSDIR). pls suggest.

[Taco Bell]

Seem like that new if condition would be sufficient jagdishprabhu, or just outright remove the conditional statement to ensure that EVERY file is logged.

Edited by Taco Bell, 03 October 2003 - 14:11.

[jagdishprabhu]

But what abt the the datetime for my application dlls and exes going into my appln directory? they are not captured. Any reasons?

[Taco Bell]

Well if the return codes fail, then it won't right the date & time, so maybe you can step through it the debugger and figure out why that is happening. Not sure off the top of my head though since I didn't write the code, but maybe Ozone knows.

Edited by Taco Bell, 08 October 2003 - 14:33.

[Ozone]

To jagdishprabhu,

Your post dated 10-03-2003 stated that it worked fine logging into TARGETDIR but not the WINDIR. Removing the filter [ if ( File % TARGETDIR ) then ] will allow all files to be logged as suggested by Taco Bell. Below is a sample of what your log file should contain.

Installing patch file ====== C:\Alpha\Tkiscale.exe Dated: 2003\10\02 Time: 10:43:44
Installing patch file ======== C:\Alpha\TKPOST.EXE Dated: 2003\04\28 Time: 11:58:26
Installing patch file ======= C:\Alpha\TKPRICE.EXE Dated: 2003\04\24 Time: 10:2:32
Installing patch file ====== C:\Alpha\TKREXCEP.EXE Dated: 2003\04\24 Time: 9:33:12
Installing patch file ====== C:\Alpha\Tkrsale3.exe Dated: 2003\09\29 Time: 19:44:42

Without seeing your code I would just be guessing. Did you check to make sure that the String and Numeric variables defined locally in the function are not the same as some Global String and Numeric variables?