Unable to create the logs while maintenance from maintainance

[sonu]

Hi Team,

Unable to create the logs while maintenance in method 1, we followed two different ways to move into the maintainance phase.

method -1 : From add or remove programs---cliking on change button.

we are not able to view thw log in this method.

method -2: double click on the setup.exe and it pop up a wizard it goes to maintainance if product us already installed

we are able to view the log by using this method.

Thanks,
Pradeep.

[Eusebiu]

Hi Pradeep,

Did you check the Enable Verbose Logging option from the "Install Parameters" page? In this case the log file will be automatically generated in the TEMP folder.

Best regards,
Eusebiu

[sonu]

Hi Eusebiu,

I've already enabled the "Verbose logging" option in Install Parameters page. It created the log file with <Product name> in TEMP folder during installation. But, From Add/Remove programs it was not created instead of this, "AI_ResourceCleanerLog" file was created.

During maintenance I configured some custom actions. If any errors are occurred during maintenance it would be helpful to figure out the problem from log file.
Could you please help me how to get log file from Add/Remove Programs during Maintenance.

Thanks,
Pradeep

[Eusebiu]

Hi Pradeep,

I tested the scenario and the log file was created as expected even when the product was run in maintenance mode from "Add/Remove Programs" window.

Please note that the log file that is created in TEMP folder has a random name like this: MSI*.LOG (i.e. MSIb867d.LOG). It does not have the Product Name of your application.

Best regards,
Eusebiu

[sonu]

Hi Eusebiu,

We followed the recommended steps to generate log file, no luck to generate the log in the maintainenance from add or remove programs. verbose log option is enabled in install parameters. do we have any other way to find this ?


Thanks,
Pradeep

[Eusebiu]

Hi Pradeep,

I tested the scenario on three machines and it worked as expected. Can you reproduce the problem on multiple clean machines? If so, can you send us to support at advancedinstaller dot com, a simple MSI package that reproduces the behavior, so we can investigate it?

Best regards,
Eusebiu