Regarding slowness, the sync logs may be getting too large, and standard db maintenance is required.
It's possible the sync did not complete and another sync or crash is preventing the LastPushTime from updating
In terms of the error being reported the 577 indicates "(invalid usage - see NSF documentation)". Domino documentation does not reference this error, the closest we found is the generic “Invalid or nonexistent document”. It is possible there is a malformed or corrupt document causing the error.
We recommend the following steps to remediate:
1. If not already disabled, disable the automatic schedules for the syncs for the profiles (Domino program doc for Push and corresponding schedule for Pull).
2. Allow any running syncs for the profiles to complete.
3. Back up the DirsyncProLogs SQL database through SQL (back up to disk is fine – for that right click the SQL database and use Tasks – Backup and create a disk destination).
4. Clear the BT_Log2 table from the DirsyncProLogs SQL database (Truncate Table [DirsyncProLog].[dbo].[BT_Log2]).
5. Restart the DSP Domino task (or the Domino server itself that runs the groups sync)
6. Re-enable the automatic schedules for the syncs, if you have a scheduled sync.
7. Verify that the groups sync does start and then allow that to run and if it does report an error gather the Domino and DSP logs for review.
Note: this is not going to clear the audit logs, this does not need to be done now and can be reviewed after the above are completed.
Depending on how the initial steps above go, the next steps are going to be to run Domino maintenance on the source nsf (compact, fixup, updall) to at least verify there are no data issue in the source nsf that Domino itself would resolve.
If this does not resolve the issue open SQL to the Dirsync DB and update the LastPushTime manually to a more recent date. Restart IIS via an IISRESET command prompt.
