Motion Installation error

By fraser on Dec 16, 2008 at 2:49 PM 5 Vote 0 Votes

I am getting the following error when attempting to install motion (4.25b1):

Error during upgrade: failed to execute statement CREATE INDEX mtasuacacheurltype ON mtasuacache (asuacacheurl,asuacacheaction_type): Specified key was too long. Max key length is 500 at lib/MT/Upgrade.pm line 2553.

I tried both a fresh install and an upgrade. I used a fresh database for the clean install attempts. It is installing in a Mysql environment, Server version: 4.0.27-standard. It is installing to a Cpanel controlled shared hosting environment.

MT 4.23 installed just fine, and upgraded fine from 4.1 as well.

I get the error during the database initialization sequence and it stops dead.

5 Replies

| Add a Reply

Mike T | December 17, 2008 7:18 AM | Reply

Sounds like you two have a similar problem. Your best bet is to file a bug report.
Mike T | December 17, 2008 6:22 PM | Reply

Looks like a known issue with Action Streams 2.0.
Lee | December 23, 2008 4:34 PM | Reply

I have encountered this error in my installation too Fraser. It seems that it is related to the host server. Here is some information regarding it:

http://forums.movabletype.org/2008/12/upgrading-to-trunk-fails.html

Though it seems like a long work around. There should be a resolution to this for the lesser inclined programming people that may be doing these installs at a later date. It would be good to get an official word on the fix still.
Yves Luther | December 29, 2008 4:06 AM | Reply
Same error here:
```
Error during upgrade: failed to execute statement CREATE INDEX 
mt_as_ua_cache_url_type ON mt_as_ua_cache 
(as_ua_cache_url,as_ua_cache_action_type): 
Specified key was too long; max key length 
is 1000 bytes at lib/MT/Upgrade.pm line 2553.
```
Except my max key length was 1000 bytes ;-)

Not funny: I tried both a clean install of 4.25b1 and an update from a clean install of 4.25v1.

I even tried to fix things by hand, but had no fortune.
Lee | December 30, 2008 2:18 AM | Reply

Suffering the same issue. There are some others that experienced the same issue much earlier in December, however they were able to do a very complicated workaround. It would be great to get an official word on what steps we can take in the meantime if there is no fix otherwise planned.