Microsoft Knowledge Base Email Alertz

Exchange services cannot be started, and event ID 7024 is logged after you install Symantec Mail Security on a Windows Server 2008-based computer that is running Exchange Server 2007

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 954204 - Last Review: February 20, 2009 - Revision: 2.0

Exchange services cannot be started, and event ID 7024 is logged after you install Symantec Mail Security on a Windows Server 2008-based computer that is running Exchange Server 2007

SYMPTOMS

After you install Symantec Mail Security on a Windows Server 2008-based computer that is running Microsoft Exchange Server 2007, Exchange services cannot be started. Additionally, the Exchange Active Directory Topology Service fails, and the following event error is logged in the System log:

Log Name: System
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
Description:
The Microsoft Exchange Active Directory Topology Service service terminated with service-specific error 2147942414 (0x8007000E).

Note When this issue occurs, you cannot resolve this issue by uninstalling Symantec Mail Security. You may also notice that you cannot clear the Application log events.

CAUSE

This issue occurs because Symantec Mail Security modifies the following registry subkey to write event logs only for Symantec applications:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\Application\CustomSD
Therefore, when Exchange services tries to log events in the event log, Exchange services receives an "access denied" error message, and Exchange services cannot be started.

RESOLUTION

To resolve this issue, upgrade to Symantec Mail Security for Microsoft Exchange version 6.06. This version of Symantec Mail Security for Microsoft Exchange includes full support for Windows 2008.

MORE INFORMATION

For more information about the CustomSD registry subkey, click the following article number to view the article in the Microsoft Knowledge Base:
323076  (http://kbalertz.com/Feedback.aspx?kbNumber=323076/ ) How to set event log security locally or by using Group Policy in Windows Server 2003
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

REFERENCES

For more information, visit the following Symantec Web sites:
http://service1.symantec.com/support/ent-gate.nsf/854fa02b4f5013678825731a007d06af/b594607c46cde6f280257372003cb3f7?OpenDocument (http://service1.symantec.com/support/ent-gate.nsf/854fa02b4f5013678825731a007d06af/b594607c46cde6f280257372003cb3f7?OpenDocument)
http://service1.symantec.com/support/ent-gate.nsf/854fa02b4f5013678825731a007d06af/18e2d707a1bf85068825738600629e24?OpenDocument (http://service1.symantec.com/support/ent-gate.nsf/854fa02b4f5013678825731a007d06af/18e2d707a1bf85068825738600629e24?OpenDocument)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

APPLIES TO
  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Service Pack 1
Keywords: 
kbexpertiseinter kbtshoot kbprb KB954204
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate