Error 3102 and 90000 - Resolved

[Aangeliceus]

From the beta forum:

Regarding the Error 90000 Issue
We apologize for the delay in getting all of you an update on the Error 90000 issue.

We have made adjustments to the database server on the backend and the issue has been addressed.

For those who were unable to participate in the Beta Test due to this issue, we deeply apologize for the inconvenience. We ask for your continued support in Early Access and the official launch of the service.

Regarding the Error 3102 Issue
Again, we would like to apologize for our delay with the update on Error 3201 issue.

The issue has been resolved after the maintenance that was performed during the Beta Test and we have confirmed that the issue has been fully addressed.

We have corrected the character data for all the characters that were affected by this error, and you'll be able to participate in both Early Access and the official service without any problem.

Once again, for those who were affected by this issue, we deeply apologize for the inconvenience and ask for your support in both Early Access and the official launch of the service.

Hope it's really fixed and not just a band-aid type of fix.

 

[Elvier]

I just hope they were able to find and fix all the 3102 characters (had to do this individually from what they said in other posts).

 

[Aangeliceus]

I just hope they were able to find and fix all the 3102 characters (had to do this individually from what they said in other posts).

Any programmer with their salt should have taken a sample of the problem characters and identified a singular root cause. Then, applied that fix globally across all characters that fit the profile.

The error 90000 should have been even more simple to resolve for a range of characters since it appeared to be a problem with the database or the server hosting the database.

In any case, I didn't get caught by either of these, but I hope all that had have had their characters fixed.

 

[Fiko]

Mine was fixed at end of beta because I posted my info in their thread, so I'm not too worried.

 

[Elvier]

@Fiko I posted to their thread too. So maybe mine got fixed. I did not try to log in Sunday since I did not know til too late that they extended the Beta a bit. So I don't know but figure it should be done.

 

[Aangeliceus]

Revision:

2013/08/22 20:20 Regarding the Issue Occurred on Beta Phase 4 (Aug. 22)


Thank you for playing FINAL FANTASY XIV: A Realm Reborn.

We are notifying about the issues that occurred and measures taken during the Beta Test Phase 4.

-For Worlds under the North America/European Data Centers, we have resolved the issue where in some cases Error 3102 was displayed and was not allowing login.

Since the detail of the error was that it occurs when a Character is left in a World for a short period of time, the error may display upon situations such as connection loss. Even in that case, we have fixed the issue so players are able to login again after a minute or so.

-We have resolved the issue where in some cases Error 90000 was displayed and was having login difficulty.

-We have resolved the issue where in some cases Error 90000 was displayed and players were unable to move to certain areas.

-We have resolved the issue where in some cases players were unable to complete Main Quests and Class Quests even though they were completed.

Also regarding the Beta Test Phase 4, we are currently fixing the data for Characters that had the corresponding issues.

*There are Quests that allows players to choose their rewards, but we have reports saying that the status of the selection stayed as unselected. For Quests that allows players to select their rewards, we please ask our players to select the rewards.

-We have resolved the issue where in some cases players were unable to complete certain Sub Quests even though they were completed.

Also regarding the Beta Test Phase 4, we are sorry to ask our players to abandon the Quest once and offer it again for the corresponding issues if occurred.

*There are Quests that allows players to choose their rewards, but we have reports saying that the status of the selection stayed as unselected. For Quests that allows players to select their rewards, we please ask our players to select the rewards.

-We have made a change, so when receiving damage during an Event and in some cases unable to progress in certain Quests, players will no longer receive damage.

Also, regarding the Beta Test Phase 4, we are sorry to ask our players to abandon the Quest once and offer it again for the corresponding issues if occurred.

-We have resolved the issue where in some cases players were unable to progress Guildleve Release Quest.

Also regarding the Beta Test Phase 4, we are currently fixing the data for Characters that had the corresponding issues.

-We have resolved the issue where in some cases the client program force quits when selecting a Character.

-We have resolved the issue when completing Thaumaturge and Fisher Class Release Quest, the amount of gear set increases by two.
*Gear sets normally increase by one

Also, if affected by this issue, some players will be at a disadvantage compared to other players so for the corresponding Characters, we are planning to implement a compensation. We will notify everyone once we decide on the compensation date and method.

-We have resolved the issue when in some cases during a server outage, the action to mount and call a Minion was disappearing.

Also, for Characters that have the call action disappear, the action has been reinstated.

-We have resolved the issue when in some cases during a server outage, Items that were stored in the Cabinet was disappearing.

Also, for Characters that have lost Items, what was in the Cabinet has been reinstated.