Webgility Desktop Will Not Load When the C: Drive Is Full
Webgility Desktop may stop loading when the local C: drive has very little free space. SQL logs, error logs, shipping logs, and older backup files can accumulate over time and consume available storage. In the referenced support case, removing unnecessary files, an old backup, and Webgility logs freed disk space and restored Webgility Desktop.
Resolution
- Close Webgility Desktop and disable the Webgility Scheduler.
- Press Windows + R, enter
services.msc, and select OK. - Locate the SQL Server service used by Webgility, commonly named
SQL Server (WEBGILITY)orSQL Server (UNIFY). If you need to confirm the instance name, openC:\Webgility\UnifyEnterprise\XML\APIConfig.xmland review the SQL instance entry. - Right-click the SQL Server service and select Stop.
- Review the SQL log folder and remove obsolete
ERRORLOGor text log files. Depending on the SQL Server installation, the folder may be one of these locations:C:\Program Files\Microsoft SQL Server\MSSQL15.WEBGILITY\MSSQL\LogC:\Program Files (x86)\Microsoft SQL Server\MSSQL15.WEBGILITY\MSSQL\Log
- Review
C:\Webgility\UnifyEnterprise\ErrorlogandC:\Webgility\UnifyEnterprise\ShippingLog, and remove obsolete log files. Remove only known log files and old backups. Do not delete active database or configuration files. - Return to Services and start the SQL Server service.
- Open
C:\Webgility\UnifyEnterprise, right-clickUnifyDBUtility.exe, and select Run as administrator. - Launch Webgility Desktop and re-enable the Scheduler.
Verify the resolution
Confirm that Webgility Desktop opens normally and that the Scheduler starts without errors.
Maintenance recommendation
Review available space and remove obsolete Webgility logs and backups regularly. A 30 to 60 day cleanup interval may help prevent recurring disk space warnings, depending on system usage. If Webgility Desktop still does not load after the cleanup, contact Webgility Support with the available C: drive space and the steps already completed.