Problems with Logging installs

[Gareth Owen]

Hi all, still having issues with Administrative installs, the main issue now is the lack of logging.

Even passing the log option into the MSI command line,
(both the MSI and IA part of the command line)

I get absolutely no infomation until the main installation actually begins.

In this case, I believe that the installation is failing BEFORE we get to the main install, either due to failing to install prereqs or incorrect command line parameters.

Unfortunately this means the there is no way for us to tell what the issue is.

The MSI wrapper logging just shows a successfull install, and there is no log at all for the IA part of the installation.

Please Help, how can I find out what is failing.

Can I manually write information to the log file?

Cheers

[jimo]

When all else fails there is the messagebox or write to your text file at key points through out your script.

Just a thought.

[Gareth Owen]

Yep, about what i thought, Message Box is not really an option for admin silent installs, but it looks like I will ahve to manually write to file.

Would it be best to try to write to the log file manually ($LOGGED$) , or do I need to use another file?


Cheers

[MichaelNesmith]

I would use another file, say $LOGGED$.custom.txt.

[Gareth Owen]

Also, where do I need to put the write to file, such that I can return information about failing to extract Web Blocks?

I want an entry saying if a particular web block could not be opened.


Cheers for the help

[Gareth Owen]

Well I have managed to get most of the logging functionality in manually, but it is very long winded,

For every MessageBox I have to put a

If $LOGGED$ not Equals
Write into Text File $LOGGED$
end

Is there any chance of making the default behaiviour of a MessageBox to write the message to the log file if doing a silent, logged install. This would make life so much easier.

[Gareth Owen]

Doh, next issue.

When you select the logged install option in IA.

it creates a new log file when it gets to the Applying the install.

That means that any logging information I have put in manually during the information gathering and Prereq stage is then lost.

Oh well, at least I can now tell why the install is failing as it quits before it gets to the apply install normally.

If it gets that far, it has probably worked, so I do not need the logging information.

[MichaelNesmith]

That is why above I said:

I would use another file, say $LOGGED$.custom.txt.

[Gareth Owen]

Must read things more carefully next time.

Cheers