Troubleshooting: FileSync Service Fails to Start (Error 1053)

Version Affected: All (FileSync 3.4.5 and below)
 
 

Overview

This article explains how to resolve an issue where the FileSync service hangs in a starting state and times out, or fails to start or restart with the error: "Windows could not start the SecureAuth FileSync Service service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

The Windows Event Viewer System log shows a matching Event 7000 from Service Control Manager.

Cause

The SecureAuth FileSync service has a digital signature that lets .NET validate the binary's authenticity at runtime — a feature known as Code Access Security (CAS). If CAS cannot reach the GoDaddy/Starfield CRL-OCSP URLs to check for certificate revocation, the .NET thread can hang, preventing the service from starting.

Resolution:

To resolve this:

1. Allow the FileSync service to reach the GoDaddy/Starfield CRL-OCSP URLs — whitelist them in your firewall or proxy.
2. If security policy does not allow opening access to those URLs, disable CAS instead. Edit the FileSync service configuration file, located at D:\MFCApp_Bin\Appliance_Sync\FileSyncService\FileSyncService.exe.config. Change:
   

   <generatePublisherEvidence enabled="true"/>

   to:
   

   <generatePublisherEvidence enabled="false"/>

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.