Help with server errors (pics)

**Derision** · #1 03-04-2010, 10:24 AM

Quote:

Also, I still get a 10061 error just one time at the beginning of eqlaunch, but then it says its connected to localhost and begins loading zones. Here's what it says:
[Debug] Starting Log: logs/eqemu_debug_4936.log
[Debug] [LAUNCHER__INIT] Loading server configuration..
[Debug] [NET__WORLD] WorldConnection connect: Connecting to the server localhost
:9000 failed: TCPConnection::Connect(): connect() failed. Error: 10061
[Debug] [LAUNCHER__ERROR] worldserver.Connect() FAILED! Will retry.
[Debug] [LAUNCHER__INIT] Starting main loop...
[Debug] [NET__WORLD] Connected to World: localhost:9000

That 10061 error is not a problem, it's just that the launcher tries to connect to world before world is ready. You can see it successfully connects shortly afterwards by the [NET__WORLD] Connected to World: localhost:9000 message.

Code:

<!-- Loginserver information. Defaults shown -->
<loginserver>
<host>clmtyserver.dnsalias.com</host>
<port>5998</port>
<account>MyAdminAccountName</account>
<password>MyAdminAccountPassword</password>
</loginserver>

If you are running EQEmuLoginServer on the same PC as world, then I would put localhost or 127.0.0.1 or your internal IP (192.168.x.x) in the <host> part of the loginserver section. Also, I don't think you need to specify an account or password for the loginserver.

It sounds like world is not connecting to the loginserver. If you switch to the command window in which EQEmuLoginServer.exe is running, you should see a message along the lines of 'New server connection from a.b.c.d' when world connects to it, or you might have some error messages in there.

In addition, look at the output of world.exe, does it say connected to loginserver, or are there error messages there as well ?

Eva Aisling · #2 03-04-2010, 10:45 AM

First, I tried just changing the dns address to my local IP as you suggested. When the zones are loaded up in the sleeping window, this is what is in world.exe:

[Debug] [WORLD__LS] Connecting to login server...
[Debug] [WORLD__LS] Connected to Loginserver: 192.168.x.xxx:5998
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:62069
[Debug] [WORLD__CONSOLE] New launcher from 127.0.0.1:62069
[Debug] [WORLD__LAUNCH] Adding pending launcher 1
[Debug] [WORLD__LAUNCH] Launcher Identified itself as 'zone'. Loading zone list.

[Debug] [WORLD__LAUNCH] Removing pending launcher 1. Adding zone to active list.

[Debug] [WORLD__LAUNCH] zone: dynamic_01 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:62071
[Debug] [WORLD__CONSOLE] New zoneserver #1 from 127.0.0.1:62071
[Debug] [WORLD__ZONE] [1] Zone started with name dynamic_01 by launcher zone
[Debug] [WORLD__ZONE] [1] Auto zone port configuration. Telling zone to use por
t 7000
[Debug] [WORLD__LAUNCH] zone: dynamic_02 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:62073
[Debug] [WORLD__CONSOLE] New zoneserver #2 from 127.0.0.1:62073
[Debug] [WORLD__ZONE] [2] Zone started with name dynamic_02 by launcher zone
[Debug] [WORLD__ZONE] [2] Auto zone port configuration. Telling zone to use por
t 7001
[Debug] [WORLD__LAUNCH] zone: dynamic_03 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:62075
[Debug] [WORLD__CONSOLE] New zoneserver #3 from 127.0.0.1:62075
[Debug] [WORLD__ZONE] [3] Zone started with name dynamic_03 by launcher zone
[Debug] [WORLD__ZONE] [3] Auto zone port configuration. Telling zone to use por
t 7002
[Debug] [WORLD__LAUNCH] zone: dynamic_04 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:62077
[Debug] [WORLD__CONSOLE] New zoneserver #4 from 127.0.0.1:62077
[Debug] [WORLD__ZONE] [4] Zone started with name dynamic_04 by launcher zone
[Debug] [WORLD__ZONE] [4] Auto zone port configuration. Telling zone to use por
t 7003
[Debug] [WORLD__LAUNCH] zone: dynamic_05 reported state STARTED (1 starts)
[Debug] [WORLD__ZONE] New TCP connection from 127.0.0.1:62079
[Debug] [WORLD__CONSOLE] New zoneserver #5 from 127.0.0.1:62079
[Debug] [WORLD__ZONE] [5] Zone started with name dynamic_05 by launcher zone
[Debug] [WORLD__ZONE] [5] Auto zone port configuration. Telling zone to use por
t 7004

Tried logging in but still get blank screen.

Second, I tried removing my account and password info under login as you suggested. World.exe window again said it was connected to my IP. I tried logging in and got this error and launcher crashed: http://i135.photobucket.com/albums/q...ebugError2.png

EDIT: It seems that I always get that C++ Debug Error when I try to log in without entering my account name and password into config file, but the number changes.

EDIT: ROFLMAO! I hit [Ignore] for debug, rather than just closing game and my server popped up in list! I tried logging in with my account info and my husband's and it hung forever and in the World window I got a duplicate name message. Perhaps this is because I registered us with the same name we used for eqemu? I decided to make a new one and try logging in and it worked!

If the Devs want any more information to try and post a workaround for the debug error just let me know. I have no idea if it's just me or an issue with Windows 7 or what. Thanks for help!

Eva Aisling · #3 03-04-2010, 12:19 PM

I apologize for double-post, but I couldn't edit again.

I just entered a new account into MySQL and didn't get a debug error when logging in. Server was already in list. I have no idea why...

I made a new account for my husband and imported it into the database, but he can't login. I have port forwarded on router for his internal IP and changed his eqhost file to read :
[LoginServer]
Host=clmtyserver.dnsalias.com:5998

He can see the server Up with no debug error. I log in with his info and the screen is black for a minute or two before telling me that it could not connect to the server. We are on LAN.

**Derision** · #4 03-04-2010, 02:01 PM

Try putting an entry in the c:\windows\system32\drivers\etc\hosts file on his PC to map clmtyserver.dnsalias.com to the internal IP address of your server, i.e.

Code:

192.168.x.x             clmtyserver.dnsalias.com

This will mean his connection will stay completely internal to your LAN, rather than going into your router and back to your LAN.

Eva Aisling · #5 03-04-2010, 03:37 PM

I set permissions and tried that, but it didn't work.

I'm currently wading through dozens of posts looking for a solution that's already been posted...