Forum Settings
       
Reply To Thread

Error 90000 STILL keeping me from progressingFollow

#1 Aug 19 2013 at 1:14 AM Rating: Decent
*
130 posts
Despite the fact that the servers are up and I havent been able to play my character for a day and a half, I still cant continue on with the main quest line... just tried accepting the same quest that DCd me last time and it's still DCing me and giving me the error 90000. So apparently they fixed 3102 but not this one :(
#2 Aug 19 2013 at 1:17 AM Rating: Good
**
424 posts
When did the servers come back online?
#3 Aug 19 2013 at 1:25 AM Rating: Decent
*
130 posts
not long ago, maybe 10 - 15 min?
#4 Aug 19 2013 at 1:40 AM Rating: Good
**
424 posts
I'm still getting the same error 90000 ****. One error down, one to go? Smiley: lol
#5 Aug 19 2013 at 1:48 AM Rating: Decent
*
123 posts
Worst open beta I've ever participated in. Logged on and noticed I still had that red triangle next to my name, logged back out at the inn.

Edited, Aug 19th 2013 3:49am by SuikodenXXX
#6 Aug 19 2013 at 1:51 AM Rating: Decent
****
4,175 posts
Wait, wut? They brought the servers down to fix the 3102 and 90000 issues and didn't actually fix them? You gotta be kidding me...
____________________________
Rinsui wrote:
Only hips + boobs all day and hips + boobs all over my icecream

HaibaneRenmei wrote:
30 bucks is almost free

cocodojo wrote:
Its personal preference and all, but yes we need to educate WoW players that this is OUR game, these are Characters and not Toons. Time to beat that into them one at a time.
#7 Aug 19 2013 at 2:16 AM Rating: Good
*
130 posts
FilthMcNasty wrote:
Wait, wut? They brought the servers down to fix the 3102 and 90000 issues and didn't actually fix them? You gotta be kidding me...



I think they brought them down to mainly fix the 3102... i just logged out for the night (and obv until early release) because I literally cant do anything with that 90000 error. Got my Pug to 15 early yesterday and planned on lvling LNC straight through but cant even finish the quest line to unlock the airship to get to Gridania in order to unlock the lancer, also cant get cooking or fishing (the only crafts im interested in) or CNJ (for cure/protect), or Archer (for a couple abilities). So this bug completely screwed my whole beta experience lol... oh well I just hope when I log back in for early access that its fixed.

Edited, Aug 19th 2013 4:17am by Phoenix904
#8 Aug 19 2013 at 2:36 AM Rating: Decent
****
4,175 posts
Phoenix904 wrote:
FilthMcNasty wrote:
Wait, wut? They brought the servers down to fix the 3102 and 90000 issues and didn't actually fix them? You gotta be kidding me...



I think they brought them down to mainly fix the 3102... i just logged out for the night (and obv until early release) because I literally cant do anything with that 90000 error. Got my Pug to 15 early yesterday and planned on lvling LNC straight through but cant even finish the quest line to unlock the airship to get to Gridania in order to unlock the lancer, also cant get cooking or fishing (the only crafts im interested in) or CNJ (for cure/protect), or Archer (for a couple abilities). So this bug completely screwed my whole beta experience lol... oh well I just hope when I log back in for early access that its fixed.


I'm having trouble trying to understand why they wouldn't resolve both issues. That kinda defeats the purpose(as well as all the 'this is what beta is for' arguments) if they just clear people to log into the game, but don't actually test to make sure that isn't happening again. That on top of not fixing the 90000 issue.

____________________________
Rinsui wrote:
Only hips + boobs all day and hips + boobs all over my icecream

HaibaneRenmei wrote:
30 bucks is almost free

cocodojo wrote:
Its personal preference and all, but yes we need to educate WoW players that this is OUR game, these are Characters and not Toons. Time to beat that into them one at a time.
#9 Aug 19 2013 at 3:08 AM Rating: Good
**
424 posts
FilthMcNasty wrote:
Phoenix904 wrote:
FilthMcNasty wrote:
Wait, wut? They brought the servers down to fix the 3102 and 90000 issues and didn't actually fix them? You gotta be kidding me...



I think they brought them down to mainly fix the 3102... i just logged out for the night (and obv until early release) because I literally cant do anything with that 90000 error. Got my Pug to 15 early yesterday and planned on lvling LNC straight through but cant even finish the quest line to unlock the airship to get to Gridania in order to unlock the lancer, also cant get cooking or fishing (the only crafts im interested in) or CNJ (for cure/protect), or Archer (for a couple abilities). So this bug completely screwed my whole beta experience lol... oh well I just hope when I log back in for early access that its fixed.


I'm having trouble trying to understand why they wouldn't resolve both issues. That kinda defeats the purpose(as well as all the 'this is what beta is for' arguments) if they just clear people to log into the game, but don't actually test to make sure that isn't happening again. That on top of not fixing the 90000 issue.



Maybe they didn't have enough info on 90k without first clearing up what might have been the easier of the two issues to fix. Now that they have 3102 fixed, it might lead them to the info they are missing to fix the problem. Sometimes you can't solve for x without first solving for y.
#10 Aug 19 2013 at 4:31 AM Rating: Decent
****
4,175 posts
supermegazeke wrote:
FilthMcNasty wrote:
Phoenix904 wrote:
FilthMcNasty wrote:
Wait, wut? They brought the servers down to fix the 3102 and 90000 issues and didn't actually fix them? You gotta be kidding me...



I think they brought them down to mainly fix the 3102... i just logged out for the night (and obv until early release) because I literally cant do anything with that 90000 error. Got my Pug to 15 early yesterday and planned on lvling LNC straight through but cant even finish the quest line to unlock the airship to get to Gridania in order to unlock the lancer, also cant get cooking or fishing (the only crafts im interested in) or CNJ (for cure/protect), or Archer (for a couple abilities). So this bug completely screwed my whole beta experience lol... oh well I just hope when I log back in for early access that its fixed.


I'm having trouble trying to understand why they wouldn't resolve both issues. That kinda defeats the purpose(as well as all the 'this is what beta is for' arguments) if they just clear people to log into the game, but don't actually test to make sure that isn't happening again. That on top of not fixing the 90000 issue.



Maybe they didn't have enough info on 90k without first clearing up what might have been the easier of the two issues to fix. Now that they have 3102 fixed, it might lead them to the info they are missing to fix the problem. Sometimes you can't solve for x without first solving for y.

I meant resolving both issues before bringing testing to a close. It's great that they extended the beta, but it doesn't run through peak server times. Wouldn't it make more sense to at least run the servers through prime time and make sure they actually fixed it? It would also seem logical to keep servers up until they can bust the 90000 issue as well. It would do a lot for people's confidence in the game if they did anyway.
____________________________
Rinsui wrote:
Only hips + boobs all day and hips + boobs all over my icecream

HaibaneRenmei wrote:
30 bucks is almost free

cocodojo wrote:
Its personal preference and all, but yes we need to educate WoW players that this is OUR game, these are Characters and not Toons. Time to beat that into them one at a time.
#11 Aug 19 2013 at 5:59 AM Rating: Good
***
1,674 posts
I'll see your Error 90000 and raise you the evolved form of it: client crashing.

I posted about this before (link), but basically I tried progressing and doing stuff, non-instanced stuff, while still under the effect of Error 90000. Well, it seems to have pissed the lobby or data center or whatever right off, and since logging off and trying to log back in yesterday afternoon, my game crashes like clockwork when I try and enter the lobby/character selection screen.

And worse, I know this is related to character corruption as well. How? Well, for one, I tried a full reinstall and that did nothing. But most damning is that when the NA/EU servers were down, I actually *did* manage to get to the lobby. Was even able to test and make a new character on a JP server for an hour late last night during the emergency maintenance. But once that ended and NA/EU servers became available again? Yep, you guessed it: crash and burn.

I'm seriously scared that this won't be resolved in time for early access, let alone ever, since I've yet to see anyone have a similar evolution of the Error 900000 issue that I am now having. I had a friend who E9'd, and I asked her to basically try and do what I did and see if it caused their game to ***** up like mine did. It didn't.
#12 Aug 19 2013 at 7:36 AM Rating: Decent
Scholar
***
1,732 posts

I posted this in another thread about this error for some people:

This problem may not be SE problem... It is a disconnect issue.. I had it for a while and it turned out to be my wireless... Changed to hardwired and no issue ever with it again.

Another friend had it but his isp is terrible. He took his laptop over by me and had no issues at all.

So basically it may be a problem on your side for some people.

Edited, Aug 19th 2013 9:36am by Nashred
____________________________
FFXI: Nashred
Server: Phoenix

FFXIV : Sir Nashred
server: Ultros
#13 Aug 19 2013 at 8:02 AM Rating: Good
*
65 posts
Nashred wrote:

I posted this in another thread about this error for some people:

This problem may not be SE problem... It is a disconnect issue.. I had it for a while and it turned out to be my wireless... Changed to hardwired and no issue ever with it again.

Another friend had it but his isp is terrible. He took his laptop over by me and had no issues at all.

So basically it may be a problem on your side for some people.

Edited, Aug 19th 2013 9:36am by Nashred



I am on hardwire, and I still have this issue. I was even on wireless at my gf place and the same issue. I will mess around with the isp and see what happens. Thanks for letting us know =)
#14 Aug 19 2013 at 8:09 AM Rating: Good
Scholar
***
1,732 posts
amit wrote:
Nashred wrote:

I posted this in another thread about this error for some people:

This problem may not be SE problem... It is a disconnect issue.. I had it for a while and it turned out to be my wireless... Changed to hardwired and no issue ever with it again.

Another friend had it but his isp is terrible. He took his laptop over by me and had no issues at all.

So basically it may be a problem on your side for some people.

Edited, Aug 19th 2013 9:36am by Nashred



I am on hardwire, and I still have this issue. I was even on wireless at my gf place and the same issue. I will mess around with the isp and see what happens. Thanks for letting us know =)


There is a issue in the game that is causing some people that error too.
I am just saying some of the 9000 issues are on the users side. there are so many things that cause disconnects and the 9000 error is a broad error.
It could be a bad router, to tight of firewall or nat settings either in your router or isp router, bad wiring to your house, bad network cable etc.



Edited, Aug 19th 2013 10:11am by Nashred
____________________________
FFXI: Nashred
Server: Phoenix

FFXIV : Sir Nashred
server: Ultros
#15 Aug 19 2013 at 9:30 AM Rating: Decent
*
130 posts
Nashred wrote:

I posted this in another thread about this error for some people:

This problem may not be SE problem... It is a disconnect issue.. I had it for a while and it turned out to be my wireless... Changed to hardwired and no issue ever with it again.

Another friend had it but his isp is terrible. He took his laptop over by me and had no issues at all.

So basically it may be a problem on your side for some people.

Edited, Aug 19th 2013 9:36am by Nashred


Nah that's impossible for me because while my main was undergoing that problem I logged onto a JPN server and leveled a guardian to 16, completing the airship quest, then doing a CNJ to 8 and fishing to 8ish and I never had that error once. Seems like its an NA server problem
#16 Aug 19 2013 at 11:16 AM Rating: Good
**
773 posts
I am thinking that it had something to do with that red triangle thing. Not only did I get the 9000 error going into Copperbell, but /tell was blocked and I could not abandon quest nor disband the party I was in. Even after reboots and a server restart I was still stuck in the party I was in, even when everyone else logged for the night.
____________________________
"We apologize for the inconvenience"
- SE Cruciatus Curse




#17 Aug 19 2013 at 11:21 AM Rating: Good
**
259 posts
3102 is the bigger issue cause you literally can't do anything. But they need to make sure both issues are fixed in 5 days. People aren't going to be nearly as patient once they are paying for this.
#18 Aug 19 2013 at 11:28 AM Rating: Decent
I know it wasn't my internet connection because anytime I tried to do anything with an instance I would get the 90000 error. Any other time I had rock solid connection. I was in "another world" stuck in a bound by duty state. I couldn't progress the story, couldn't /tell and my linkshell disappeared on me. This was never fixed. Hoping they everything worked out in time for early access/release.
#19 Aug 19 2013 at 2:13 PM Rating: Good
**
773 posts
Quote:
I know it wasn't my internet connection because anytime I tried to do anything with an instance I would get the 90000 error. Any other time I had rock solid connection. I was in "another world" stuck in a bound by duty state. I couldn't progress the story, couldn't /tell and my linkshell disappeared on me. This was never fixed. Hoping they everything worked out in time for early access/release.


I am thinking this is actually what is causing the 90000 error. We are stuck in limbo and that prevents us from interacting with the instance server. Just for fun, I switched to MRD to do the guild quests. Couldn't target the mob I was supposed to kill
____________________________
"We apologize for the inconvenience"
- SE Cruciatus Curse




#20 Aug 19 2013 at 5:20 PM Rating: Decent
i posted on the 'Official Beta Forums' that i think the 90k error is a limbo thing. I got stuck on my MRD during Axe in the Stone Quest i got to the part where you save Sighard and hit the 90k error. after this i went to a different server and made a PUG and got all the way to the airship quest line with minor issues. My MRD i managed to get to 17 but my wife said it was like i was stuck in a Duty and on another world is what it showed on her friends list my friends list on the other hand was blank and no matter i logged out i always logged in at the crab fight for Axe in the Stone. Victory in peril gave me another 90k error and forget about dungeons or Guildleves they were impossible to do. Now i had someone in game tell me it was on my end that was the cause of the problems i thought they were stupid then and i still do cause aint nothing on my end going to put me in an almost alternate reality. oh and prevent you from /tell cause your in a duty.
#21 Aug 19 2013 at 11:20 PM Rating: Good
**
773 posts
Had no problem until Copperbell mine quest for my ACN. Went in 3-4 times and d/c'd each time. Got a red triangle. Was invited to a party tried to go in. same thing. Could not abandon quest, use /tell. or even disband party. Server went down and when I came back I was still in party even though everyone else had logged off.
____________________________
"We apologize for the inconvenience"
- SE Cruciatus Curse




Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 314 All times are in CST
Anonymous Guests (314)