Client crashes when attempting to enter Windurstian Consul in Northern San d'ria

Platform: Windows
ISP: Verizon FIOS
Type of Internet Connection: Optic Fiber
Internet Connection Speed: Over 50 Mb/s
Date & Time: May 1 2016 18:45 EST
Frequency: Always (Reproduced the issue six (6) times)
Character Name: Detsero
Race: HumeM
World: Valefor
Main Job: Thief, Lv.99
Support Job: Dancer
Area and Coordinates: Northern San d'Oria, H-9/I-9 Border, at the Windurstian Consul
Party or Solo: Solo
NPC Name: None
Monster Name: None

Steps:

I had switched my city-nation allegiance to Windurst (Previously: San d'Oria, Rank 10) earlier in the day and was working my way through Windurst story missions. I started the Windurst story mission 2-3 "The Three Kingdoms," spoke to Kupipi in Heavens Tower, then proceeded to Northern San d'Oria to perform the San d'Oria branch of the mission before the Bastok portion of the mission. When I approached the Windurstian Consulate building stairs (The bottom of the stairs that lead up to the door), my FFXI client crashed with the following error:

Error code: FFXI-2003
Failed to read data.

After clicking, "OK" I am sent back to the FFXI portal on PlayOnline. I am currently unable to log in because my client crashes with the same error code before any of the game's graphics are able to load.

Additional Information:

On a hunch, I decided to try running a file check on my FFXI files through the PlayOnline main menu. The process found one corrupt data file, which it repaired, but the issue still occurred on the next attempt to log in.

I attempted to log on to the installation on my laptop and this error did not occur. This appears to have been something that went wrong with the client files on my desktop, as I attempted a file repair two times in a row without doing anything in between, and the same file (SquareEnix\FINAL FANTASY XI\ROM\2\0.DAT) was flagged both times. I am unsure of why this file was corrupted, but I am going to re-install the game on my desktop.

In summary, this is probably not a bug in-game, but rather an issue with my game client that may have been fixed with a re-installation of the game. Sorry for the confusion.