1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Inserted data is exist. Client with login name 'xxx' already exists

Discussion in 'Plesk Expand 2.2 Troubleshooting Issues' started by eugenevdm, Oct 24, 2007.

  1. eugenevdm

    eugenevdm Silver Pleskian

    30
    68%
    Joined:
    Nov 11, 2003
    Messages:
    611
    Likes Received:
    0
    We're having this perpetual problem:

    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <packet version="2.2.1.27">
    <set>
    <result>
    <status>error</status>
    <errcode>4003</errcode>
    <errtext>[Operator] PleskAgent error. Error Plesk server #12 answer for client #1158: (1007) [PleskAgent - GENERAL] inserted data is exist. Client with login name 'yyy' already exists..</errtext>
    <id>1158</id>
    <server_id>12</server_id>
    <plesk_client_id>549</plesk_client_id>
    <login>yyy</login>
    </result>
    </set>
    </packet>
    Action Input
    <?xml version="1.0"?>
    <packet version="2.2.1.27">
    <set>
    <filter>
    <id>1158</id>
    </filter>
    <values>
    <gen_info>
    <cname>yyy ccc</cname>
    <pname>aaa bbb</pname>
    <login>yyy</login>
    <phone>(224) 4816000</phone>
    <fax></fax>
    <email>amoottar@kaasdfex.com</email>
    <address></address>
    <city></city>
    <state></state>
    <pcode></pcode>
    <country>ZA</country>
    </gen_info>
    </values>
    </set>
    </packet>
    Advanced: Taskman Output
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <packet version="0.1.1.0">
    <result>
    <status>error</status>
    <errtxt>Action executed with errors</errtxt>
    </result>
    </packet>

    The interpretation is simple "The client is already supposed to be there.". Yes the client is there but only one client (the client we are trying to change) has this login name. As a workaround we change the login name to something else, proceed (without error), and then we change the username back to the original value. Is anyone else experiencing this problem? It doesn't look like it's always happening, i.e. it only happens sometimes.
     
  2. girin

    girin Guest

    0
     
    Hi!

    This is a strange reaction of a Plesk server to the command Client/Set with unchanged login name in the protocol 1.5.1.0.

    I decreased the protocol version to avoid this issue:
    Code:
    mysql>delete from plesk_server_api_version where server_id=X and api_version='1.5.1.0';
    
    But if you will follow the same way, you will lose the central backup functionality in the Expand for this Plesk server.

    And another thing, the protocol version will be restored back to 1.5.1.0 when the server info will be manually reloaded for the Plesk server.
     
  3. eugenevdm

    eugenevdm Silver Pleskian

    30
    68%
    Joined:
    Nov 11, 2003
    Messages:
    611
    Likes Received:
    0
    Thank you girin!

    I thought I was going mad. I confirm this problem only happens on our Linux servers, or our Windows boxes there is no problem.

    kind regards,
     
Loading...