The database for the Webgility Desktop application is located in an SQL Server instance. The Webgility Desktop program is installed prior to the SQL installation. There may be a situation where the SQL error logs take up disk space when the Webgility Desktop program is installed on a local server. These error logs typically occur as a result of SQL's excessive error recording activity and are typically not used.
The "DBUtility" program from Webgility (UnifyDBUtility.exe) can assist in resolving this problem and keeping the C: drive free of any unnecessary logs.
Problem Identification:
SQL is always installed on the C:\ drive of your server computer.
To check the ‘Logs’ folder of SQL, you need to access the below path:
C:\Program Files\Microsoft SQL Server\MSSQL15.WEBGILITY\MSSQL\Log
OR
C:\Program Files (x86) \Microsoft SQL Server\MSSQL15.WEBGILITY\MSSQL\Log
The logs will be located in the SQL installation and "Logs" folder.
The log file sizes can be measured in gigabytes. When examining the size of the "ERRORLOG" files, the larger log files should be removed.
Steps to delete the ERRORLOG files:
Once the log file issue has been located, the first step is to exit Webgility's automation and quit the Webgility Desktop application on any computer it has been installed on.
Below is a reference article which gives an overview of the scheduler.
The scheduler icon shows no color (no green or orange) when the automation is turned OFF.
Next, please click on the "Windows" icon from the bottom left-hand side of the screen, and type the word "services" to access the services menu.
In the "services" menu, we need to select the active database service SQL Server (Webgility Database Name) then Right Click on the Stop button.
If you need to find the SQL Database name, access and open the "API Config" file, which is located in the C:\Webgility\UnifyEnterprise\XML folder. In the "Data Source" section as seen below, you will discover the name of the database:
Now, to delete the "ERRORLOG" files, please access C:\Program Files\Microsoft SQL Server\MSSQL13.UNIFY\MSSQL\Log > Select the ERRORLOG files > Right Click > Delete.
Once these log files are deleted, please access the "Services" menu once again Right Click on the service SQL Server (Webgility Database Name) which was stopped earlier then click on Start.
Close the "Services" window and access C:\Webgility\UnifyEnterprise and double-click on the file named UnifyDBUtility and run the file.
After the "UnifyDBUtility" file has finished running, you can restart the Webgility application and scheduler. Going forward, SQL should be prevented from making excessive logs.
For any further questions or issues, please send an email to support@webgility.com You can also go to webgility.com and chat with our support team or use the chat option from within the Webgility application itself!