• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

SQL error by Domainadministrator

A

aaargh

Guest
When a user logged in as domain admistrator and want to make changes to the hosting setup, it gets the following error:

Unable to query: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
0: /usr/local/psa/admin/plib/class.IPAddressSelector.php:87 psaerror(string "Unable to query: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1")
1: /usr/local/psa/admin/plib/class.IPAddressSelector.php:62 ipaddressselector->fetchcertslist()
2: /usr/local/psa/admin/plib/class.PHostingManager.php:84 ipaddressselector->ipaddressselector(integer "8", integer "18", NULL "")
3: /usr/local/psa/admin/htdocs/domains/hosting/phosting_setup.php:32 phostingmanager->phostingmanager(integer "365")

This only occurs in "domain administrator" mode.

I'm running plesk 7.5.2 on FreeBSD 4.9

Anyone here seen this before and know how to solve this ?

regards,

Maurice
 
There is a problem in your psa database, but it's impossible to be diagnosed remotely. The error can be caused by an unsucesfull upgrade attempt.
 
I have upgraded this server from 7.0 to 7.1.6 to 7.5.2, and indeed I noticed some problems, but those have been fixed, this is the only problem left.

If you need some more info, please let know what you need.
 
This issue can not be diagnosed without access to your server, sorry.
 
Back
Top