Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Strange Plan Sync Error Message
- Thread starter MorrisC
- Start date
MorrisC
Basic Pleskian
Thanks, UFHH01,
I found there are so many longtasks params and in long tasks, therefore, I delete all of them from the record.
I then move customers to another plan and delete the original plan. And create the plan again and move them back.
No more sync problem message anymore.
From my understanding, since the primary key should be unique, therefore, deleting records in longtasks and longtakparams tables should resolve the issues.
I found there are so many longtasks params and in long tasks, therefore, I delete all of them from the record.
I then move customers to another plan and delete the original plan. And create the plan again and move them back.
No more sync problem message anymore.
From my understanding, since the primary key should be unique, therefore, deleting records in longtasks and longtakparams tables should resolve the issues.
Last edited:
Similar threads
