Downloaded the latest ljarchive program, ran it, right in the middle of the comment index loading it came out with this monstrosity:
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.ConnectStream.Read(Byte buffer, Int32 offset, Int32 size)
at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
at EF.ljArchive.Engine.Sync.ExportCommentsMeta(OptionsRow or, ILJServer iLJ, SessionGenerateResponse sgr, Int32& serverMaxID, UserMapCollection umc)
Wondering if the host decided it was taking too long and blew up or something. Personally I would LIKE to be able to archive my LJ; I do have older backups, maybe it could be set to a more recent string or something?
I see a lot of posts like this. I see no indication whatsoever that anybody knows what to do about them, intends to do anything about them, or has done anything about them. Do any of the folks involved with the construction of this program read this community?