Overview

The Central Management Server (CMS) installed in LanGuard can occasionally run into corruption errors after being installed. This causes the service to fail to start. Once the service failed to start, the CMS will no longer function and will not be able to gather information from the main LanGuard server installations, where it is attached for centralized reporting.

This article demonstrates how to diagnose a server update issue along with its resolution.

Process

Diagnosing a Failed Server Update

If the customer reports that the "GFI LanGuard 12 Server Update" service fails to start, check the following before troubleshooting:

1. Verify that the credentials have the correct permissions to run the service. In most cases, the default setting using the Local Service Account should be enough.
2. Verify that there are no restrictions placed on the same Local Service Account via environment-specific variables, such as changes to the Group Policies or permissions.

Fixing a Failed Server Update

The main confirmation for an Update Service corruption or failure can be found in the Application Event Logs while starting the service. Follow the steps below to locate and verify the error.

1. Select Start > Run.
2. Type eventvwr.msc in the textbox.
3. Expand Windows Logs > Select Application.
4. Locate the time of the attempted service start.
5. The error is displayed, as shown in the image below. The main component in the General tab returns the error:  System.Xml.XmlException: Root element is missing.
   
   
   
   
   
6. Check if you are on the latest release of LanGuard CMS. Read this article on GFI LanGuard 12.5 release notes and upgrade to the latest version.
7. After validating the occurrence of a Server Update Failure, re-install or repair the Central Management Server to resolve the issue.

Back to top

Confirmation

If you are not on the latest release of LanGuard/CMS, an upgrade can be attempted to fix the issue.

Back to top