After a new install or upgrade of SMSDOM 8.x.x you see nntask process stuck at 50% CPU usage.

Products

• Mail Security for Domino

Issue/Introduction

Task Manager shows nntask stuck at 50% CPU usage when trying to load. See screen shot below.

 

If you have enabled SMSDOM debug parameters you will see the following line as the last line in the log of either smstask0.log or smstask1.log (if exist).  Whichever has the newest modifications.
SMSDOM DEBUG [ CF 01-0D28-16:40:37 04/03/12 ] Unknown Exception caught while loading the Verity DLL.

 

 

Cause

Verity has dependencies on Microsoft files which would normally be installed automatically on the system as part of OS install, updates, etc.  If these system files needed by kvfilter.dll are not present, then the nntask process will not pass the point of trying to load that dynamic link library over and over in a loop. This is why you see the process stuck at 50% CPU usage.  See Solution for fix.

 

Resolution

• Install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
• Enable SMSDOM debug parameters

Download Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) from the Microsoft website:
http://www.microsoft.com/en-us/download/details.aspx?id=5638

If installing the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) does not fix the issue then please apply newer version of the package:
http://www.microsoft.com/en-us/download/details.aspx?id=26347

If the issue is still not fixed, please follow steps for enabling the SMSDOM debug parameters.

 

Enable SMSDOM debug Parameters:

Stop the Domino server
Browse to where the notes.ini is located.
Make a backup of the notes.ini
Open the notes.ini in notepad to edit the file.
Add these lines to the notes.ini

SAVTrace=10
SAVTraceDest=2
SAVTraceDestSize=50
SAVTraceDetach=1
SAVTraceHook=10
SAVTraceHookDestSize=50

 
Save the notes.ini
Start the Domino server
Note: The debug logs for SMSDOM will be located in the (<Drive>:\\<Domino Data Path>\sav\savlog). See the Error section of document for what to look for in the smstask0.log.
 

Applies To

Windows 2k3 32 bit