Well, *that* ain't cool.

[camwyn]

I just got this message from DW:

Your entries have failed to import.
XMLRPC failure: Client error: Invalid text encoding: Cannot display this post. Please see http://www.livejournal.com/support/encodings.bml for more information.

This was failure #1.

Suggestions on how to fix this?

Comments

[vivien]

They are probably overloaded right now: http://dw-maintenance.dreamwidth.org/41520.html

This kind of thing usually happens when LJ breaks/does something stupid.

[camwyn]

Ah, okay. Well, that's cool. I can be patient.

here via latest

[ursamajor]

Hmm. I used to volunteer for LJ Support, and whenever we saw errors that mentioned "invalid text encoding," it was usually from a fellow old-school LJ user whose journal creation predated the switch to Unicode (spring 2002 IIRC).

I suspect that you may have to do some conversions on LJ; it's been a long while since I did it myself, but the FAQ about "Invalid Text Encoding" has some information on how to convert your journal entries and other data to Unicode.

Re: here via latest

[camwyn]

Yeah, I got LJ sometime in.... I dunno, 2000? 2001? I know I posted about the World Trade Center stuff right around when it happened... anyway, yeah, I'll have to fix that. Does this mean that the whole process is being aborted?

Re: here via latest

[silveraspen]

I had something like this happen to me when I imported my main journal to DW, and what ursamajor says above fixed the problem. Once you convert the (usually very few) entries that are glitching the process, the rest of it will hum right along.

ETA: I can't remember for certain, but I think it stops the import at the break point, which may be how I found the troublesome entries to begin with.

Re: here via latest

[camwyn]

I just got told the import succeeded and the earliest post is an import of my first post, so... I'm good. Must've just been DB overload.

Huzzah!

Re: here via latest

[camwyn]

Whoop, my mistake. I got LJ in January of 2002. I know this because I just got told the import succeeded and the earliest post is an import of my first post, so... I'm good. Must've just been DB overload.

[agonistes]

I'm looking at this DW page to try to figure out why my entry import process is aborting. Haven't gotten one of those messages yet, but this may help with yours?

[camwyn]

Yeah, I went to see about changing the encoding. Hopefully that'll help.

[feonixrift.livejournal.com]

DW is suffering an import request flood atm, they are adjusting delays to try to get it all through without swapping the database. Last I heard, they didn't think any imports were dropping, just being heavily delayed. You might want to let them know the extent of the problem has increased.

[feonixrift.livejournal.com]

*swamping the database

[ymfaery]

I was gonna suggest trying again later, but it sounds like the problem sorted itself out, so never mind. ;)