Skip to content

Troubleshooting & Known Issues

This page collects known issues and general troubleshooting information for GroundControl VGRS that don't fit into a specific module or setup guide.

Known Issues

Web Service Fails to Start During a Windows Language Pack Installation

Symptom: After a system restart or update, the Web Service does not start, while all other GroundControl VGRS services start successfully.

Observed cause: This has been observed on a customer system where a Windows language pack installation/update was running in the background at the same time GroundControl VGRS services were starting. Once the language pack installation finished, the Web Service could be started normally (either automatically after a delay, or via a manual restart).

Why only the Web Service is affected

Windows language pack installations and updates are handled by the Windows Modules Installer service (TrustedInstaller), which performs Component-Based Servicing (CBS) operations. While a CBS operation is in progress, Windows can lock system components, registry keys, and files (e.g. under System32 and WinSxS) that are involved in servicing.

The Web Service takes noticeably longer to start than the other GroundControl VGRS services, since it needs to load more dependencies (ASP.NET Core runtime components, hosting libraries, etc.). This makes it more likely to hit an active servicing lock during its startup window, while the lighter, faster-starting services complete before the lock becomes an issue. This points to a timing/service-lock conflict rather than an issue with GroundControl VGRS itself.

Workaround:

  • If the Web Service fails to start, check whether a Windows Update or language pack installation is in progress (Task Manager → look for TiWorker.exe / TrustedInstaller.exe, or check Windows Update history).
  • Wait for the servicing operation to complete, then start the Web Service manually via the Manager Tool or the Windows Services console (services.msc).
  • Where possible, avoid triggering language pack installations or Windows Updates during a GroundControl VGRS installation, update, or scheduled restart, to prevent the two servicing operations from overlapping.

DAMM Subscriber Logs Error Code -7

Symptom: The DAMM Subscriber logs error code -7.

Cause: No DAMM license dongle could be found for API access.

Solution: Ensure the DAMM license dongle is plugged in, then restart the subscriber so it can detect it. The easiest way to do this is to restart the Subscriber Broker service.

Event Log Database Grows Too Large

Symptom: The event log database keeps growing over time and can eventually fill up, which may impact performance or, in extreme cases, prevent GroundControl VGRS from connecting to the database at all.

Solution: Set up a schedule in the Manager Tool to periodically clear the event log database (Manager → Schedules).

High Log Volume

If a very large amount of logs is generated, set MaxAgeInDays to 1 (or even 0) in the schedule. This keeps only today's logs (1), or only the logs generated since the last schedule run (0).

Delay Database Growth Issues

Using a larger edition of Microsoft SQL Server than Express (which has a 10 GB database size limit) can also help delay running into database size problems.

Manual Workaround

If the database is already so full that GroundControl VGRS can no longer connect, the corresponding event log table can be cleared manually by running TRUNCATE TABLE on it in SQL Server Management Studio. Use this only as a last resort, and be sure to target the correct table since TRUNCATE TABLE cannot be undone.