Common Errors and Solutions

Launching via Ashita or Windower closes immediately or doesn’t start

When the boot loader appears, attempts to connect, then immediately disconnects and closes, a common cause is that the client files are too far out of date. Be sure to open up PlayOnline Viewer and verify that your client files are at least as new as those used by the server. You can see the current server version here.

Other potential causes:

  • Your Visual C++ (MSVC) components are out of date (see below).
  • DirectPlay is missing (see below).
  • You have not run the PlayOnline Viewer and checked files at least once after a new installation.
  • You haven’t restarted your computer since installing Final Fantasy XI.
  • Your “FINAL FANTASY XI” installation has gone missing (doesn’t show up in the drop down of Check Files in POL Viewer).

If you’re coming from the Nasomi player community or have ever used their installer, you can also get this error. There’s a process to patch your installation to work with “retail” Final Fantasy XI. You can see the full instructions here: https://nasomi.com/wiki/index.php?title=Config:Installing#Retail.2FNasomi_swap.

Launching via Ashita causes ‘bootloader’ to not respond (crash)

Bootloader is not responding

This error can be caused during a new installation when using the default -1 registry values in Ashita.

Updating the values for Window Size, Background Size, Menu Size, and Startup Position can resolve this.

For example, if your playing full screen at 1920x1080, try the following options for a full-screen, windowed (can tab out/multi-monitor)

Ashita at 1080p Fullscreen

Visual C++ (MSVC) Components are missing

If you don’t have the Visual C++ Redistributable Packages installed, you’ll need to install them (this isn’t very common since almost all games use these).

There are many different versions of these packages. Final Fantasy XI, Ashita, and Windower require the MSVC 2015 version. Even if you’re running on a 64-bit (x64) version of Windows, you’ll need the 32-bit (x86) MSVC libraries for FFXI.

You can download them from Microsoft at https://www.microsoft.com/en-ca/download/details.aspx?id=48145.

DirectDraw/DirectPlay is Missing

Verifying DirectPlay

In Windows 8 (?) or higher, you’ll need to enable DirectPlay in the Windows Features dialog. For new players/installations of FFXI, this setting almost always needs set as the default installation of Windows doesn’t include this legacy feature.

  1. Open Add or Remove Programs.
  2. Click to open Programs and Features.
  3. Click to open Turn Windows features on or off.
  4. Scroll down to Legacy Components and click the checkmark for DirectPlay.
  5. Click OK

You will need to restart your computer after the installation.

Attempting to dual box randomly causes the client to crash

Unfortunately, FFXI doesn’t handle dualboxing on DSP very well.

  • Try not running the clients as administrator to reduce the chance of crashing.
  • Be sure that one character is fully logged in before attempting to start a second character.

Characters on my select screen are not my own!

This is, strangely enough, a rather common DSP bug–especially for those who play on the same IP and/or multiboxers. Players cannot actually ACCESS those characters (they’ll receive a POL-0001 error). To fix this, simply close the game and attempt to reconnect.

Launching causes a crash or “failed to initialize instance of polcorecom”

If you’re running an EU version of the client, this can be caused by Ashita or Windower not properly detecting your PlayOnline Viewer locale.

Ashita

In Ashita, add the following:

  1. In your server connection string, add --lang eu to the very end of your --server line.
  2. In the connection settings, change your language to one of the EU languages.

Windower

In Windower, change the following settings by editing your settings.xml file.

  1. Update or add the key for <region>EU</region>.
  2. Update the <args> key to include --lang eu to the very end of your --server line.

Attempting to connect, but receive no error message

Exceed Limit

When connecting via the bootloader (xiloader for Windower or Ashita), if players appear to log in and are immediately sent back to the login screen, it’s likely that they have exceeded their IP-based connection limit. The server supports 3 concurrent connections by IP at a time via our Server Guidelines.

Logged in, but cannot see UI, chat boxes, macro bars, etc.

This is a common problem if your window resolution matches your screen’s resolution (aka “full screen”), but you still have “Show Border” enabled. Disable the border in Ashita or Windower and it should resolve the offset issue that is pushing the UI aside.

“Error 10092” when launching Final Fantasy XI

Verify that your /data directory has been copied from the PlayOnlineViewer folder into the FINAL FANTASY XI folder. See step 10 here.

FFXI-3322 when signing up

The FFXI-3322 is a client-side error that you can receive at signup. This is caused by a character name violation. Unfortunately, the naming rules are handled by the local client, not by the servers and we do not have any control over this.

Error Name Invalid

We’ve found that romanji letter combos that translate to swear words in Japanese tend to be caught by this frequently, even though they’re harnless in other languages.

POL-0001 when trying to log in

POL-0001

There are two potential causes for a POL-0001.

First, a POL-0001 can be caused by a core DSP bug (that’s existed since 2014) that pops up when you have more than 4 characters on a single account. Please keep it to 4 characters per account (you can create as many accounts as you like on Nocturnal Souls). If you receive this error, please contact a GM for assistance.

Bug details at https://github.com/DarkstarProject/darkstar/issues/497.

Second, players who have multiple accounts on the same IP will sometimes receive a POL-0001 if they’ve tried to log in more accounts than they have allowances for and forced a disconnect in one of their characters. DSP does a poor job managing which character belongs to which session when players multibox. To resolve this, log out all characters and log them in one at at time up without exceeding the maximum character limit.

FFXI-3101 when trying to log in

FFXI-3101

This error is caused by a few different errors:

  • There are connection issues between the Nocturnal Souls servers and your network. Please verify your ping, packet loss, and latency are OK.
  • There is a potential DNS issue on your network. Try connecting to our IP address of 68.102.64.244 instead of connect.nocturnalsouls.net in your Ashita or Windower settings.

POL-0033 when trying to log in

A POL-0033 is caused by the system thinking your account is still logged in. You can wait a few minutes, or use the Members Portal to “unstuck character.”

FFXI-3305 when trying to log in

FFXI-3305

A FFXI-3305 is caused by a player trying to log in a character that is already actively logged in and has not timed out. You can wait a few minutes, or use the Members Portal to “unstuck character.”

“Downloading Data” then disconnect when selecting a character

Verify that you don’t have any plugins that could be causing a glitch. The following plugins are known to cause this issue for some players.

  • Windower: xivbar
  • Windower: enemybar
  • Windower: giltracker
  • Windower: weathermon

If you receive this while moving zone to zone (and into a known working zone), it’s possible that you’re also having internet connection issues and have lost your connection to the login server (corrupting your session’s account key). The following may solve your problem:

  • Use our IP address of 68.102.64.244 instead of connect.nocturnalsouls.net when connecting.
  • Try adding --hairpin to the end of your connection string in Ashita or Windower can resolve it on some Windows 10 machines (per the DSP devs).
  • Shutdown/restart your computer, modem/router, and verify your connection to the internet is stable.
  • Check your firewall settings that you’re allowing all ports for all of the FFXI executables and/or add an exception to allow all traffic to/from 68.102.64.244.
  • Try pinging a known functional service, such as google.com for 5-10 minutes and see if you’re dropping packets; FFXI is fairly sensitive and dropped packets can cause this issue.
  • If you’re playing on Wifi, try using a wired connection; drops or reconnects of your Wifi can cause the connection to drop between the login server and client.