SpamSentinel is holding all mail after a Domino Upgrade

Problem

On a Standard Installation of SpamSentinel mail stops being delivered and all messages are held in the current scan.box database immediately after an in-place upgrade of Domino is performed.

Most Common Causes and Solutions

1.  The upgrade was from Domino version 12 or older to Domino version 14 or newer.

Starting with Domino 14 the installers from HCL make changes to how Domino is installed and where files are located which can cause SpamSentinel to stop working.  

These problems are easy to fix.   Read the details in our Knowledge Base Entry

2.  Domino is not running as a Windows Service

Sometimes after a Domino upgrade the administrator has problems running Domino as a service or they decide to simply launch Domino as a regular application in order to quickly access the console interface.

SpamSentinel Services are installed to run using the Windows account LocalSystem.  In order to access and share resources with the running Domino server, applications which used the Domino C-API like SpamSentinel must be running under Windows with the same user account as Domino.  This was not true for older versions of Domino running and some which are running on legacy operating systems.  Therefore this requirement may be a surprise for administrators who are upgrading and old environment.

There are two fixes:

A.  Shut down Domino and then launch it again as a Windows Service.

B.  Change the log-ins used within the launch properties of the following SpamSentinel Windows services to match the credentials under which Domino has been launched. Ensure both services are re-started after this change is made.

• SpamSentinel Scanner 1
• SpamSentinel Reporter 1

If you choose to change the credentials, please send an email to technical support letting us know this configuration is in use so that we can flag the servers so that certain automatic updates won't be applied without notice.