Spark stops working while opening a dialogue with one of the contacts

Spark Spark Support
1

On one of the PCs when you try to create a dialogue with one of the User Spark stops working. It is necessary to stop the process Spark.exe and run Spark again. When you open a dialogue by other users this does not happen. On the other PC conversations with all users opened without problems.

мар 22, 2016 4:14:03 PM org.jivesoftware.spark.util.log.Log error

SEVERE:

No response from the server.:

at org.jivesoftware.smackx.PrivateDataManager.getPrivateData(PrivateDataManager.ja va:209)

at org.jivesoftware.sparkimpl.plugin.scratchpad.Tasks.getTaskList(Tasks.java:205)

at org.jivesoftware.sparkimpl.plugin.scratchpad.TaskNotification$2.run(TaskNotific ation.java:73)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

мар 22, 2016 4:37:21 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

мар 22, 2016 4:38:47 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

мар 22, 2016 4:40:22 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

мар 22, 2016 4:41:11 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

мар 22, 2016 5:00:44 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

мар 22, 2016 5:06:36 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

мар 22, 2016 5:08:40 PM org.jivesoftware.spark.util.log.Log error

SEVERE: Dictionary not found

2

This is usually caused by a corrupted history file with that contact. If you don’t need chat history with that contact, you can just delete that file (or rename to just keep it, Spark will create new one). C:\Users\username\AppData\Roaming\Spark\user\user@server\transcripts\

It will be probably contactsusername@server.xml But you can also try removing/renaming contactsusername@server_current.xml