Jump to content
Forums

System Error After Update.


Scarlet Shadow

Recommended Posts

2 minutes ago, Atanee said:

No is not the moonlit soul because my other alts have it and my husband have it in all his character and not have any issue

if its S1 / not upgraded its fine

but if its upgraded you cant log the chars.

Link to comment
Share on other sites

Still...1hour and half and not fixed, they could literally delete that item from few of people that mentioned their chars here and see if that is the issue, or directly run an emergency maint. What a wasted day in EU...already 10 pm and main was from 1 PM..

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Same issue here

 

EU Jinsoyun

Pickcelle - can't login (had a partly upgraded Moonlit Soul in inventory)

Pickis - same as above

 

My other two alts can login just fine, never had a Moonlit Soul on any of those two.

Link to comment
Share on other sites

2 minutes ago, Shîro said:

Still...1hour and half and not fixed, they could literally delete that item from few of people that mentioned their chars here and see if that is the issue, or directly run an emergency maint. What a wasted day in EU...already 10 pm and main was from 1 PM..

actually an emergency maint would be the best solution, that way people are out of the accounts and they can take their time to comb the Database, as this is 100% a Database error, es the Database doesnt know this item anymore and throws an error cuz of that, thats why the Server yeets you as soon you try to log an "infected" Character table.

  • Like 1
  • Thanks 2
Link to comment
Share on other sites

vor 46 Minuten schrieb Hime:

We're checking through to see what the cause is. Can I also get the name and server of the character that can't log in?

Can't login on my WL and Astro, error 300. Both had the Event Soul don't recall what Stage exactly.
WL: lilTaro

AST: Astrotaroro
Server - EU - Jinsoyun
On other Characters i could login.

Link to comment
Share on other sites

2 minutes ago, ThunderDex said:

actually an emergency maint would be the best solution, that way people are out of the accounts and they can take their time to comb the Database, as this is 100% a Database error, es the Database doesnt know this item anymore and throws an error cuz of that, thats why the Server yeets you as soon you try to log an "infected" Character table.

actually if that was my DB (if i was responsible for that DB) i would call an emergency maint and fix this asap, just delete the entries of that item. then again im guessing that i know more about DBs than their team, as i dont need any tools if its an SQL DB.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...