when i activate views ui, i get this error:

PDOException: SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=': SELECT s.uid, c.updated FROM {ctools_object_cache} c INNER JOIN {sessions} s ON c.sid = s.sid WHERE s.sid <> :session_id AND c.obj = :obj AND c.name = :name ORDER BY c.updated ASC; Array ( [:session_id] => FBtJ0GWSYKA2lyf6MUQUbgjHuE6luu22ZL7n2Jl5vTg [:obj] => view [:name] => comments_recent ) in ctools_object_cache_test() (line 115 of /home/ligaph/public_html/sites/all/modules/ctools/includes/object-cache.inc).

i use drush to turn off ctools which also turns off views, and it works again. i have the ff. modules:

Name Installed version Proposed version Status
Administration menu 7.x-3.0-rc1 7.x-3.0-rc1 Up to date
Backup and Migrate 7.x-2.1 7.x-2.1 Up to date
Drupal core 7.0 7.0 Up to date
Content Construction Kit (CCK) 7.x-2.x-dev 7.x-2.x-dev Up to date
Date 7.x-1.0-alpha2 7.x-1.0-alpha2 Up to date
Fivestar 7.x-2.x-dev 7.x-2.x-dev Up to date
ImageCache Actions 7.x-0.0 7.x-0.0 Up to date
ImageCache Profiles 7.x-1.0-rc2 7.x-1.0-rc2 Up to date
Job Scheduler 7.x-2.0-alpha2 7.x-2.0-alpha2 Up to date
LoginToboggan 7.x-1.1 7.x-1.1 Up to date
Mollom 7.x-1.0 7.x-1.0 Up to date
Pathauto 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Taxonomy CSV import/export 7.x-5.6 7.x-5.6 Up to date
Taxonomy Manager 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Token 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Views 7.x-3.0-alpha1 7.x-3.0-alpha1 Up to date
Voting API 7.x-2.4 7.x-2.4 Up to date
Wysiwyg 7.x-2.0 7.x-2.0 Up to date
Sky 7.x-1.6 7.x-1.6 Up to date

help appreciated thank you
Gary

Comments

ghmercado’s picture

ghmercado commented

ive tried removing / reinstalling ctools and views and i still get error. I have a nearly identical d7 installation with same details on same host but that gets no error.

bojanz’s picture

bojanz commented

The problem is in your database.
Drupal usually detects which collation is used in the database and uses the correct one, but if not all tables have the same collation (such as in your case), the system gets confused.
Not sure how you can fix it, try searching around on drupal.org since this is a generic drupal issue. Post back when you find your solution.

(Also, upgrade to 7.x-3.x-dev regardless of this. alpha1 is ancient)

fafamonge’s picture

fafamonge commented

I have the same problem. I already change the collation for all tables in mysql and the error persist.

Do you have any idea how to solve it?

fafamonge’s picture

fafamonge commented

I solve this using the bobburns post in http://drupal.org/node/251938

bojanz’s picture

bojanz commented
Status: Active » Fixed

Good to know.

ghmercado’s picture

ghmercado commented

solution mentioned in #4 worked for me, link here. many thanks! http://drupal.org/node/251938#comment-3871030

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

rflet’s picture

rflet commented

The solution in post #4 didn't work for me for some reason. But I found another solution an outside forum which told me to open PHPmyAdmin in CPanel, find 'ctools_object_cache' and manually change the collations from utf8_general_ci to utf_unicode_ci.

And when you go back and look at the message "Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=': SELECT s.uid, c.updated FROM {ctools_object_cache}" it seems to sort of make sense... in a robot sort of way.

guypaddock’s picture

guypaddock commented
Status: Closed (fixed) » Active

Sorry, but... this isn't exactly fixed. I saw this just now when I enabled a feature that installed a view with Views 3.3. I'd like to know how Views caused the table to suddenly just got the wrong collation?

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed".

If there is new information, please re-open the issue.

--
This issue was edited with the help of Issue Helper

Status: Fixed » Closed (fixed)
Issue tags: -error, -views ui

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +error, +views ui

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.