The following is a list of known issues for PureMessage for Microsoft Exchange, version 3.0.2. For additional information, refer to the product Release Notes.
Ensure that the Microsoft SQL Server computer is in the same domain as the current machine. Ensure that the instance name is correct. If you are using a Microsoft SQL Server 2005 database located on a different computer (a remote database), use the Microsoft SQL Server Configuration Manager to enable the TCP/IP protocol for the database instance and start the SQL Server Browser service.
Possible reasons are:
Contact Sophos technical support for more help to identify the problem, or to use SQL Server authentication instead of Windows authentication.
Tags added to email subject lines (if you set up Email tagging) may be displayed as question marks. This occurs when all the following conditions apply:
For messages sent from Outlook Web Access with Exchange 2003, the issue can be resolved by modifying the registry value UseRegionalCharset in key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA to zero. See http://support.microsoft.com/kb/830827 for details.
If the group or resource names use extended characters, e.g. if Japanese resource names are used in a system with an English locale, installation fails. See knowledgebase article 31777 for advice on solving this problem.
Check for installations of Adobe Acrobat Reader. Puremessage can only run with Adobe Acrobat reader version 7. If any other versions are installed, remove them. If the error still occurs, reinstall Puremessage
Check for installations of Adobe Acrobat Reader. Puremessage can only run with Adobe Acrobat reader version 7.
If any other versions are installed, remove them. If the error still occurs, reinstall Puremessage
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.