Issue when retrievieng data from server

Issue when retrievieng data from server

Avatar image
Dec 03, 2014
Léo GALLAND wrote
Hello,
I have a big issue when I want to retrieve data from server.
My configuration is :
PS 1.6.0.9 on 1and server dedicated
Connection via PHPMySQL gateway

Everything goes right before, no connection problem or data restore.
Since 2 days I am facing this new issue.
I've deleted the database folder in C:\Users\\AppData\Local\eMagicOne Store Manager for PrestaShop\LocalMySQLData\data several times without succes. This folder seems to be created each times without problem.

The message is at the third step during data connection and restore:
"You have a problem with your database"

Where is the problem and what ca I do to solve it?

Thanks.

Leo
Reply
8 Answers
Avatar image
Dec 03, 2014
Oksana Semenyuk agent wrote
Leo,

Thanks for your question and details

Please try to rename your local database. You can do it in Preferences (F12) -> Bridge connection tab -> Local database name field.
Delete the name you have specified and type any other name there. Latin letters (without caps), no spaces or numbers can be used. You can specify "local_database" as name.

After that use Get Data From Web button (find the button in Preferences) and confirm the action to create local database and retrieve your remote data.

Let us know how it goes.
Avatar image
Dec 04, 2014
Léo GALLAND wrote
Hello Oksana,

thanks for your answer.
I've tried your hints but that don't works anymore.
1- Rename my database to local_database in database name field + OK button
2- I click on button : Create and ...

A new folder called local_database is created, it contains 3 files by retrieved tables (frm, MYD, MYI) + db.opt file
And after I get the error message.

Do you need more information to search ?
Avatar image
Dec 04, 2014
Léo GALLAND wrote
Oksana,

I have found this log file in C:\Users\Léo\AppData\Local\eMagicOne Store Manager for PrestaShop\Logs
I hope this can help you to solve my problem.
Thanks for your help.

Léo
Avatar image
Dec 04, 2014
Andrii Yanosh agent wrote
Hello Leo,

We've checked your logs and it looks like there are a few prefix sets in your database and you have to specify the correct one in Preferences of Store Manager: http://screencast.com/t/zPvSoeVfkA
Autodetect will not work. You can check your PrestaShop database prefix in settings.inc.php file which is located at: store root/config: http://screencast.com/t/iAkmQ8vdDuXC
Avatar image
Dec 05, 2014
Léo GALLAND wrote
Hello Volodymyr,

I've tried your correction but even if I set prefix to bcc_ the issue comes again.
It occurs at he beginning of the database verification step.
The situation becomes urgent because I need your application to be operational for next monday at my customer office.
Question : is there any modification to make on the brifge conf after store-manager update ?
Thanks !!
Leo
Avatar image
Dec 05, 2014
Andrii Yanosh agent wrote
Hello Leo,

Please submit a ticket at: http://support.emagicone.com/submit_ticket and attach your store configuration file*, so we could check the issue more deeply and offer possible solution for you.

*You can save you store configuration file at: Store Manager > Preferences(F12) > Database Connection tab > Store Configuration section > Actions... > Save current configuration: http://screencast.com/t/Hmy0nUDBsHJc

Question : is there any modification to make on the brifge conf after store-manager update ?
A: Please specify more exactly what modification would you like to make.
Avatar image
Dec 08, 2014
Léo GALLAND wrote
Hello Volodymyr ,

I've found the solution for this issue.
It's coming from the bridge.php file at line 42 : $limit_query_size = 8192; //Kb
When I set greater value (ie 65536) that generates the issue !!
What's the use of this parameter and wich values does it accept ?
Thanks.

Léo
Avatar image
Dec 09, 2014
Andrii Yanosh agent wrote
Hello Léo,

$limit_query_size defines the amount of records selected from the table while database dump generation.
In case server closes the connection before the backup has been generated the $limit_query_size should be increased.

And if server turns 501 Internal Server Error or 404 error, probably $limit_query_size may be reduced to 2048 or even 512 Kb.