OOTP reports connection and import problems as numeric codes with very short messages. This is the full list, grouped by when you hit them, with the cause that actually explains most occurrences.
Download errors (-100 to -105)
These occur when OOTP tries to download the league file.
| Code | Message | What it usually means |
|---|---|---|
| -100 | Missing Login Data | No credentials entered. If managers hit this, the commissioner likely left "Save FTP account data for league file download in league file" unchecked. |
| -101 | Connect error | Cannot reach the server at all. Wrong host, server down, or blocked port. |
| -102 | Download error | Connected, but the transfer failed partway. Often a permissions or disk problem on the server. |
| -103 | Wrong path | The folder does not exist. See the path note below — this is the most misunderstood one. |
| -104 | File not found | The path is right but the league file is not there. The commissioner has not uploaded yet. |
| -105 | Unknown error | Rare. Re-test the connection and check server logs. |
Upload errors (-201 to -204)
These occur when a manager exports their team or a commissioner uploads.
| Code | Message | What it usually means |
|---|---|---|
| -201 | Connect error | Almost always FTP Mode set to Active instead of Passive. Full fix here. |
| -202 | Upload error | Connected and authenticated, but could not write. The account lacks write permission on /exports. |
| -203 | Wrong path | The upload directory does not exist, or is spelled differently than configured. |
| -204 | Wrong base folder | The base folder set in OOTP does not exist on the server. |
The difference between -201 and -202 is worth internalising: -201 never connected, -202 connected but could not write. The first is a network or mode problem, the second is a permissions problem.
The path rule that causes most -103 and -203 errors
Paths in OOTP are relative to the root of your FTP account, not your server's filesystem root.
If your FTP account already lands you in /home/leagues/myleague, then the
league file directory is:
- Correct:
/leaguefile - Wrong:
/home/leagues/myleague/leaguefile
Entering the full server path produces a folder that does not exist from the FTP account's point of view, and OOTP reports -103 or -203.
Team import errors
These appear when the commissioner runs Import all teams from server.
The ones you will actually see
| Code | Message | Cause and fix |
|---|---|---|
| 1 | Team file not found | No export from that manager. They did not export, or it went to the wrong folder. |
| 2 | Wrong game date | The export is from a different sim date — usually a manager who exported from a stale league file. They must download the current file and redo their moves. |
| 3 | Wrong number of games | Same root cause as code 2: the export does not match the current league state. |
| 4 | Wrong team id | The export is for a different team than the manager is assigned to. |
| 5 | Wrong build number | The manager is on a different OOTP version. Everyone must be on the same build. |
| 999 | Checksum incorrect | Corrupt or incomplete file, usually an interrupted upload. Have them re-export and re-upload. |
Data-loading codes
Codes in the 100s mean OOTP found the file but could not reconcile its contents against the master database:
| Range | Area |
|---|---|
| 110–112 | Team / minor league team data |
| 120–122 | Player data |
| 130–132 | Coach data |
| 140–142 | Human manager data |
| 150–153 | Contract offers |
| 160–161 | Scouting reports |
| 170 | Waiver claims |
These nearly always trace back to the same thing: the manager exported from a league file that no longer matches yours. The fix is the same in every case — have them download the current league file, redo their moves, and export again.
Codes 77 and 78 — incomplete roster
"Roster not properly set or incomplete." The manager's roster violates a league rule — wrong roster size, an unfilled position, or an illegal minor league assignment. They need to fix the roster in-game and re-export.
Avoiding most of these entirely
A large share of these errors come from three preventable situations:
- Managers working from a stale league file. Announce the sim, and make clear that anyone who downloaded before the latest upload must re-download.
- Version drift. Agree on an OOTP version at the start of the season. Build mismatches produce code 5 with no useful detail.
- Wrong paths at setup. Use the Test button in every FTP section before inviting anyone. A -103 found during setup takes a minute; the same error found by twelve managers takes an evening.
If you host with SimHosts, the directories are created for you at the paths OOTP expects, with write permissions set so managers can upload exports but cannot overwrite the league file — which removes the -202/-203 class of problem before it starts.