Writing to [AI_INSTALL] output.log|error.log

[digitalrinaldo]

I have an advanced installer install package for Windows, 32 bit mode. When I install this package on Windows 7, the install works properly however there is an issue with the stdout and the stderr from a launched application. I set the output directory to the default which is the install directory -- same directory that the executable is located. When the executable launches, there is an access denied error. That is the executable cannot write to the directory to create the output files. Is this the expected behavior. I do not have this issue on Windows 8. Is it bad practice to use that directory for the log files. I have changed it to use the temp directory and it works properly there. If it is an issue it would be helpful to change the defaults to a directory that is writable.

A second question.

Suppose I would to process the install results on the server is there an easy way to get the contents of the installer log and the error.log and output.log and post them to the server. There are three files. The name of the installer log file for Advanced Installer changes each time.

[Daniel]

Hello,

I have an advanced installer install package for Windows, 32 bit mode. When I install this package on Windows 7, the install works properly however there is an issue with the stdout and the stderr from a launched application. I set the output directory to the default which is the install directory -- same directory that the executable is located. When the executable launches, there is an access denied error. That is the executable cannot write to the directory to create the output files. Is this the expected behavior. I do not have this issue on Windows 8. Is it bad practice to use that directory for the log files. I have changed it to use the temp directory and it works properly there. If it is an issue it would be helpful to change the defaults to a directory that is writable.

Please keep in mind that starting with Windows Vista and above operating systems you should run elevated your application in order to be able to write in per-machine location (Program Files folder, Windows Volume folder, etc.). A recommended aproach, as you already observed, would be to write the related log files in per-user locations (Temporary folder, Application Data folder, etc.).

Suppose I would to process the install results on the server is there an easy way to get the contents of the installer log and the error.log and output.log and post them to the server. There are three files. The name of the installer log file for Advanced Installer changes each time.

I'm afraid we don't have predefined support for this. In order to achieve this you can try to create your own custom action which will search for the above log files and will copy them on your server location. The custom action should be added after "Install Execution Stage -> Finish Execution" action group and should have the "Wait for custom action to finish before proceeding" and "Wait for return code at the end of the sequence" execution options disabled.

Also, in order to generate an unchanging installer log file name you can run your MSI using a command line like this:

Code: Select all

msiexec /i setup.msi /L*V "PATH_TO_LOG\installer.log"

or if you are building an EXE installation package, then you can set in "MSI Command Line" field, from "Media -> Configuration" tab, the following command:

Code: Select all

/L*V "PATH_TO_LOG\installer.log"

If you have any questions let us know.

All the best,
Daniel

[digitalrinaldo]

Thank you ignore my BTW comment. I truly appreciate the time you have taken to answer these questions in great detail. Many thanks.

[Daniel]

You're welcome.

All the best,
Daniel