·To catch errors from custom actions, use DebugViewer.exe
·To catch error from windows installer, use the following command: msiexec /i [path Add-in Installer.msi file] /l* [path Add-in InstallerLog.txt file]
·Make sure that your distribution point is shared and the permissions on the share are set to allow access to the distribution package
·Make sure that your Add-in Installer.msi is added into the group policy software installation with full UNC path to the shared folder
·Check, if group policy changes were successfully refreshed for logged users. Run the gpupdate command on the client computer to refresh the policy. Check client machine event logs for similar descriptions: Failed to apply changes to software installation settings. Software installation policy application has been delayed until the next logon because an administrator has enabled logon optimization for group policy. Try to log on again.
·Open group policy security options and check, if Apply Group Policy is checked for the groups or users, that you want to prevent from having this policy applied.
·Make sure that all required prerequisites for Add-in Installer.msi were installed before. Check client machine event logs for similar descriptions:
"Failed to apply changes to software installation settings. Software changes could not be applied. A previous log entry with details should exist. The error was: Fatal error during installation. , or
The Group Policy client-side extension Software Installation failed to run. Please look for any errors reported earlier by that extension., or
The install of application Archive Manager Outlook Add-in from policy Archive Manager Outlook Add-in failed. The error was : Fatal error during installation. usually these events come, if the .NET Framework 2.0 is not installed on the client computer.
·Make sure that the Archive Manager Add-in was deployed and registered under: HKCU\Software\Metalogix\PAM4Exchange Outlook Add-in
·Check the registry value HKLM\Software\Microsoft\Office\Outlook\Add-ins\PAM4ExchangeAdd-in\LoadBehavior, must be set to 3.
·Archive Manager Outlook Add-in can be deployed and registered only in one registry location, if you find ...\Software\Microsoft\Office\Outlook\Add-ins\PAM4ExchangeAdd-in both in HKLM and in HKCU, you have to delete one of them, depending on outlook version (The MS Outlook will not load the Add-in, if both are present).
For Outlook 2013 or higher delete HKLM key
·Visual Studio Tools for Office can write all errors that occur during startup to a log file or display each error in a message box. By default, these options are turned off for application-level projects. You can turn the options on by Add-ing and setting environment variables. To display each error in a message box, set the VSTO_SUPPRESSDISPLAYALERTS variable to 0 (zero). You can suppress the messages by setting the variable to 1 (one). To write the errors to a log file, set the VSTO_LOGALERTS variable to 1 (one). Visual Studio Tools for Office creates the log file in the folder that contains the application manifest. The default name is <Manifestname>.manifest.log. To stop logging errors, set the variable to 0 (zero). For information about setting environment variables in Microsoft Windows XP, see "How To Manage Environment Variables in Windows XP".