Neverfail for Exchange Start Script Must be Modified When Microsoft Forefront Security for Exchange is Installed

Follow
KB-01218 TABLE { font-family: "verdana"; font-size: xx-small; color: #484848; } blockquote { margin-top: 0; margin-bottom: 0; } ul { margin-top: 0; margin-bottom: 0; } li { margin-top: 5; margin-bottom: 5; } h5 { margin-bottom: 5; } .nf-red { color: #BD3447; } .nf-header1 { font-family: Verdana; font-size: 10pt; font-weight: bold; } .nf-header1red { color: #BD3447; font-family: Verdana; font-size: 10pt; font-weight: bold; } .nf-header2 { font-family: Verdana; font-size: 10pt; } .nf-body { font-family: Verdana; font-size: 7.5pt; } .nf-link { font-family: Verdana; font-size: 8pt; color: #BD3447; } .linkLight { font-family: "verdana"; font-size: 14; color: #9A1718; font-weight: bold; text-decoration: none; }

Summary

This Knowledgebase article provides information about how to modify the Neverfail for Exchange Application Module Start script when Microsoft Forefront Security for Exchange Application Module eXtension is installed.


More Information

When Microsoft Forefront Security for Exchange is installed on a server group running Neverfail for Exchange Application Module, the Start script must be modified to prevent errors during the startup process.

FSEIMC is responsible for registering the FSE Agent to ensure that messages are scanned by the FSCTransportScanner process. The Transport service depends upon the FSEIMC service, which is designed to start and then stop. To clear the error in the Neverfail Management Client, select the Application tab, and then click Clear in the Application Health pane.

The FSEIMC service is always set to manual and stopped; if one tries to start it, it will start and stop and give a default message after stopping. Because it is set to manual and stopped, it is not picked up and protected by the AMX. However, since the Microsoft Exchange Transport depends on it, and that service is protected, it will try to start the FSEIMC service as well, and return "FAILED" even though the Transport service starts (because the FSEIMC starts/stops quickly and doesn't report progress as expected).

If Microsoft Exchange Transport service fails when it is restarted by Heartbeat, the following message is reported:

FSEIMC: Time out has expired and the operation has not been completed

To prevent further occurrences of this error, use sc.exe to remove the dependency between the Transport Service and the FSEIMC service. The Neverfail Application Management Framework (AMFx) then ensures that the service starts. Open a command prompt and enter the following command:

sc config MSExchangeTransport depend= MSExchangeADTopology

Procedure

To prevent the error messages, perform the following steps on both the Primary and Secondary servers:

Versions 5.2.[n] and Earlier

  1. Navigate to \R2\scripts\Exchange\start.bat.
  2. Using a text editor, change:
From: NfNet Start "MSExchangeTransport" /R || set FAILED=1
To: Net Start "MSExchangeTransport"
NOTE: There may be more than one "NfNet Start "MSExchangeTransport" /R || set FAILED=1" command in each script. You should either remove the multiple presences, or change them all to use Net Start "MSExchangeTransport".

Additionally, to prevent error messages as a result of dependencies, change the default 90sec limit for "MSExchangeADTopology" service start to prevent "Timeout Application Start/Stop" error messages.

To do this, make the following changes:

From: NfNet Start "MSExchangeADTopology" /R || set FAILED=1
To: NfNet Start "MSExchangeADTopology" 250 /R || set FAILED=1

Versions 5.3.[n] and Later

  1. Remove the MSExchange Transport service dependency on FSEIMC by executing the following::
sc config MSExchangeTransport depend= MSExchangeADTopology
  1. Create start.bat in <Neverfail_installation_folder>\R2\bin with the following content:
Net Start "MSExchangeADTopology"
Net Start "MSExchangeTransport"
  1. Open the Neverfail Heartbeat Management Client.
  2. Navigate to Application > Tasks.
  3. Click Add .
  4. Type a name for the new task.
  5. Select the Pre Start Task Type.
  6. Type start.bat as a command.
  7. Click OK.

Applies To

Microsoft Forefront Security for Exchange


Related Information

None

KBID-1218

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.