• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

After 10.0.1 UG from 9.5.2, can't get into Domain Control Panel

M

matrixtech

Guest
I have scoured the forums and KB here at Parallels for another user having this problem. I have eliminated most errors (except for how to make SSO work without disabling it, but that's another matter), but when I go into any of my or my customer's domain control panel links, this is what I see (had to turn on Remote Error Responses):

scaled.php


Also, the panel.log file says much the same thing:
2010-11-18T00:16:12-05:00 CRIT (2): com_exception: <b>Source:</b> Microsoft OLE DB Provider for SQL Server<br/><b>Description:</b> Invalid column name 'userId'.
file: C:\Program Files (x86)\Parallels\Plesk\admin\plib\common_func.php3
line: 119
code: -2147352567

I don't know if related, but I also get errors trying to modify customers:
2010-11-16T00:21:19-05:00 CRIT (2): com_exception: <b>Source:</b> Microsoft OLE DB Provider for SQL Server<br/><b>Description:</b> Cannot insert the value NULL into column 'limits_id', table 'psa.dbo.clients'; column does not allow nulls. UPDATE fails.
file: C:\Program Files (x86)\Parallels\Plesk\admin\plib\common_func.php3
line: 119
code: -2147352567

Of note:
CPU INTEL Pentium-III Intel64 Family 6 Model 26 Stepping 5 ~2134MHz
Version Parallels Plesk Panel v10.0.1_build20101029.19 os_Windows 2003/2008
OS Microsoft Windows 6.0;build-6002;sp2.0;suite272;product3 (on VMWare ESXi 4.0)

Is it a database updating problem. In the Administrator's Panel, everything seems correct. I do have Customer & Billing Manager installed, but haven't moved any accounts over to it yet. I haven't figured out how to do that yet, but realize it may possibly be causing this issue.

Thanks so much in advance (My brain hurts!),
Joe Peavey
 
It looks like there is Plesk database inconsistency. I strongly suggest you contact support team for database repairing because it is complex procedure.
 
Back
Top