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

PMM mysql charset problems - pls help

N

next-step

Guest
Big problem during migration:

below is the example of migration results
I'm sure its charset problem

In the original server psa database has cp1251 charset.

Please help how can I rectify this?

Code:
Execution of /usr/local/psa/bin/client --update golden -phone +7\ 923\ 333\ 7838 -city  -company \ - -country RU -zip 633009 -state  failed with return code 1.
Stderr is
An error occured during client update: Unable to update client data: cObject::update() failed: Some fields wrong or has inproper values: 'state' = .

  	Execution of /usr/local/psa/bin/client --update golden -country RU -zip 633009 -state  failed with return code 1.
Stderr is
An error occured during client update: Unable to update client data: cObject::update() failed: Some fields wrong or has inproper values: 'state' = .
 
Plesk (starting from 7.x) stores all records in database in UTF8. If you set system locale on both source and destination hosts to unicode - you greatly reduce probability of encoding problems.

Plesk don't like particular 'state' field. It is limited to just 50 characters and your double-encoded 'Новосибирская' have 54 symbols in it...
 
Back
Top