If fixing the replication under the wiki guide Handling Replication Errors has not worked then the easiest thing to do is to reset replication.
Be aware that the process will involved stopping DualShields Server Services, therefore there will be some down time.
Stage 1 – Remove the broken machine from the cluster.
The DualShield Server service will need to be stopped on all of your VMs running DualShield.
Once done You can then launch DualShield Assistance on your Primary machine, and go into Replication→Management
Delete the server with the replication issues and click on Modify Cluster
You will see the clusters being modified:
Once Finished you can restart the DualShield Server service machines.
Stage 2 – Uninstall DualShield from the VM you have just removed from the cluster
Go on to the sever that you have deleted from Cluster Management in the stage 1, above.
In fie explorer, browse to ...C:\Program Files\Deepnet DualShield\Uninstaller and click on RemoveDualShield.exe.
Stage 3 – Deploy clone of working version of server to the VM
Deploy from the server with the most up-to-date database by launching DualShield assistant on it and following this document.
http://wiki.deepnetsecurity.com/display/DUALSHIELD/Cloning+DualShield
Dualshield server and MYSQL services will be stopped on the local server as the cloning process takes place. Please follow the instructions carefully remembering to start the MYSQL service on both machines but leave the DualShield server service off for now.
Stage 4 – Add the Repaired machine to the cluster.
Please follow this guide.
http://wiki.deepnetsecurity.com/display/DUALSHIELD/Setting+up+Replication
It will involve stopping the DualShield Server service on all the machines, beforehand though.