New login issues?

[Stormlord]

The last couple of days, I've been having some login issues.

I get to Megan, type in the password, then it hangs.

The DOS login window just states "Login OK" for the last line.

Usually, I just quit and keep trying until I get in ... sometime 4 or 5 times.

Today though (Thanksgiving), I've tried over and over and can't get in.

I reset the updates, just in case there was some corrupt or missing files, but no difference.

The Net7 screen varies for how many ppl are on (up and down), so it appears others are getting in.

Fairly certain this has just been since the last update. Before then I had no issues whatsoever.

Any ideas?

Edited November 25, 2010 by Stormlord

[fuulishone]

I've been noticing this too. Resetting my home network, rebooting, checking other Internet locations and such pretty point at it NOT being my Internet connection.

If you let it wait long enough, you might get in, or the client will eventually time out. It seems like the client/proxy is simply sitting there waiting for an answer back from the server.

P.S. There also didn't seem to be any packet loss, so probably not the trans-atlantic internet connection either.

[Orga1]

I've been noticing this too. Resetting my home network, rebooting, checking other Internet locations and such pretty point at it NOT being my Internet connection.

If you let it wait long enough, you might get in, or the client will eventually time out. It seems like the client/proxy is simply sitting there waiting for an answer back from the server.

P.S. There also didn't seem to be any packet loss, so probably not the trans-atlantic Internet connection either.

Oh goodies, it's not just my end then , I'm just reporting this quickly cause i have a thanksgiving gathering and kinda sad, i too can't log in but I Notice I got a Illegal OpCode in the net7proxy. I don't know what it means I was going through secure authentication last time and worked all day yesterday. Now today it's causing the launcher at log-in to crash, Hang and other bad equally M$ reporting errors!

25/11/10 10:53:52 Connecting to Authentication Server on 127.0.0.1:443
25/11/10 10:53:52 RegisterSectorServer at IP address 127.0.0.1, port 3500
25/11/10 10:54:21 User 'Orga2' logging in from IP: 127.0.0.1
25/11/10 10:54:22 TCP login link established.
25/11/10 10:54:22 Starting TCP login connection
25/11/10 10:54:22 Login link established to server.
25/11/10 10:54:22 Received account valid from Server
25/11/10 10:54:22 Received account request.
25/11/10 10:54:23 Received TCP avatarlist from Server
25/11/10 10:54:23 Received Avatar list.
25/11/10 10:54:32 Sending Avatar Login.
25/11/10 10:59:22 Connecting to Authentication Server on 127.0.0.1:443
25/11/10 10:59:22 RegisterSectorServer at IP address 127.0.0.1, port 3500
25/11/10 10:59:46 User 'Orga2' logging in from IP: 127.0.0.1
25/11/10 10:59:46 TCP login link established.
25/11/10 10:59:46 Starting TCP login connection
25/11/10 10:59:46 Login link established to server.
25/11/10 10:59:47 Received account valid from Server
25/11/10 10:59:47 Received account request.
25/11/10 10:59:47 Illegal opcode from Server to Global Account connection
25/11/10 11:00:35 MVAS thread running
25/11/10 11:01:23 TCP connection on port 3805 was reset

[Lot]

Login server does seem to go through a period of getting jammed up every now and again. And the launcher too. After getting a character logged in -- and that may take many attempts -- it seems ok.

[Tienbau]

yes the login server had crashed. I forgot to re-build it using the release version; the debug build was running - when a program exception is thrown (a fancy way of handling program errors) something different happens for 'release' and 'debug' builds:

In a release build, the part of the server that handles these exceptions (called the exception handler, for obvious reasons) can catch these problems, and for the login server the program self-terminates, the main game server spots that it hasn't heard from the login server for a while and starts a new login server, so the total interruption to logins lasts only 30-40 seconds.

However, when a debug build of the login server slips through, and program exceptions occur (as they do inevitably - the login server bears the brunt of the evils of the internet), the program 'helpfully' invokes the Just-In-Time debugging feature, which locks up the program and because the login server mutex is still being held, the main game server is unable to start a new login. So basically, the login server is sat there, frozen, until someone comes along and manually intervenes.

I'll change the project settings so this can't happen again accidentally - we really don't need debugging for the login server, just for it to automatically restart when it dies.

Anyway, that's enough tech talk, but I know some people appreciate the full story of what's actually going on.

cheers,

TB

[CptGemini]

Anyway, that's enough tech talk, but I know some people appreciate the full story of what's actually going on.

I'm one of them lol.

[Hexersup[IS]]

Oh goodies, it's not just my end then , I'm just reporting this quickly cause i have a thanksgiving gathering and kinda sad, i too can't log in but I Notice I got a Illegal OpCode in the net7proxy. I don't know what it means I was going through secure authentication last time and worked all day yesterday. Now today it's causing the launcher at log-in to crash, Hang and other bad equally M$ reporting errors!

25/11/10 10:53:52 Connecting to Authentication Server on 127.0.0.1:443
25/11/10 10:53:52 RegisterSectorServer at IP address 127.0.0.1, port 3500
25/11/10 10:54:21 User 'Orga2' logging in from IP: 127.0.0.1
25/11/10 10:54:22 TCP login link established.
25/11/10 10:54:22 Starting TCP login connection
25/11/10 10:54:22 Login link established to server.
25/11/10 10:54:22 Received account valid from Server
25/11/10 10:54:22 Received account request.
25/11/10 10:54:23 Received TCP avatarlist from Server
25/11/10 10:54:23 Received Avatar list.
25/11/10 10:54:32 Sending Avatar Login.
25/11/10 10:59:22 Connecting to Authentication Server on 127.0.0.1:443
25/11/10 10:59:22 RegisterSectorServer at IP address 127.0.0.1, port 3500
25/11/10 10:59:46 User 'Orga2' logging in from IP: 127.0.0.1
25/11/10 10:59:46 TCP login link established.
25/11/10 10:59:46 Starting TCP login connection
25/11/10 10:59:46 Login link established to server.
25/11/10 10:59:47 Received account valid from Server
25/11/10 10:59:47 Received account request.
25/11/10 10:59:47 Illegal opcode from Server to Global Account connection
25/11/10 11:00:35 MVAS thread running
25/11/10 11:01:23 TCP connection on port 3805 was reset

Could it be that you have Local Cert checked in the Launcher?

greets

Hexergirl

[Orga1]

Could it be that you have Local Cert checked in the Launcher?

greets

Hexergirl

Yeah I didn't mean to say "auth secure", I meant "local cert" checked but thats correct and with local cert checked it was working the day b4 Thanksgiving holiday. I got tired of thinking without checking local cert, would I crash less? So because of that, switching seems to be working for me atm.

If this debugging is true then could this be one of the reason I never log-in successful the 1st or 2nd time, when I launch the client in awhile. It never fails to freeze as Tienbau says when I haven't launched the client in awhile, on the 1st and second try. I haven't seen a Just-In-Time error, when it freeze or locks up recently compared to past versions of the client. I'm glade Tienbau explained it, thankyou.

[Desidiosusprime]

Well I just installed all the stuff to get EnB going but so far all I can do is get it to go to the in game log in screen. I type in my username and password info and Megan just says my info is wrong. Pretty annoying to hear her say that over and over. Even tried using my brother's information to log in while i had him on the phone as he was able to log in with his info without any trouble, but of course my bad luck held and no dice on the log in. His system is using WinXP so I can't say for sure if that's the difference or not.

After that it was re-install everything but the net7 client since that took awhile to fully update I didn't want to have to go through that again. At this point I'm not sure what the actual problem is. I am using Win7 and opening the programs as admin just to see if that helped. Not that I aboslutely must get back to playing EnB but I thought it would be a nice diversion from WoW occasionally.

[fuulishone]

Are you launching the game from the EnB shortcut or the Net7 launcher one?

[davinci]

Well I just installed all the stuff to get EnB going but so far all I can do is get it to go to the in game log in screen. I type in my username and password info and Megan just says my info is wrong. Pretty annoying to hear her say that over and over. Even tried using my brother's information to log in while i had him on the phone as he was able to log in with his info without any trouble, but of course my bad luck held and no dice on the log in. His system is using WinXP so I can't say for sure if that's the difference or not.

After that it was re-install everything but the net7 client since that took awhile to fully update I didn't want to have to go through that again. At this point I'm not sure what the actual problem is. I am using Win7 and opening the programs as admin just to see if that helped. Not that I aboslutely must get back to playing EnB but I thought it would be a nice diversion from WoW occasionally.

I am having the same issue, but my friend is able to log in on my system, I can not...