Cannot Login to everquest server rerun patcher. (error insid
 

When I click Play in server select it loads all the models and crap at the end of the loading my monitor clicks 2 times then it pops me back to server select and says Cannot login to everquest server. Try re-running patcher.

I had this problem trying to login to other servers on frags before I tried my own server. Whats the problem here?

Here the error in world.exe

Logged in: Local: eqemu
Sending list of guilds
Client timeout
Removing client from 127.0.0.1
Unknown Opcode:13601 size:2056
Client disconnected


Now the first 2 times I didnt recieve the client timeout but still got the rerun patch message. The third time gave me that message so im wondering.

Heres the entire log the most I could grab. This is me trying to log in afew times.



829004 Unkown opcode:13601 size:2056
Client disconnected
Removing client from ip:127.0.0.1 port:1499
1385997 New client from ip: 127.0.0.1 port:1558
Logged in: Local: eqemu
Sending list of guilds
1407998 New client from ip: 127.0.0.1 port:1562
Logged in: Local: eqemu
Sending list of guilds
Client timeout
Removing client from ip:127.0.0.1 port:1558
1416002 Unkown opcode:13601 size:2056
Client disconnected
Removing client from ip:127.0.0.1 port:1562
2505998 New client from ip: 127.0.0.1 port:1702
Logged in: Local: eqemu
Sending list of guilds
Logged in: Local: eqemu
Sending list of guilds
Logged in: Local: eqemu
Sending list of guilds
2514997 Unkown opcode:13601 size:2056
Client disconnected
Removing client from ip:127.0.0.1 port:1702


Whats this unknown Opcode? When I removed eqemu from password and username in login.ini it stopped doing double logins in world but I still get kicks with same message as above. Whats up with this?

awnser
 

Everyone that is running the servers get that unknown oppcode because those are the commands that everquest is sending that is not implamented in the servers yet. but this has nothing to do with your error.

k you said you hade the same problem trying to log to others servers to then this has nothing to do with your servers that you are running it has to do with your everquest files.
i will try to help you later if someone else dosnt because i must go now. im at school and have to get a vb program done

so viper are you actually up and running sometimes then? i noticed you helping ipak in the other thread (think it was ipak).

quag notes: 0.2.0 World.exe has a deadlock in it, fixed in next release.

upon someone pointing out intermittent problems logging in.

I've experienced the same problem. So I've basically stopped looking into it until the fix is in.

It was weird, I was able to log into my server without a problem the fist day I installed 0.2.0. Next night I start my server up and go to connect and get dropped as soon as I hit the character creation screen.

Glad to see I wasn't losing my mind and the only one with this problem :p

I thought it was my account in the DB when I had this problem. I manually entered my gotfrags user and password. Then I could not log in, so I bombed the account in the DB and let the login server create it. Works so far...

glad to hear it =)

Well I cant get past this. When I tried to play on frags servers none of them worked everyone of them would give me the repatch error after loading everything. I assume there is an issue with the login and client having issues?

Ive tried everything now apart from formatting and installing new OS. heh. Guess ill have to wait for another release.

What do you mean by Quag said there was a deadlock? Think I know what you mean but give an example.

Hogger:

What did you do to do that? To my knowledge all you can use is eqemu username to play local. Im using mini login. I get afew error in minilogin on start up but I think thats normal. What did you do step by step to get it working?

Zeit:

I have never been able to get to char select. I always have had this issue. The world server not showing in server select issue I had when I first got my server running and playing with login.ini fixed that so figured id give Ipak some help. hehe. This issue I have though is very bad. I got the feeling I might have this issue even with newer versions. I just cant get to char select on frags server or mine. =(

me too..
 

Ok, heres the full text of the output of what happens when I try to log in.

------
LoginServer.ini read.
Using database 'eq' at 10.0.0.4
Loading items...done.
Loading guild ranks...done.
World server listening on port:9000
Connected to LoginServer: eqlogin.gotfrags.com:5999
New TCP connection: 10.0.0.4:3634
New TCP connection: 10.0.0.4:3636
New TCP connection: 10.0.0.4:3639
New zoneserver: #1 10.0.0.4:3636
New zoneserver: #2 10.0.0.4:3634
New TCP connection: 10.0.0.4:3640
Zoneserver SetConnectInfo: 10.0.0.4:3634: 10.0.0.4:9005
Zoneserver SetConnectInfo: 10.0.0.4:3636: 10.0.0.4:9002
New zoneserver: #3 10.0.0.4:3639
New TCP connection: 10.0.0.4:3641
Zoneserver SetConnectInfo: 10.0.0.4:3639: 10.0.0.4:9001
New zoneserver: #4 10.0.0.4:3640
Zoneserver SetConnectInfo: 10.0.0.4:3640: 10.0.0.4:9003
New zoneserver: #5 10.0.0.4:3641
Zoneserver SetConnectInfo: 10.0.0.4:3641: 10.0.0.4:9004
67997 New client from ip: 10.0.0.3 port:1073
Logged in: LS#747: patman
Sending list of guilds
97998 Unkown opcode:13601 size:2056
Client disconnected
Removing client from ip:10.0.0.3 port:1073
------

as you can see, im getting the same opcode error, and then *poof* it decides to disconnect.

heres the loginserver.ini:

-----
[LoginServer]
loginserver=eqlogin.gotfrags.com
worldname=PatMan's Server (Internal IP)
locked=false
worldaddress=10.0.0.4
account=
password=
-----

Now, I had originaly tryed this with my full install (rok, sov, sol) of eq client. So I was thinking that maby it was caused by server filter, or some other wierd option I might have set.

So I created another directory and only installed the clasic package client. I didnt change any of the defaults, and I still get this error.

I've tryed connecting to other servers on gotfrag's login, nothing.

Basicly, the progress indicator of the loading screen gets to 'loading player charcter models' and thats when I see the opcode error and disconnect message on the console.

Anyone know what this opcode does, and if theres a temporary workaround to keep the client from sending it?

consistent
 

Actually your log looks cleaner than mine. I get 13601 too, and a couple of extra before it.

The next unknowns should be: 14625 and 0x9221
then the autoboot

So the problem is not that you are getting unknown op codes, but you are not getting enough of them.

After you start minlogin (which you are not doing), world, and boot5zones.bat , you world screen should have this:

Newzone server #5
Zoneserver


then when your client logs nothing interesting happens until you select a server then you get the logged in message and sending guild list.

I then get 4 known opcodes, then the 13601.

I also get by the time I am at the char select two more unknown op codes:
14626 & 0x9221.

So you are getting disconnect from the server select to before all the char load stuff and the char select.

All this matches what you have said. So now its a matter for someone to duplicate that.


but here is my point, you screen looked fine up to and including 13601
But I also get 4 additional known op codes before 13601.
You are hanging/crashing on the client side. The connectivity message is correct-- when you crash the world server you can go on. EQ for some reason puts out their cryptic message but all it means is that you have crashed.

Ok, I've been able to get it to work...by using eqw.

So whatever eqw does to the client environment, it doesn't case that unknown opcode.

Not quite that easy. You and Cyrax91x are the only two so far that claim eqw 2.2 works and eqgame patchme doesn't. There are also a couple of people that can't get going at all -- including me on my second machine.

I believe that most people can use both eqgame patchme and eqw 2.2 just fine. So it s a matter of still finding out why some people are still having difficulty.

mini login repatcher prob
 

I had a similar problem using the mini login. I resolved it
by making my loginserver to point to 127.0.0.1 instead of
the external ip. It works now but now people outside can't
log in. I'm guessing mini login was designed for internal
use only?

Baltar

yeah thats why it was released :)