• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Migration tools error: Unable to update database user properties: attribute name is invalid: status

femotvaff

Regular Pleskian
Hello,
I'm trying to use the migration tool to migrate some sites from a

Server B Plesk 12 (unlimited subscription licence) to Server A Plesk12 (web admin licence)

Now after lot of problems solved, the last problem is that all DBs for a 1 "subscription" have these alerts:

Failed deployment of database ...
Stderr is
Unable to update database user properties: attribute name is invalid: status

Failed deployment of database ...
Stderr is
Unable to update database user properties: attribute name is invalid: status

Failed deployment of database ...
Stderr is
Unable to update database user properties: attribute name is invalid: status

...


Any idea how to solve the problem,
I didn't find anything about this case.
Thank you for any help.
 
Thank you!

The solution in MU#40 is to make Plesk microupdates in both servers.
but really I already did it to solve an other problem with this command on both servers:

/usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base

Now I will try to see if the update of MU#40 is on the servers or not
 
Last edited:
SOLVED

in both server I used this command to make Plesk 12 microupdates:
/usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base

in 1 Server some components was still not updated.
I lunched the automatic component update from Tools/"updating" menù of Plesk (check both servers) and this problem was solved.
 
Back
Top