-
Title
DSP: DirSync profiles are stuck in "Syncing" status -
Description
DirSync profiles are stuck "Syncing" This issue just started, we had no issues until recently. What can be causing this?
OS EVENT LOG ERROR: The transaction log for database 'DirSyncProLog' is full due to 'LOG_BACKUP'.
Q. Can this file cause problems being too large? DirSyncProLog_log.ldf
A. Yes -
Cause
Log file table has become very large -
Resolution
Check each profile to ensure the log level is set to Low.We recommend the log auto purge setting to be set to two weeks. It can be set to a lesser value if the log levels are growing too quickly.
What is the sync interval set to for each profile?
Steps to clean up.
1. Open SQL Management Studio on the SQL server
2. Right click on the DirsyncProLog database (that is the default name, the name of the log may be different in your environment)
3. select New Query
4. Type the following within the New Query Editor window: Select * from dbo.BT_log2 (this will show you the?logs within the table)
5. To Truncate, erase the previous query and type: Truncate table BT_log2 and hit Execute( or F5). This will delete the contents within the table
6. On the Windows Dirsync server: close out of DirSync
7. restart the BinaryTree SMART DirSync service(To perform this operation ensure the BTCodexlog DB is selected within the drop down menu below the 'New Query' option).
After performing the above, please read this KB article:DSP: Clearing the logs, setting log levels and testing the SQL connections DSP 19.07 (B365891)
In addition to discussing how to clear the logs it also discusses setting the log purge intervals. If logging level is set to low I would set the purge interval to 2 weeks. This will prevent future log build-up. Ensure these settings are applied to all profiles.
As for Sync Report data, it can be cleared from the SQL tables following steps 1-7 above but substituting dbo.Dirsync_AuditData for dbt.BT_Log2. As documented in the KB article above, you can periodically purge report data, but it has to be done manually at this point. The current Dirsync product doesn't include the ability to set a purge interval for sync report data.