Hi all. I got my server all installed and in trying to run the latest client I got the client/server mismatch (client version 650559). So for now I dug out my DVD's and installed the game up to Kingdom of Sky without updating, figuring it would work. But when I try to run everquest2.exe it does nothing at all. I'm running Windows 10 and tried it in compatibility mode with earlier versions of Windows and as an administrator with no luck. Sorry I don't have more info. I'm at work and not at my PC. Any ideas what the problem might be?

Hello Xaeyr.

For the latest client to be compatible with your server you will need to have either world.exe or world64.exe connect to the db patcher to download the latest opcodes. This is done in you world dir by editing the LoginServer.ini. At the bottom you need to edit the [UpdateServer] part to look like this.
You may have to change autotableupdates to always.

Then you will need to backup the updated opcode table in eq2world database. I usually export the opcodes table as a SQL file. Now switch over to the eq2ls database to import the SQL file you created. This will update your login server database with the latest opcodes. This has to be done or login server will not recognize the latest client. You should now be able to connect to your server.

Be sure to backup you client for before the next patch or it will not work on the emulator.

As for Kingdom of Sky it is not supported by the server now. The supported clients can be found on the Wiki at the Compatible Clients page.

Hope this helps.

EDIT: Jab can you verify those settings for UpdateServer and the autotableupdates needing to be set for me please. I thought I had a ini with me, but turns out I don't.

Cynnar wrote:EDIT: Jab can you verify those settings for UpdateServer and the autotableupdates needing to be set for me please. I thought I had a ini with me, but turns out I don't.

That is correct.

Thanks for the assist. Tried what you suggested and connected to the update db but still get the client/server mismatch, so my version must be newer than is supported. It says it's client version 650559 build 12203L.

Are you running a minilogin locally? If so you should get red text saying a client was rejected due to invalid version in the console, what number is reported there. I ask as the data version is hidden and can't be obtained by any means other then packets.

EDIT: The live client I got connecting recently is 12261L, Oct 21

The only red I see is...

And yes, minilogin locally.

Xaeyr wrote:The only red I see is...

Code: Select all

Error bad version: 60130 - Login Denied.
Login Denied! Bad version: 60130 (resp 6)

This means that the opcodes for the client you are trying to connect with are not in your login server database. If I am not mistaken this is looking for opcodes for version 60130.

If you exported the opcodes from the eq2world database after you connected to the db patcher then you may need to open the sql file in a notepad program like notepad++ and make sure that USE `eq2world`; is set to your loginserver database USE `eq2ls`;. Otherwise it is adding the sql back to eq2world instead of eq2ls.

This means that the opcodes for the client you are trying to connect with are not in your login server database. If I am not mistaken this is looking for opcodes for version 60130.

If you exported the opcodes from the eq2world database after you connected to the db patcher then you may need to open the sql file in a notepad program like notepad++ and make sure that USE `eq2world`; is set to your loginserver database USE `eq2ls`;. Otherwise it is adding the sql back to eq2world instead of eq2ls.

I ran the db update as suggested, exported the opcodes, edited the sql as you suggested and sourced it in. It sourced it into eq2ls as it should but when I run the client I still get the same error referencing the same version number.

In your opcodes table for the eq2ls do you have version_range1 60127 version_range2 60145?

Edit: Also are you able to connect to the EQ2Emulator server with that client?

Thank you, Cynnar. The message you sent me worked perfectly. I was able to login locally with no problems Not sure why I wasn't getting updated opcodes though.

No problem and glad it worked. I am not sure about the db patcher and why it did not update your opcodes. Jab when you read this you will have a pm, if you didn't read it first, waiting for you. I am going to test the db patcher on a older db I have, and will give you the results.