Views:
The following table explains the most common ScanMail messages that may appear on the Domino server console:
Message
Cause
What To Do
SMDreal: Unable to create message queue. Restart Domino server.
Domino server may not be running properly.
Restart the Domino server.
SMDreal: Unable to initialize common message. Unload and then reload SMDreal.
Message files are missing.
Uninstall, and then re-install ScanMail.
SMDreal: Unable to initialize scan engine. Check the scan engine and pattern file.
The scan engine or pattern file is missing.
smconf.nsf does not contain policy document
Uninstall, and then re-install ScanMail.
Create a policy in smconf.nsf, and then load smdreal again
SMDreal: Missing Extension Manager in notes.ini. Re-install ScanMail.
ScanMail was installed using a wrong installation package. Alternatively, ScanMail was removed manually.
Uninstall, and then re-install ScanMail.
SMDreal: Invalid Activation Code. Activate ScanMail via the Configuration Database and then reload SMDreal.
Activation Code (AC) was not entered during ScanMail installation. Alternatively, an invalid AC was entered.
Enter a valid AC using the ScanMail Configuration Database > Administration > Product License document. See Registering and Activating SMD.
SMDreal: The trial period has expired. Obtain a Registration Key and then activate ScanMail.
An AC trial version was entered during installation, and the AC already expired.
See Renew SMD Maintenance
SMDreal: Unable to load policy. Check Configuration Database and then reload SMDreal.
The Configuration Database might be corrupt.
Reinstall ScanMail.
SMDreal: Unable to load Message Database. Check smmsg.nsf and then reload SMDreal.
smmsg.nsf (ScanMail Message Database) might be corrupt.
SMDdbs: Invalid database list settings. Check the database list in the Manual or Scheduled scan rule setting.
The format of the database list in the Configuration Database is incorrect.
Check Databases to Scan list in the Real-time Database Scan, Scheduled Scan, or Manual Scan documents. Use semicolons to separate multiple entries.
SMDreal: Unable to read Domino directory. Check server status.
The fully qualified name (FQDN) of the Domino server is empty. Alternatively, other Domino configuration is wrong.
Correct the Domino settings.
SMDreal: Cannot open database {database name}. Check the database name in the Configuration Database.
ScanMail cannot open the database when trying to scan the special document in that database. Probably, the database was deleted before ScanMail was able to scan it.
No action needed.
SMDdbs: Cannot read Database Scan settings. Check Configuration Database.
Database Scan setting is incorrect.
Check database scan rule (see Creating Real-time Database Scan Rules).
SMDupd: Unable to run multiple SMDupd instances
Scheduled update, manual update, or update task from the Apex Central / Control Manager server are running at the same time.
Wait until an update is finished, then run another update task.
SMDupd: Invalid parameter
The Update task only accepts 4 kinds of format parameter, which represent update that was triggered from 3 different sources. If the parameter did not follow the required format, this message will be displayed.
Check the manual scan document or scheduled update rule (see Running Manual Scan or Updating Components).
SMDupd: Unable to initialize the update task
Unable to obtain the correct update settings or ActiveUpdate cannot be invoked.
SMDupd: Unable to set up connection. Check network connection. Refer to ScanMail Help > Troubleshooting section for details.
Connection to the ActiveUpdate server cannot be established.
Check the network connection and the proxy server connection and configuration. Refer to <ScanMail Installation Path>\AU_Log\TmuDump.txt for details.
SMDupd: Unable to download components. Check server status or refer to ScanMail Help > Troubleshooting section for details.
Network congestion or unable to perform integrity checking for the downloaded component.
Refer to <ScanMail Installation Path>\AU_Log\TmuDump.txt for details.
SMDupd: Unable to update component(s), the Activation Code already expired.
AC already expired.
See Renew SMD Maintenance
SMDupd: Unable to update to the latest version. Refer to ScanMail Help > Troubleshooting for details.
Connection to the ActiveUpdate server cannot be established or
unable to perform integrity checking for the downloaded component.
Check the network connection and the proxy server connection and configuration.
Refer to <ScanMail Installation Path>\AU_Log\TmuDump.txt for details.
SMD Loader: The executable file exceeds the allowable maximum size {maximum size}
The path name of executable file is too long. This could be caused by multiple cascading subdirectories or long file names.
Reinstall ScanMail on a directory with a short path name.
SMD Loader: Unable to find the latest program directory
Unable to find ScanMailInstallPath in notes.ini. This is caused by incomplete installation or manual deletion of ScanMail files.
Reinstall ScanMail or add ScanMailInstallPath parameter and value in notes.ini.
SMD Loader: Unable to browse the latest program directory {path}
The path name specified by ScanMailInstallPath is an invalid path or directory.
Reinstall ScanMail or add the correct ScanMailInstallPath parameter and value in notes.ini.
SMD Loader: Unable to load dynamic library "%s"
Unable to load the dynamic library because a file is missing, corrupted, or has insufficient permission.
Reinstall ScanMail or obtain a valid file and overwrite the corrupted one on the Domino server.
SMDsch: Unable to start the scheduled task "%s"
Keywords: error messages