Iris Online Help

Troubleshooting for Iris Online server owners across 1.18, v1.18, 1.10 and 1.20 - connection errors, database problems, client crashes and configuration mistakes.

Most problems posted here come down to a handful of causes: the client pointing at the wrong address, a database the server cannot reach, a missing runtime library, or a port that was never opened. Search before posting - the same Iris Online errors come up often and usually already have an answer.

Iris Online private server files center on KR 1.18 - server, database and client - with JP 1.10, v1.8.201, 1.18.18061 JPN and SOKE v1.18 sources, and 1.12 and 1.20 in development. Setup creates IRIS_MEMBERDB, IRIS_LOGDB and IRIS_GAMEDB in MS SQL 2005, three ODBC DSNs, then Installation00_DB.bat. Gamebryo 2.6 source compiles in Visual Studio 2005 with SP1 and DirectX SDK; IrisClient.exe needs the Visual C++ 2008 debug DLL. Server IP comes from IPCONVERTER, patch.ini or hex edits. GM Tool, IrisLauncher, IrisPatcher, PatchMaker and PackTools cover the client, .pack files unpack in WinRAR with a fixed password, exp rates sit in Script/Resource/DropExpIncrease.txt, and a PHP web store needs PHP 5 and MySQL.

Client versions covered here 1.18v1.181.101.20

Common questions

Why will my Iris Online client not connect to the server?

Nearly always the address the client is pointed at. On many builds the server address sits inside a packed client file rather than a plain text config, so it has to be edited there. Check as well that the server is listening and the port is actually open.

Why will my Iris Online server not start?

Usually a database it cannot log in to, a missing runtime, or a port already in use by something else. The server console or log normally names the cause on the first failure, and the processes often have to be started in a particular order.

How do I get a useful answer about Iris Online here?

Post the Iris Online build you are running, the file set you used, the exact error text and what you have already tried. Threads with that detail get answered; vague ones usually do not.