MGS
Posts: 128
Joined: Tue Oct 04, 2022 9:52 am

More detailed log output

Hi,

The following error message tells us that the specified file could not be found. But what is the specified file? Is this an error message that is thrown by Advanced Installer itself? If yes, can you please include the path/name of the specified file in the log output? That would definitely be beneficial for the user to fix such an issue.
MSI (s) (EC:70) [12:28:30:364]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI4C6.tmp, Entrypoint: OnExpandArchConfig
MSI (s) (EC!F8) [12:28:47:442]: Product: XRStorage -- The system cannot find the file specified.

CustomAction AI_ExpandArchConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 12:28:47: InstallExecute. Return value 3.
All the best,
Johannes
Catalin
Posts: 7664
Joined: Wed Jun 13, 2018 7:49 am

Re: More detailed log output

Hello,

That is indeed a Custom Action proprietary to us.

The log file is mostly meant for the developers.

When a developer sees that, it's most likely obvious where the issue comes from and what the issue is.

These messages are actually predefined return codes. For instance, "The system cannot find the file specified" is:
Screenshot_173.png
Screenshot_173.png (8.69 KiB) Viewed 30574 times
according to the following article: System Error Codes (0-499)

If you want a more detailed log, you can use the AI_DEBUGLOG=1 property. This should give you exactly what you need in this case:

Screenshot_174.png
Screenshot_174.png (55.82 KiB) Viewed 30574 times

Hope this helps! :)

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MGS
Posts: 128
Joined: Tue Oct 04, 2022 9:52 am

Re: More detailed log output

Hello Catalin,

Thanks for explaining the steps necessary to get a more detailed log using
AI_DEBUGLOG=1 property
, that will definitely come in handy next time! For me it would have been obvious if I just did one step and then rebuilt the project and this issue appeared. But instead, I did many changes to the project (added a whole new build config, many files and custom actions, and then switched the build config and then the issue appeared. So there could have been many places that caused this issue and thus it wasn't easy to track it down. I am glad that there is this feature to set the log-level so I'll be faster tracking down such an issue next time, that will definitely help. :D

Best regards,
Johannes
Catalin
Posts: 7664
Joined: Wed Jun 13, 2018 7:49 am

Re: More detailed log output

You are always welcome, Johannes!

Glad I was able to assist. :)

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Feature Requests”