Chat logs are getting corrupted (after the upgrade to 2.6.3)

Description

However, this is only the case for about half of our XML Transcript files. The other half do not have this missing "e>" but instead have problems were some of the "<to>name@server/Spark 2.6.3</to>" is missing.

They look like:

"ver/Spark 2.6.3</to>"

so they are missing the login name and part of the server name. Not good.

Fix this by making the syntax correct... so in this case:

"<to>name@server/Spark 2.6.3</to>"

Save, and then ur history should be back for this effected transcript file.

Hope this helps somebody! Not sure why Spark had this many problems with the 2.6.3 upgrade... seems like it was rushed perhaps.

NOTE: also, wanted to clarify for any future readers, that you are only concerned about the files labeled:

name@server.xml – not the name@server_current.xml files.

Environment

None

is related to

Activity

Show:

wroot March 27, 2014 at 3:11 PM

Closing for now, as 2.6.3 is old and probably this issue won't come up often now.

Cannot Reproduce

Details

Priority

Assignee

Reporter

Affects versions

Fix versions

Components

Ignite Forum URL

Created October 11, 2011 at 7:35 AM
Updated October 28, 2020 at 1:44 PM
Resolved March 27, 2014 at 3:12 PM