Does changing to one of the newer servers change this? I'm tired of this bullshit. I'd rather restart then deal with this error over and fuckin over again.
Does changing to one of the newer servers change this? I'm tired of this bullshit. I'd rather restart then deal with this error over and fuckin over again.
lol, so I had to force log because of the massive Duty finder affecting a solo instance fail, and now I got hit by this. No queue or anything. Neat.
Last edited by Klefth; 08-25-2013 at 04:16 AM.
I'm getting this as well, it should be allowing us to queue up to the server, but it's just kicking me out...
this has to be frustrating for a lot of people. and embarrassing for SE. i mean come on. you have the numbers....you know exactly how many players there are in each world. you also know roughly how many there will be on the 27th if you include v1.0 and potential first day of release players. with that in mind, there should be some contingencies to prevent a crowding so severe that players don't even so much get a queue. i can understand the various instance errors end whatever, but there is no reason why the problem would be as such that you simply lock out players entirely.
and no, i am not going to make another player in another server so that they can have the same problem. i certainly don't want to go through some [wonderful] opening sequence again for the n'th time (which i cant skip btw). so it would be really nice if all of this would be resolved at least by the 27th....generously speaking.
[NA] Regarding the Instance-Related Issues (Aug. 24)
While we were able to address the previous issue wherein players were unable to access instances, we conducted another investigation and confirmed that the issue was ongoing for a number of players.
We have been able to identify the cause of the issue and have started the recovery operations. Once we have tested the fix, we plan on conducting another emergency maintenance. We will follow up once we have a better idea on the time frame of the maintenance.
We sincerely apologize for any inconvenience this may cause.
Yes another Emergency maintance. SO dont get to comfy playing it you will get d/c for another 3hours soon
I think I'm done trying to play this game today...
got this error now too seems even the queue system is bugged
Legacy servers should not be allowing new characters, and they should have been mathematically reviewed. Otherwise why have them other than to secretly punish us for not wanting them to wipe our characters??
Legacy Campaign.....Yaaaaay, you appreciate us... You reaaally do.
Just tried logging back in myself after taking a break, was in que #12 and then boom error 1017 and been stuck at that for 5 mins now![]()
"Everyone has something they hold dear, something they never want to lose. That's why they pretend. That's why they hide the truth. And that's why they lie."
Please post over here about this.
http://forum.square-enix.com/ffxiv/t...ing-Error-1017
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.