FileCatalyst Server will not start after migrating from Windows Server 2003 to 2008
Posted by , Last modified by Aly Essa on 04 August 2016 12:41 PM

Overview

When FileCatalyst Server is started as a Service by the user account that is different than user account that installed software the FileCatalyst Server stops. It does not start automatically when set to Auto in the Service Manager. 

There are implemented much tighter security policies in Windows Server 2008 than in Windows Server 2003. Only owners of the application folder can start FileCatalyst Servers' service.

 

Environment

FileCatalyst Server v3.4 and later.

Windows Server Environment.

 

Resolution

If the new user is created for the purpose of starting the application as a service, this user account has to have read and write permissions to the folder where the application is installed. Additionally, you can start the Service using this service account through the Service Manager.

  1. Click Start.
  2. Open the Run command.
  3. Type Services.msc and hit OK.
  4. Locate the FileCatalyst Server service, right-click on it and select Properties.
  5. Click Log On to shift to that tab.
  6. Choose the This Account radial and fill in the service account information.
  7. Hit OK.
  8. Start the FileCatalyst Server service.