Of the multiple MSIExec log entries within the setup.exe log, the following is of most interest and demonstrates the success result: A review of the setup log confirmed that setup.exe was launching multiple MSIExec and these were returning a success result back to setup.exe. The Microsoft Office Setup saves logs to %temp% when using Add/Remove Programs to change installed components. As a result, chances are the logs would not show an error but a change in behaviour. This suggested that whatever Application Manager was doing, was allowing the Office Installer or child process to return a success code. The interesting aspect of the symptoms was MS Office was reporting back that the configuration had completed successfully but there were no obvious changes to the MS Office install. A few other applications tested appeared to be unaffected. A Bit of Back StoryĪ customer had found that when the Add/Remove Programs Component was elevated using Application Manager, they were not able to Add/Remove components from Microsoft Office 2010 ( - Login Required). If you’re already familiar with Regular Expressions then this blog probably doesn’t contain anything of addition use but if you’re an AppSense Administrator and haven’t tried comparing working and non-working logs using RegEx, this might provide a pointer for further investigation. It tends to be more difficult to use if multiple actions are running in parallel and it’s not possible to isolate individual actions or threads within a log file.
I tend to find this a useful technique when reading through large log files from other vendors, where actions mostly run sequentially. I had an incident recently where using the log parsing technique of removing unique fields such as date/time from a MSIExec log and then using a compare application helped find the issue. *This post originally appeared on the AppSense blog prior to the rebrand in January 2017, when AppSense, LANDESK, Shavlik, Wavelink, and HEAT Software merged under the new name Ivanti.
0 kommentar(er)
