These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Black screen / "The client's local session information is corrupt... "

Author
Malcaz
Omni Paradox Securities
Grand Inquisitors Federation
#1 - 2015-04-04 09:48:16 UTC  |  Edited by: Malcaz
Yesterday Eve Online crashed. I had 3 clients open, but only 2 crashed. For one of them, the account I was using is now inaccessible. Every time I try to login I get this message:

"The client's local session information is corrupt, probably as a result of failed cleanup during a disconnect. Connecting to the server in this state could lead to a rather unpleasant game experience. Please restart the client prior to logging in."

And it returns me to the login screen (if I am using "exefile.exe", if I use the normal launcher I just get a black screen). I have tried to login on different installations of Eve and I get the same message. My other accounts work just fine.

How do I make it so that I can play with this acount again? Maybe I can delete "local session information", how do I do it? I tried running repair.exe and rescache.exe but it didnt change anything.

I also searched the technical support website but couldn't find a mention of the message that I get.

The solution suggested in some very old threads to delete the cache and settings in the application data folder doesn't work either.

edit: I have tried to login on another computer on a different connection and the same thing happened so the problem seems to be server-side.
Malcaz
Omni Paradox Securities
Grand Inquisitors Federation
#2 - 2015-04-04 12:09:58 UTC
The login issue somehow got fixed. But now I can't login to my character. When I click on a character, it does not login, it makes the login sound but just stays at the login screen. I can only login with 2 out of 3 characters, not the one that I want.
Malcaz
Omni Paradox Securities
Grand Inquisitors Federation
#3 - 2015-04-04 17:17:10 UTC
It got fixed by petition.