Using sql import and getting session or cookie problems

[petednz]

Getting this message after putting a 'select' query in as the sql import option.

Sorry. A non-recoverable error has occurred.

We can't load the requested web page. This page requires cookies to be enabled in your browser settings. Please check this setting and enable cookies (if they are not enabled). Then try again. If this error persists, contact the site adminstrator for assistance.

Error type: Could not find a valid key.

We have checked the following

drupal uid 0 exists

url is consistent between drupal and civicrm.

Any other suggestions?

[menasor2782]

Hello: Did you figure out this problem. I'm having the same, but with Joomla.

[Eileen]

Not yet, we have just come back to it.

I note that if in your first attempt you reference a civi-table e.g. select * from civicrm_contact it does *work* but if you use the back button to change it over it doesn't

Also, if you select the drupal users table it seems to work.

[Eileen]

OK, I haven't figured out a patch for this. But I have managed to find out how to replicate it and how to work around it.

It falls over if there is an upper case character in the table name. I really can't see how this is happening in the code but I presume it is including the table name in the session calculation somehow & the values for a lower case and an upper case error are different

So, I get the error if I do
"Select * from Individuals"

But if I rename the table to "ndviduals" then
"Select * from ndviduals"

works

I can't see what's happening in the code here but renaming the table is a work around & I will log a JIRA.

(NB spaces in table names are fine as long as you use backticks `)

[Eileen]

Hang on , there is something more to this. The tables that are failing have yucky ms access fields which seem to be the problem (and they just happen to be capitalised)

[Eileen]

OK, so the tables I am having problems with came from an MS Access database. I used an imported tool & it brought across the system tables including

S_Lineage
which is of type - LONGBlob but also seems to have attribute 'Binary' - removing this field fixes it. (it could be that a better error message would make all the difference here)

[Eileen]

And a bit more - it's not even the structure - it's the data. I set all data for that field to null & the imports worked