• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Plesk Expand + Plesk Reload 7.5.3 .. Little Help

R

ruski

Guest
Hi Folks,

When adding a domain to a client from the Plesk Expand interface (and even via the XML API) I continually get this error in the XML response:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<packet version="1.0.3.11">

<add_use_template>
<result>
<status>error</status>
<errcode>4003</errcode>
<errtext>[Operator] PleskAgent error. (2308) [PleskAgent - DOM_DOMAIN] Error while limits setuping. Domain adding was failed. Error: Unable to update Domain Level User property: domainuser: Column 'perm_id' cannot be null</errtext>
<client_id>1598</client_id>
<server_id>2</server_id>
</result>
</add_use_template>
</packet>

Is this is a bug or am I doing something wrong here?

Example of XML input packet:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.0.3.11">
<add_use_template>
<gen_setup>
<name>testbunny.com</name>
<client_id>1598</client_id>
<status>0</status>
<tmpl_id>2</tmpl_id>
</gen_setup>
<hosting>
<vrt_hst>
<ftp_login>testbunny</ftp_login>
<ftp_password>*******</ftp_password>
<fp_admin_login>tesbunny</fp_admin_login>
<fp_admin_password>*******</fp_admin_password>
</vrt_hst>
</hosting>
</add_use_template>
</packet>

Nothing in my code has changed and the only thing I've done is updated to Plesk Reloaded 7.5.3 (as well as updated Expand to its latest version).

Any help would be appreciated.

Russ.
 
> Column 'perm_id' cannot be null

Looks like your Plesk DB has lost integrity after upgrade.
 
I can't see why that would be the issue, could you elaborate sligthly?

I'm fairly certain Plesk Expand is attempting to insert a NULL value into the perm_id column, which for all intents and purposes, it shouldn't do and thus the Plesk servers are throwing that error in response.

I think this is a problem with the API to be honest, but if you could elaborate more on what you mean by 'lost integrity' I'd be more than willing to try and do some mysql debugging to see what queries are causing the DB/Plesk servers to have a cry about things.

Much appreciated for your response thus far, don't get me wrong :)
 
The other thing I should mention is that if you submit an XML packet via the Plesk Expand API rather than the GUI it throws the same response but the domain actually gets added where as with the GUI it throws the error and the domain does not (I assume this is due to more error checking in the GUI than what I've implemented for my submissions via Perl).
 
I have the same problem on a clean 7.5.3 install.
When is use the PLESK api, I get the error domainuser: Column 'perm_id' cannot be null.
The domain is created, but with the wrong properties.
I'm sure this is a bug or onducumented change is the Plesk API version 7.5.3
 
Anobik, contact Plesk support they've developed a hot fix to resolve this issue.
 
Back
Top