Jump to content

upgrade 1.7.0.6 to 1.7.1 - fault updating database


Recommended Posts

i get following error so reverted back to 1.7.0.6:

 

Updating database schema...,, , [Doctrine\DBAL\Exception\DriverException] , An exception occurred while executing 'ALTER TABLE ps_tab CHANGE class_name class_name VARCHAR(64) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL, CHANGE icon icon VARCHAR(32) NOT NULL': , SQLSTATE[01000]: Warning: 1265 Data truncated for column 'icon' at row 2 , ,, , [Doctrine\DBAL\Driver\PDOException] , SQLSTATE[01000]: Warning: 1265 Data truncated for column 'icon' at row 2 , ,, , [PDOException] , SQLSTATE[01000]: Warning: 1265 Data truncated for column 'icon' at row 2 , ,,doctrine:schema:update [--complete] [--dump-sql] [-f|--force] [--em [EM]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-s|--shell] [--process-isolation] [-e|--env ENV] [--no-debug] [--] 

 

,,

 

 

any clues?

Edited by sennevb (see edit history)
  • Like 1
Link to comment
Share on other sites

It is complaining that you have a record in the ps_tab database table, whose character length is too long.

 

If I had to guess, you have a module installed that added a new back office tab, and the name of the icon for that tab exceeds 32 characters.  Use phpmyadmin to review the existing records and locate the record causing the issue.

 

Once you locate the record, then note if the module column is null or not

  • Like 1
Link to comment
Share on other sites

Ours turned out to be a permission to do with INDEX in the database, adding that for the dbuser fixed it and the upgrade completed.

 

It was not needed for the 1.7.0.4 > 1.7.0.5 > 1.7.0.6 upgrades...

Link to comment
Share on other sites

Ours turned out to be a permission to do with INDEX in the database, adding that for the dbuser fixed it and the upgrade completed.

 

It was not needed for the 1.7.0.4 > 1.7.0.5 > 1.7.0.6 upgrades...

To avoid confusion, you likely had a different issue.  The issue in the OP is very specific

Link to comment
Share on other sites

It is complaining that you have a record in the ps_tab database table, whose character length is too long.

 

If I had to guess, you have a module installed that added a new back office tab, and the name of the icon for that tab exceeds 32 characters.  Use phpmyadmin to review the existing records and locate the record causing the issue.

 

Once you locate the record, then note if the module column is null or not

will check this out, keep you posted!

 

edit: all records are smaller then 64 chars , where do you get 32 chars??

 

only thing longer then 32 chars is 

AdminParentCustomerPreferences  

 

Edited by sennevb (see edit history)
Link to comment
Share on other sites

Ours turned out to be a permission to do with INDEX in the database, adding that for the dbuser fixed it and the upgrade completed.

 

It was not needed for the 1.7.0.4 > 1.7.0.5 > 1.7.0.6 upgrades...

Can you exactly tell me what you did??

Link to comment
Share on other sites

Managed to rollback to 1.7.0.6.


 


Howto Restore back to 1.7.0.6 Manually :


1. Download complete PS root folder. 


2. Delete all files in root


3. Upload all files from /admin/autoupgrade/backup/ Last Backup Folder to root


4. Delete all tables in DB


5. Run the DB Backups from /admin/autoupgrade/backup/ folder as script in phpMyAdmin 


6. Go back to your uploaded files and ensure to change recursively files & folder permissions. All files to have 644 permissions & all folders to have 755 permissions.


7. Login to your BO & remove 1-Click Upgrade Module.


8. Download the latest 1-Click Upgrade Module from PS Addons Website and uploaded.


 


You are set with your 1.7.0.6 again.


 


And also managed to upgrade to PS v1.7.1.0 using 1-Click Upgrade v2.0.8 without any problems. 


 


Hope this helps.


Link to comment
Share on other sites

 

will check this out, keep you posted!

 

edit: all records are smaller then 64 chars , where do you get 32 chars??

 

only thing longer then 32 chars is 

AdminParentCustomerPreferences  

 

The error specifically states that it failed to update the icon column to a varchar(32), which is 32 characters

CHANGE icon icon VARCHAR(32) NOT NULL
Link to comment
Share on other sites

Hello,


 


we have the same problem.


we would like to upgrade our prestashop from version 1.7.0.6 to version 1.7.1.


 


But we can not, because we have this error messege:


Activity log:

10255 files left to upgrade.

[Ajax / Server Error for action upgradeFiles] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "

--------

Directory /vendor/composer/ca-bundle/res already exists.

Copied /vendor/composer/ca-bundle/res/cacert.pem.

10255 files left to upgrade.

 

Do you know where could be the the problem ?

 

Thanks & Regards

Link to comment
Share on other sites

  • 3 weeks later...

Hi, 

 

I had exactly the same problem today (from 1.7.0.6 to 1.7.1) with 1-click-upgrade, as quoted below, with exactly the same error message:

 

 

 

Activity log:
10255 files left to upgrade.
[Ajax / Server Error for action upgradeFiles] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "
--------
 

 

The restore function (button) didn't work, only resulting in a new error line, reproduceable (that one I've forgotten to note). The site access was broken then, had to restore manually the database and the files. And I can't figure out how you resolved that issue, without ending up in a loop, restoring manualy again and again...

 

Any hint will be really appreciated, thank you for your time. 

Link to comment
Share on other sites

its possible that the upgrade process takes too long and times out, which could be a server configuration issue, especially if you are on a shared hosting server.

 

I would suggest you take your own backups, and disable both the database and image backups during the upgrade.  It is not necessary, and could take a long time depending on the size of the database, and how many images you have.

Link to comment
Share on other sites

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...