Results 1 to 3 of 3
  1. #1
    Player
    vimzo's Avatar
    Join Date
    Sep 2013
    Posts
    1
    Character
    Imma Dude
    World
    Garuda
    Main Class
    Marauder Lv 33

    Unable to logon after error 90000

    Time: august 31, 2013 around 7:30PM CST
    Frequency: Only once
    World name: Garuda
    Character name: Imma Dude
    NPC name: N/A
    Monster name: N/A
    Class/level: Warrior lv33
    Party or solo: party
    Race: Hyur Midlander Female
    In-game time: Don't remember
    Area and coordinates: Brayfloxs' Longstop

    My party and I were nearing the final boss of Brayfloxs' Longstop when I suddenly disconnected (error 90000). Now, whenever I get to the character select screen it says my character is still in the instance and I cannot login at all (error 1017). I have not been able to login since I got disconnected last evening.

    According to the Lodestone site, the issue has been resolved?....then why am I still not able to logon? It still says I'm in Brayfloxs' Longstop....another day of no FFXIV.../sad
    (0)

  2. #2
    Player
    Lokisama's Avatar
    Join Date
    Sep 2013
    Location
    Gridania
    Posts
    85
    Character
    Loki Fimafeng
    World
    Odin
    Main Class
    Lancer Lv 60
    yeah i was just in contact with the live support chat and they said they are still investigating/working on the problem
    (0)

  3. #3
    Player
    neiris's Avatar
    Join Date
    Jul 2013
    Posts
    65
    Character
    Aya Daisho
    World
    Balmung
    Main Class
    Astrologian Lv 70
    Time: 9.1.13 2:01 PM EST
    Frequency: Only once
    World name: Balmung
    Character name: Nanami Nami
    NPC name: N/A
    Monster name: N/A
    Class/level: WHM 37
    Party or solo: party
    Race: Female Lalafell Dunesfolk
    In-game time: Don't remember
    Area and coordinates: Brayfloxs' Longstop

    Hit enter dungeon, was taking a long time on loading screen and then got 90000. Unable to log in now. This happened yesterday too, same dungeon, and was unable to log in for 4 hours..... This is RIDICULOUS. Getting REAL sick of SE saying they have "resolved the issue" when it clearly is not resolved.
    (0)
    Last edited by neiris; 09-02-2013 at 03:07 AM.