Fatal error upon update 1.4.0: “Specified key was too long”

  • Resolved BBQBrian

    (@bbqbrian)


    3 years, 3 months ago

    Hello All,

    I went to update Google Listing and Ads today to 1.4.0 and experienced a fatal error. The error logs on the server indicated “Specified key was too long; max key length is 767 bytes”. I am running PHP 7.3, Mariadb 10.1. I see this is a common issue however in this instance for me, it is associated with the update to version 1.4.0. Can anyone help me troubleshoot? or provide a fix?

    Thanks

    Brian

Viewing 3 replies - 1 through 3 (of 3 total)
  • Zach H

    (@zhollenbeak)

    Hi @bbqbrian

    Thanks for reaching out to the Forums for support on this error message.
    >“Specified key was too long; max key length is 767 bytes

    I’ve searched for any other reports of this and do find some instances of this error, but not specific the the Google Listings and Ads plugin.

    This article: https://stackoverflow.com/questions/1814532/mysql-error-1071-specified-key-was-too-long-max-key-length-is-767-bytes
    indicates that the problem is with the database schema that doesn’t support InnoDB MySQL 5.6.

    If that isn’t helpful, Please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.

    Please include a link to this forum thread, so that we can keep track of what’s already been done.

    We will be able to help you further there.

    Thread Starter BBQBrian

    (@bbqbrian)

    Hi Zach,

    I saw that article before I posted. There’s many different solutions in that thread ranging from simple “change this” to complete reconfiguration of db tables with export/import steps amongst all of it. That is why I hesitated.

    A completely different article indicated to switch the character set definitions from “latin” to “utf8” for the db. I tried that and it continued to fault the application.

    I will take a look at more fixes and if need be, contact support.

    Thank you

    Brian

    Zach H

    (@zhollenbeak)

    Hi @bbqbrian

    Thanks for the update! Do let us know if you find a solution.

    I’ll mark this thread as resolved now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error upon update 1.4.0: “Specified key was too long”’ is closed to new replies.