• 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.

Issue smb_apsMetas table empty

John W

New Pleskian
Server operating system version
CentOS 7.9.2009
Plesk version and microupdate number
18.0.68 Update #2
I was trying to update a WP admin password in WP Toolkit, but received the following error:
Unable to update site administrator settings: Unable to find row with id in smb_apsMetas table.

I followed instructions on https://support.plesk.com/hc/en-us/...ble-to-find-row-with-id-in-smb-apsMetas-table and found the error:
8905:6801596452811 DEBUG [dbquery] [89] SQL: SELECT `smb_apsInstances`.* FROM `smb_apsInstances` WHERE (((`smb_apsInstances`.`id` = 214)))

But step four, "SELECT * FROM smb_apsInstances WHERE id=214;" yielded no results.

Out of curiosity, "SELECT * FROM smb_apsInstances" returned:
Empty set (0.00 sec)

Is that normal? How can it be fixed? I ran all the repairs from the GUI to no avail.

Thanks,
John
 
Hi John!

Have you tried the last 2 steps of the guide? After the statement that says "if the issue persists." That fix should work in cases when it's not possible to find the records to restore. Just make sure you back up the database as instructed in the step 1 of that section.
 
Back
Top