Log in

Or connect using:

Request #1364544

Account type:Permanent Account
LiveJournal:username: khyron
style: (S2) core: public, i18n: none, i18nc: none, layout: public, theme: public, user: custom,
email validated?yes
cluster: Hambone (#5); data version : 8
scheme: horizon; language: en_LJ
underage? no
Is JavaScript enabled:(unknown)
Request sent from Beta:
Photo hosting migration:done
Support category:Entries [previous|next]
Time posted:Sat, 20 Aug 2011 02:01:40 GMT (3 years ago)
Status:closed (10 points to coffeechica)
Summary:importing livejournal to wordpress.com results in XML-RPC error
Original Request:
I've been trying to copy the contents of my LJ into a wordpress.com account, and I've come across a problem that may be an LJ issue and not a WP issue. It involves using the wordpress.com LJ import feature, which now contacts LJ via the API (not to be confused with the old method of using exported XML files).

When I attempt the import, wordpress.com reports this XML-RPC error:

couldn't retrieve anum for entry at /home/lj/cgi-bin/ljprotocol.pl line 3952

Not sure what can be done about this? If it's in fact a problem with the code here at LJ, can anyone take a look and figure out what's going wrong? Thanks.
Diagnostics: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20100101 Firefox/6.0
khyronkhyron - Quamzin Kravshera
Comment (#5214646)
Posted: Sat, 20 Aug 2011 17:00:16 GMT (3 years ago)

I've been able to verify that this same error is also currently being reported from the utility ljdump, when used on the command line with my Mac (running 10.6.8 with Python 2.6.1, r261:67515). The script is able to contact LJ and authenticate but then immediately drops out with the error:

couldn't retrieve anum for entry at /home/lj/cgi-bin/ljprotocol.pl line 3952

khyronkhyron - Quamzin Kravshera
Comment (#5217364)
Posted: Sun, 21 Aug 2011 20:02:06 GMT (3 years ago)

I received some advice from this community post...


...that this "missing anum" problem could be related to a single journal item not having been saved properly. In an effort to troubleshoot further, I downloaded my entire journal month-by-month via the LJ export page into XML files. Unfortunately, I was not able to reproduce any error in that manner, so either the presumption was false or if there is any "bad" data in my journal somewhere perhaps it is within a comment?

Not sure how to proceed further.

khyronkhyron - Quamzin Kravshera
Comment (#5220388)
Posted: Mon, 22 Aug 2011 20:49:36 GMT (3 years ago)

Here's another user's ticket reporting the same problem...


Here's another user reporting the same problem on their journal...


markfmarkf - Mark
Answer (#5220568)
Posted: Mon, 22 Aug 2011 22:19:03 GMT (3 years ago)

Thank you for your report. Your request has been forwarded to our engineering team, who will work to investigate the cause of this problem. They may also reply to this request to ask you for troubleshooting assistance.

Due to the complexity of the issues involved, it may take a longer time to receive a response; if you have any additional questions or comments to add, please feel free to reply to this request. Your patience is appreciated during this time, and I apologize for the inconvenience this problem is causing you.

khyronkhyron - Quamzin Kravshera
Comment (#5222064)
Posted: Tue, 23 Aug 2011 15:47:12 GMT (3 years ago)

Here is yet another user reporting the same issue:


khyronkhyron - Quamzin Kravshera
Comment (#5225414)
Posted: Wed, 24 Aug 2011 19:06:28 GMT (3 years ago)

These discussions seem to relate to the same or a very similar issue...failures involving the export of journal entries and comments, starting very recently (possibly with the latest LJ release):



khyronkhyron - Quamzin Kravshera
Comment (#5228334)
Posted: Thu, 25 Aug 2011 20:22:03 GMT (3 years ago)

This code change between lines 3913 and 3915, where it appears "anum" has been added to a query which previously did not request it, may bear attention. If this proves helpful please thank user av8rmike, who just reminded me to mention this.


coffeechicacoffeechica - Carrie: she tampered in God's domain
Answer (#5230286)
Posted: Fri, 26 Aug 2011 18:27:29 GMT (3 years ago)

Thank you for your extra information. I have passed this information on to developers. (This problem has actually been happening since before that specific change happened, but this tip allowed us to find an earlier change that probably did trigger this influx of problems at this time.) I am sorry that we don't have a timeline on when this will be resolved, but continuing to watch lj_releases will get you the most updated information on when bugfixes are live.

ariearie - Arie
Answer (#5238570)
Posted: Tue, 30 Aug 2011 18:25:00 GMT (3 years ago)

Thank you for your patience while we've been working on this issue. Our engineering team is still investigating this, and have asked for more information.

We've added some information to the error output to help us identify this problem. Please try using LJ Archive again, and respond back with the full text of the error message you're now getting.

khyronkhyron - Quamzin Kravshera
Comment (#5238648)
Posted: Tue, 30 Aug 2011 18:43:56 GMT (3 years ago)

I continue to get the same error, using the wordpress.com importer or ljdump:

couldn't retrieve anum for entry at /home/lj/cgi-bin/ljprotocol.pl line 3976

I can install ljarchive and try that as well, I need to boot into Windows. I'll report back as soon as I've tried ljarchive.

khyronkhyron - Quamzin Kravshera
Comment (#5238692)
Posted: Tue, 30 Aug 2011 19:04:57 GMT (3 years ago)

Okay I set up a Windows VM and installed .NET 3.5 and ljarchive into it, and ran ljarchive. It immediately reported the following error, and the portion coming back from LJ appears to look the same (including all the other .NET stuff too in case it's useful).

ljArchive Error: CookComputing.XmlRpc.XmlRpcFaultException: Server returned a fault (Server): couldn't retrieve anum for entry at /home/lj/cgi-bin/ljprotocol.pl line 3976

      at CookComputing.XmlRpc.XmlRpcSerializer.DeserializeResponse(TextReader trdr, Type returnType)
      at CookComputing.XmlRpc.XmlRpcClientProtocol.ReadResponse(XmlRpcRequest req, WebResponse webResp, Stream respStm, Type returnType)
      at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
      at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
      at XmlRpcProxy59b5d49a-e2ba-418c-bb22-898010057554.SyncItems(SyncItemsParams )
      at EF.ljArchive.Engine.Sync.SyncItems(OptionsRow or, ILJServer iLJ, SyncItemCollection& sic, SyncItemCollection& deletedsic, DateTime& lastSync)
      at EF.ljArchive.Engine.Sync.ThreadStart()

khyronkhyron - Quamzin Kravshera
Comment (#5238696)
Posted: Tue, 30 Aug 2011 19:06:17 GMT (3 years ago)

In case it's helpful, I've been keeping a running tally of support tickets which appear to reference this same issue. If you need additional testers to report whether their errors are including any new content that may help with troubleshooting you may want to contact these users as well:


coffeechicacoffeechica - Carrie: she tampered in God's domain
Answer (#5239050)
Posted: Tue, 30 Aug 2011 22:03:34 GMT (3 years ago)

Thank you for your report, and I apologize for the inconvenience. I have sent this output to our engineering team, and thank you for your continuing patience while they investigate and resolve the problem.

We have indeed contacted a number of those users for more information. We have an internal tagging system that allows us to call up requests that are all affected by the same issue, and everyone on that list is covered. Thank you for your offer to help!

Go to: previous open request,next open request
Back to the list of open requests.
Back to the support area.

Welcome to the new LiveJournal

Some changes have been made to LiveJournal, and we hope you enjoy them! As we continue to improve the site on a daily basis to make your experience here better and faster, we would greatly appreciate your feedback about these changes. Please let us know what we can do for you!

Send feedback

Switch back to old version

LiveJournal Feedback

See a bug? Let us know! Here you can also share your thoughts and ideas about updates to LiveJournal

Your request has been filed. You can track the progress of your request at:
If you have any other questions or comments, you can add them to that request at any time.

Send another report Close feedback form

If you're a LiveJournal user, you will be logged in after submitting your request.

(optional, if you're a LiveJournal user only)

(optional, if you're a LiveJournal user only)

(not shown to the public)

If you have a billing inquiry, please go here to submit your question.

Provide a link to the page where you are experiencing the error

Do not include any sensitive information, such as your password or phone number. No HTML allowed.

If you can't pass the human test, email your inquiry to: support@livejournal.com

Welcome to LiveJournal

Create an account