How to troubleshoot the error message: "Symantec Premium AntiSpam registration failed. The product will not receive definition updates", on Symantec Mail Security for Microsoft Exchange.

Article:TECH83981  |  Created: 2005-01-09  |  Updated: 2014-06-25  |  Article URL
Article Type
Technical Solution


After installing a Symantec Premium AntiSpam license to Symantec Mail Security for Exchange (SMSMSE) the following error message is displayed:

Symantec Premium AntiSpam registration failed. The product will not receive definition updates

Do the following:
1. Ensure that a valid, up-to-date Premium AntiSpam license is installed.
2. Verify that DNS can resolve
3. Allow outbound secure https through firewall (port 443).
4. If using proxy server, see documentation for manually running register.
5. Retry registration by enabling Premium AntiSpam within the product.


The following event may also be seen in the Application Log:

Eventid: 353
Source: Symantec Mail Security
Category: Symantec Premium AntiSpam
Description: There was an error on the server <<servername>>. Symantec Premium AntiSpam registration failed. The product will not receive spam definition updates. Do the following: 1. Insure that an up to date premium antispam...


Note to users of legacy versions

In November 2009, the SSL certificate bundle included in several legacy versions of the Premium AntiSpam feature of Symantec Mail Security for Microsoft Exchange (SMSMSE) expired. If SMSMSE 5.0.2 or earlier is in use, read End of Standard Support and Version Upgrade Reminder for more information.

Note to Exchange 2007/2010/2013 users

The above error will occur if attempting to license and/or enable Premium Anti spam if the hub or edge roles are not present.  This is because the Premium Anti Spam requires SMTP Transport.  Symantec Premium Anti Spam can only be implemented on Exchange 2007/2010/2013 Hub or Edge roll servers.

Make sure that the license file is valid.

To check the validity of the license file

  1. Open the Symantec Mail Security for Microsoft Exchange console, click Admin then Licensing.
  2. In the right pane, under License Information, verify that the license is valid.

To fix the problem if the license is valid

  1. Check the Bmiconfig.xml file, and repair it if needed.
    For details, read Event ID 514 error messages in the application log after upgrading Symantec Mail Security for Microsoft Exchange.
  2. Examine the Conduit.log file.
  3. Try to enable Premium AntiSpam again.

Verify Access to Hostnames

  1. Verify that a connection is possible to
  2. If a proxy server is used, configure the proxy server to allow the Exchange server direct access.
    For details, read How to manually register the license for Premium AntiSpam with Symantec Mail Security for Microsoft Exchange (SMSMSE).
  3. Try to enable Premium AntiSpam again.

To verify DNS resolution for

  1. On the Windows taskbar, click Start > Run.
  2. In the Run dialog box, in the Open text box, type cmd and then click OK.
    A cmd.exe window opens.
  3. At the command prompt, type nslookup and then press Enter.
    The nslookup program should provide one or more IP addresses for  If the nslookup program does not provide any IP addresses, or "Non-existant domain" is seen, then the DNS server is not resolving the name.

Verify that a file called "trusted.cert" exists

  1. Look for the presence of this file in C:\Program Files\Symantec\SMSMSE\<version>\Server\etc 32-bit system or C:\Program Files (x86)\Symantec\SMSMSE\<version>\Server\etc 64-bit systems (default installation path of SMSMSE)
  2. If the folder 'etc' does not exist, create under \Server a folder called etc
  3. If the file trusted.cert does not exist, copy the 'trusted.cert' file from the installation files into the \Server\etc folder
  4. License Premium AntiSpam in SMSMSE, again, via the SMSMSE Console
  5. Enable Premium AntiSpam

Verify that the bmiconfig.xml was created correct during installation

  1. Navigate to C:\Program Files\Symantec\SMSMSE\<version>\Server\SpamPrevention 32-bit system or  C:\Program Files (x86)\Symantec\SMSMSE\<version>\Server\SpamPrevention 64-bit system
  2. Locate the file bmiconfig.xml, right click and open with notepad
  3. Look for the tags

<loadpoint>C:\Program Files\Symantec\SMSMSE\6.0\Server</loadpoint>
<logdir>C:\Program Files\Symantec\SMSMSE\6.0\Server\logs</logdir>
<spooldir>C:\Program Files\Symantec\SMSMSE\6.0\Server\spool</spooldir>
<statsdir>C:\Program Files\Symantec\SMSMSE\6.0\Server\stats</statsdir>
<configdir>C:\Program Files\Symantec\SMSMSE\6.0\Server\SpamPrevention</configdir>
<clientCert>C:\Program Files\Symantec\SMSMSE\6.0\Server\etc\cert.pem</clientCert>
<trustedCert>C:\Program Files\Symantec\SMSMSE\6.0\Server\etc\trusted.cert</trustedCert>

4. Verify each path is correct, in some cases they will be filled out as "pathto\basedir" instead of the full filepath.

If the file paths are not filled out correctly, do one of the following:

1. Open the registry editor (Start -> Run, Regedit).
2. Find the following registry folder:

32-bit systems: HKEY_LOCAL_MACHINE\Software\Symantec\SMSMSE\<version>\Server\Components\SMTP\BMIConfigInit

          64-bit systems: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Symantec\SMSMSE\<version>\Server\Components\SMTP\BMIConfigInit

3. In the right pane, locate the value BMIConfigInit, right click it and choose Delete.
4. Restart the Symantec Mail Security for Microsoft Exchange service.  The bmiconfig.xml file should now contain the correct values


Fill out the file paths correctly in the bmiconfig.xml using notepad, save the file and restart the Symantec Mail Security for Microsoft Exchange service.

Technical Information

The SMSMSE Administration Console uses the command line tool register.exe for registering the SPA license.  Use the following KB article to get more details from the command line on the source of the error:  How to Manually License Premium AntiSpam for Symantec Mail Security for Microsoft Exchange (SMSMSE).  If there are error messages displayed by the tool, search the SMSMSE KB articles for the error message.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices