Troubleshooting: FileSync Reports "This SecureAuth Appliance is a Primary Node"

Version Affected: All
 
 

Overview

This article explains how to resolve an error where SecureAuth FileSync reports that an appliance is a primary node, either when running the replica installer after uninstalling FileSync from a secondary appliance, or when reinstalling FileSync on a former primary appliance that is now being configured as the secondary (replication) node.

 

Cause

When FileSync is first installed on an appliance, several registry keys are added under HKEY_LOCAL_MACHINE\SOFTWARE\SecureAuth\FileSync, including a NodeType value. Uninstalling or reinstalling FileSync does not remove these registry keys. If the appliance's NodeType value is still set to PRIMARY from its previous role, the installer continues to detect the appliance as a primary node and refuses to install it as a secondary node, even though FileSync itself may no longer be present.

Resolution:

To resolve this:

1. If FileSync is currently installed, confirm all FileSync services have been stopped, uninstalled, and deleted from the appliance. The FileSync installer and the Application Event Viewer both show the error: "This SecureAuth Appliance is a primary node. Please contact SecureAuth Support for further assistance."
   
2. Open the Registry Editor (regedit.exe) and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\SecureAuth\FileSync.
3. Confirm the NodeType value is set to PRIMARY, then delete the entire FileSync registry key and all of its subkeys.
   
4. Browse to D:\MFCApp_Bin\Appliance_Sync and rerun the FileSync setup as Administrator.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.