Very interesting. I have two collector's edition accounts and on both I get the same error but on a newly created f2p account I don't have any issues and I can log in without any issues.
Yeah. They've messed up something relating to existing/older accounts. This is becoming clearer as people post.
My account is a veteran's one from the subscription days - I bought six months in advance, that's how old it is. Whenever there's a problem with routing or servers I'm always affected by it. The problem is always resolved but it's a bit annoying. And that's all it is, really, an annoyance.
The heads up to anyone with an older account when events are announced is not to spend any money - you may well find yourself locked out. Repeatedly. I do feel for people who bought Club for this server and I hope you get reimbursed.
This classic server owes me nothing so I can't really get too upset about it, but there are plenty of people who broke out their credit cards to support it...
Prior to the maintenance I *was* able to log in.
The only firewall I have is Defender built in to Win10 - I turned it off. I deleted the SSN files.
The result?
Hey everyone!
Just to briefly let you know that we're aware of the issue, and that it's not something newly introduced with the previous maintenance
Ummm... it clearly is. Many of us had no problems pre-patch (I was happily bombing things on the Isle of Dawn) but post-patch we can't log in. Just to make it absolutely clear, when you launched the classic server I created a new character and went on a happy nostalgia trip to around level 11.
Then GF patched the game. End of nostalgia.
It *is* something introduced with the previous maintenance, obviously.
I know you'll get it fixed but something didn't randomly happen on my PC. The patch happened.
IT Support - not a job I'd ever want!
I'm giving up on this for the moment, but my game installation can't see the servers:
Was really looking forward to this but, sadly, it will have to wait for another day - nothing I have tried will fix this issue at my end and it looks like another of those GF connection bugs which occur from time to time. The good news is they always fix them - the bad news is it can take a while!
It does seem to be the same accounts that get hit by this - I got whalloped with it at the end of last year too (link):
Display MoreHey everyone!
Just to briefly let you know that we're aware of the issue, and that it's not something newly introduced with the previous maintenance (so we cannot do a roll-back unfortunately).
That being said, it being an account specific issue, we're trying to pin-point the exact cause, and have also contacted the developer to get their expertise to solve it.
We're sorry that a portion of our players are unable to access the Classic Server, and will do our best to let you know once we have a viable solution at hand, though this might not be in the immediate future
Thank you for your continued reports - please also make sure to create a support ticket, so we can gather all the affected accounts to better pin-point the cause of this disturbance!
Atmorph
Hi Atmorph - There are quite a few of us who can hold our own with IT issues. Would it possible for you to share with us what the utterly nebulous 'Termination Code 2' means in the real world? Some people have fixed this themselves by deleting cached files but it hasn't worked for me or many others. If you could be more open about what the fault is, perhaps we could find a fix at our end?
My installation, like many others, was fine pre-patch. Post-patch it's broken. We're just really slinging around ideas but the fix is going to have to come from GF.
I was thinking more of redirecting that request to localhost with a copy of that file on my pc. At which point I figured I'd have to run WAMP or XAMP or similar to serve it and it's getting beyond silly. It's not a fix that could be easily shared amongst forum readers, even if it worked.
Right - so something has been saved locally to our pcs which is messing it up. Gah. 
Which means it might be fixable in the hosts file.... just trying it.
I've tried the usual - DNS flush, ip reset, nothing works. We're going to have to wait for this to be patched again I think. Deleting the server presets doesn't help either - something is going wrong between our clients and the server list and I don't think we can do anything to fix it, sadly.
This is the output from the log - it doesn't look like a problem at my end, so I can't imagine it's a problem with anyone else's pc or connection:
Well, it was all working ok prior to the patch and now I've picked up the error that a lot of other people have reported - Termination Code 2. I've tried all the suggestions offered on the forum and nothing has worked.
Anyone got any additional thoughts on this, or is my time on this server over already?!
(Sorry - in wrong forum - apologies)
This is one of those routing problems that crop up from time to time. If you get it (as I have, again) there is very little you can do about it but the mobile phone trick does work for some. It's just completely random, country independent, ISP independent and if your game tries to route you through you the failed hardware...unlucky. Always seems to happen at the end of events though, although I suspect that's confirmation bias on my part.
@niathecake you should find your account isn't blocked. I tried a VPN before, got the same message, and as soon as I turned it off my account was unlocked - I hope that's the case for you.
Three or four times a year this happens. It's a free game, tech support goes home at the weekend, but if you were just short of completing event requirements it could be a little frustrating. They'll sort it out on Monday but expect it again in three or four months time. Shrug.
