We're moving a WordPress.com blog over to a hosted linux account at GoDaddy. We have 3.3.2 installed at the root and had all plugins except for "WordPress Importer" deactivated. Jetpack could not connect to WordPress.com giving us this error:
Your Jetpack has a glitch. Something went wrong that’s never supposed to happen. Guess you’re just lucky: xml_rpc-32601
Try connecting again. Error Details: The Jetpack server could not communicate with your site's XML-RPC URL. If you have the W3 Total Cache plugin installed, deactivate W3 Total Cache, try to Connect to WordPress.com again, reactivate W3 Total Cache, then clear W3 Total Cache's cache.
We tried ~8 attempts at importing the XML file from the new, hosted WordPress dashboard. The result was an http 500 error:
Note: no helpful information was discovered from this log.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache Server at bikestylespokane.com Port 80
We had about 5 calls to GoDaddy support to help fix the issue...no success. They did what they could on their side.
We also tried importing the XML file directly into the database. We received this error:
There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the
ERROR: Unknown Punctuation String @ 1
SQL: <?xml version="1.0" encoding="UTF-8" ?>
<!-- This is a WordPress eXtended RSS file generated by WordPress as an export of your site. -->...and
...MySQL said: Documentation
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near
'<?xml version="1.0" encoding="UTF-8" ?>
<!<rss v' at line 1
Can anyone help with this SQL/XML syntax error? (The whole XML error discription is available if any wants to look at it...quite lengthy though.)
Barb and I would really appreciate some pointers as to the cause.