Error when registering Premium AntiSpam after making changes for Conduit.exe CPU issue
|Article:TECH155085|||||Created: 2011-03-08|||||Updated: 2012-01-16|||||Article URL http://www.symantec.com/docs/TECH155085|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
You are unable to register Premium AntiSpam after applying the workaround from this article: The process conduit.exe is using high CPU with Symantec Mail Security for Microsoft Exchange (SMSMSE) 6.5.2 or Higher.
- If registering the license using the Symantec Mail Security for Microsoft Exchange (SMSMSE) console the following error message is shown:
Symantec Premium AntiSpam registration failed on the server <ServerName>.
The product will not receive definition updates until registration completes. If a valid license file has been provided, the console will display that the license is installed and will re-attempt registration when the feature is enabled via the console.
To troubleshoot the registration issue, do the following:
1. Ensure that a valid, up-to-date Premium AntiSpam license is installed.
2. Confirm that the server has network and internet access.
3. Verify that DNS can resolve aztec.brightmail.com.
3. If using a proxy server, allow outbound secure https through firewall (port 443), for all users.
4. If using proxy server, see documentation for manually running register.
- If registering the license manually using this article How to Manually License Premium AntiSpam for Symantec Mail Security for Microsoft Exchange (SMSMSE), the following error message is shown:
Registration server returned:404 Not Found.
The BMI configuration file (bmiconfig.xml) is not configured to use rules2 as the testURL.
1. Open the bmiconfig.xml file in an editor:
C:\Program Files (x86)\Symantec\SMSMSE\<version>\Server\SpamPrevention\bmiconfig.xml
2. Find the line with <testURL>. It should refer to rules2. If it does not refer to rules2 then this condition is met.
This is an example of what the file should look like:
This is an example of a mis-configured file:
The BMI configuration file is using the incorrect test URL.
Typically this occurs when applying the workaround from this article: The process conduit.exe is using high CPU with Symantec Mail Security for Microsoft Exchange (SMSMSE) 6.5.2 or Higher.
Re-apply the workaround from article The process conduit.exe is using high CPU with Symantec Mail Security for Microsoft Exchange (SMSMSE) 6.5.2 or Higher using the script 1.2 or higher.
Article URL http://www.symantec.com/docs/TECH155085