airbag Posted June 9, 2010 Share Posted June 9, 2010 Hello, I was updating a localhost copy with a refresh of the database. Got this error: Invalid loadTaxZones() SQL query! Any ideas? All files are the same on local and remote, but no site or admin showing, just this error. Link to comment Share on other sites More sharing options...
airbag Posted June 13, 2010 Author Share Posted June 13, 2010 For anyone else with this error....I still dunno whats causing this, but know it is an add on module causing the error, as I reverted locally to a previous copy of the DB and did not get the error.Will report back if I isolate the cause. Link to comment Share on other sites More sharing options...
Juliette Posted July 20, 2010 Share Posted July 20, 2010 Hello Airbag,I'm having the same error but when I'm trying to pass my localhost shop to an internetserverHave you figured out what's that about? Link to comment Share on other sites More sharing options...
Juliette Posted July 20, 2010 Share Posted July 20, 2010 AirBag, I solved the problem. In my case, when I uploaded the tables to the db not all of them uploaded so I had missing information. Uploaded the missing tables and all went finegreetings! Link to comment Share on other sites More sharing options...
danipelon Posted September 7, 2010 Share Posted September 7, 2010 I was having the same error. The problem was that the import expected ANSI data, but my sql export was in UTF-8. I converted the sql file into ANSI and it worked. Link to comment Share on other sites More sharing options...
WWWendy Posted April 1, 2011 Share Posted April 1, 2011 How can I convert my sql file to ansi please? Link to comment Share on other sites More sharing options...
mecjos Posted May 11, 2011 Share Posted May 11, 2011 I got the same error. I tried to upgrade my shop from version 1.3.5 to 1.4.0 but i couldn't then i uploaded my ex files which i got back up and then i got that error. I can't see my site only this error. How can i fix it? Link to comment Share on other sites More sharing options...
i2imedia Posted May 30, 2011 Share Posted May 30, 2011 Please help i'm having the same error! 1 Link to comment Share on other sites More sharing options...
tashigiri Posted August 12, 2011 Share Posted August 12, 2011 I was having the same error. The problem was that the import expected ANSI data, but my sql export was in UTF-8. I converted the sql file into ANSI and it worked. yupz.. thanks a lot.. i change to ANSI and finally success.. How can I convert my sql file to ansi please? there is dropdown box when you want to export or import,, just choice ANSI..^^ Please help i'm having the same error! maybe u can my way above.. Link to comment Share on other sites More sharing options...
dibs223 Posted January 14, 2012 Share Posted January 14, 2012 I have no Ansi in my phpmyadmin is there anything else i can do? or im i missing somthing here! Link to comment Share on other sites More sharing options...
dibs223 Posted January 15, 2012 Share Posted January 15, 2012 can somone help me out plz Im stuck on how to fix thhis problem! Thnaks Link to comment Share on other sites More sharing options...
dornych Posted February 13, 2012 Share Posted February 13, 2012 I've encountered the same error. All i needed to do was regenereate the .htaccess file!! 1 Link to comment Share on other sites More sharing options...
templaries Posted June 4, 2014 Share Posted June 4, 2014 (edited) I have got the same issue, but my tables have got the UTF-8 charset. For example: CREATE TABLE `ps_accessory` ( `id_product_1` int(10) unsigned NOT NULL, `id_product_2` int(10) unsigned NOT NULL, KEY `accessory_product` (`id_product_1`,`id_product_2`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; My script is on ANSI to UTF-8 and if convert the file to ANSI, the diacritics chars will broke down. EDIT: OK. The problem was in the sql dump file, many table was missing. Edited June 9, 2014 by templaries (see edit history) Link to comment Share on other sites More sharing options...
ecentury Posted September 22, 2017 Share Posted September 22, 2017 This has happened a few times to me when i am swapping severs, It could just be that the sql import had a timeout because of its size and that database did not get created. If you truncate the following tables first and then export from the old database the sql file should be a lot smaller and then you can import more easily TRUNCATE `ps_guest`;TRUNCATE `ps_connections`;TRUNCATE `ps_connections_source`;TRUNCATE `ps_connections_page`; Link to comment Share on other sites More sharing options...
Recommended Posts