Knowledge Base Home

Call Support


Search the Knowledge Base

Skip to end of metadata
Go to start of metadata

Environment

Netmail Archive 6.x

Synopsis

Troubleshooting issues with the Outlook Add-in usually requires that tracing be enabled.  This is can be done centrally on the Exchange server(s) for the whole organization, or locally on the workstation for only that installation.  Generally, the latter is preferred. This method is described below.

Solution

The Add-in stores some of its configuration in the registry and reads other configuration from an XML file located at a pre-configured URL.

To enable tracing on the local machine, you must first invalidate the URL (\\HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\MPLUSArchive\URL).  This will force the Add-in to fall back on its local install directory (%APPDATA%\Roaming\Messaging Architects\NetmailArchiveOutookAddin) in order to find a config.xml file.  Normally, this is already present but if not, get it from the URL specified before.  Edit the local version of the file to use the correct IPs & ports, and change the trace level to DEBUG.

Next time you start Outlook, the Add-in should load and use the settings from the local config.xml, including the new trace level.  The Add-in produces a log file named MplusArchive.txt in the \Trace sub-folder of the %TEMP% directory on the workstation.  If Outlook is opened and this file is not produced, then it's very likely that the Add-in never loaded (check prerequisites here: Outlook Add-in Prerequisites).

Notes


Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?

  • No labels