Microsoft KB Archive/939365

= Forefront Security for Exchange Server fails in a single copy cluster environment =

Article ID: 939365

Article Last Modified on 9/21/2007

-

APPLIES TO


 * Microsoft Forefront Security for Exchange Server

-



SYMPTOMS
You may experience the following symptoms that are related to Microsoft Forefront Security for Exchange Server in a single copy cluster (SCC) environment.

Symptom 1
When you install Forefront Security for Exchange Server in an SCC environment, the installation fails, and you receive the following error message:

Setup Failed to create the Forefront resource(s) and configuration in the EVS

In addition, the Forefront Install log contains information that resembles the following: 09:35:24 048 szErrorDesc = Error SetupAntigenEVS: SetupAntigenMSCSEVS: ClusterResourceControl CLUSCTL_RESOURCE_SET_PRIVATE_PROPERTIES) failed.

Symptom 2
When you install Forefront Security for Exchange Server in an SCC environment, the installer performs passive node installation on an active node if the node name has 15 characters. After the installation, you cannot see any information in Forefront Server Security Administrator.

Symptom 3
After a clustered mailbox server (CMS) fails over to an active node, you cannot see any information in Forefront Server Security Administrator.

Symptom 4
When you install Forefront Security for Exchange Server in an SCC environment, the installation fails. This occurs after you select the shared resource to install Forefront Security for Exchange Server. In addition, the Forefront Install log contains information that resembles the following: 23:20:27 013 szErrorDesc = Error GetEVSInfo: GetMSCSEVSInfo: An Active node of an Active/Passive MSCS cluster is found, but no match for the shared drive is found.

Symptom 5
You cannot use mount points as the shared resource to install Forefront Security for Exchange Server. In addition, the Forefront Install log contains information that resembles the following: 23:20:27 013 szErrorDesc = Error GetEVSInfo: GetMSCSEVSInfo: An Active node of an Active/Passive MSCS cluster is found, but no match for the shared drive is found.



Cause 1
Symptom 1 occurs because the Forefront Security for Exchange Server discovery routine incorrectly detects active nodes and passive nodes. Therefore, an active node is incorrectly detected as a passive node.

Cause 2
Symptom 2 occurs because Forefront Security for Exchange Server cannot handle node names of more than 14 characters.

Cause 3
Symptom 3 occurs because Forefront Security for Exchange Server does not prevent active nodes from failing over to the same node. If no passive node exists, the resources will fail over to one of the active nodes. In this case, Forefront Security for Exchange Server cannot work correctly because the application registry has been overwritten.

Cause 4
Symptom 4 occurs because the shared resource names that are specified during installation contain incorrect syntax. The installer presents a text box for shared resource names. Users may input shared resource names that are syntactically incorrect. Therefore, the installation fails.

Cause 5
Symptom 5 occurs because Forefront Security for Exchange Server cannot correctly detect and cannot correctly configure mount points for use as shared drives. Forefront Security for Exchange Server cannot detect shared storage resources that third-party volume management tools manage.



Hotfix installation information
A hotfix is available to resolve these symptoms. This hotfix can be installed only on single copy clusters. To apply this hotfix, you must completely uninstall the current version of Forefront Security for Exchange Server, and then apply this hotfix. This hotfix performs a full installation of Forefront Security for Exchange Server.

After you apply this hotfix, a new FSECluRes cluster resource will appear in the cluster group. This new cluster resource makes Forefront Security for Exchange Server cluster-aware. Therefore, cluster resources will come online in the correct order. The order in which cluster resources come online is determined by using a set of dependencies.

How to uninstall Forefront Security for Exchange Server
Caution
 * Do not restart any computer until Forefront Security for Exchange Server is uninstalled from all nodes, even if the uninstaller prompts you to restart a computer. Otherwise, if an active node is restarted, the clustered mailbox server that is running on the node may move to a passive node before the passive node finishes the uninstallation.
 * Do not manually move any clustered mailbox server until Forefront Security for Exchange Server is uninstalled from all nodes.

To uninstall Forefront Security for Exchange Server from a single copy cluster, follow these steps:
 * 1) Make sure that the node that was active during installation is also active during uninstallation.
 * 2) Make sure that the clustered mailbox server that was running on the node during installation is running on the same node during the uninstallation.

Note Step 2 is required because the uninstaller will clean up the files in the shared disk drive. Then, the uninstaller will remove the registry replication configurations from the clustered mailbox server.

For example, assume that you have a three-node single copy cluster that has two clustered mailbox servers. The three nodes are named Node1, Node2, and Node3. The two clustered mailbox servers are named CMS1 and CMS2. Additionally, when you installed Forefront Security for Exchange Server, CMS1 was running on Node1, and CMS2 was running on Node2. Node3 is a passive node. Before you start the uninstallation, CMS1 must be running on Node1. CMS2 must be running on Node2. Node3 must be a passive node.
 * 1) Click Start, point to Control Panel, and then click Add or Remove Programs. Then, use Add or Remove Programs to uninstall Forefront Security for Exchange Server.

Note The uninstallation process stops Internet Information Services (IIS), and the uninstallation process takes the clustered mailbox server offline on the active node.
 * 1) Uninstall Forefront Security for Exchange Server from the active nodes.
 * 2) Uninstall Forefront Security for Exchange Server from the passive nodes.

How to apply this hotfix
To apply this hotfix, follow these steps:
 * 1) Before you start the installation, make sure that you have prepared the license activation key.
 * 2) Double-click the hotfix package.
 * 3) After you complete the installation, enter your activation key.

For more information about installation of Forefront Security for Exchange Server, see the Administrators Guide.

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply this hotfix, you must be running a single copy cluster.

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: fss rollup scc

Keywords: kbexpertiseinter kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB939365

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.