Is there no one that can help? I’m betting it’s gonna be a complete re build of the site. Next time I will make sure I use a plugin that has support, and works properly. Reading the endless forum ….this plugin has a great deal of problems. I don’t fault the developer. My fault for using it.
Hi there –
I’m sorry I missed your post. I’ve had trouble receiving all new topics since the changes to the forums a little while back, though I do try to check a few times a week regardless.
A problem in the syntax is usually a difference between how a database backup is saved on one server and how it is read on another server. Usually it’s as simple as a different option but it sometimes comes down to very old phpmyadmin installations being used on some hosts.
It looks like your previous backup had different header information included with the file, information the new server doesn’t need/want. So it triggers this error. The error spells out what is wrong, though – so it would be a fairly easy thing to open the SQL file and look on line 1 for the @ that is there that it’s throwing a fit about. It sounds like there’s a double @maybe.
One easy solution would be to have your new host install the old database file for you via the command line, if they can. This seems to circumvent the issue much of the time in my own experiments with this problem.
Unfortunately some of the much older phpmyadmin installations or MySQL installations tend to export backups with some issues.
Again, I’m sorry I wasn’t able to respond quickly and for the trouble you’re having. Best of luck to you moving forward.
Kat
