1017 Error Resolution < 50/50 chance this will work for you >

I managed an account " Lightweight Directory Access Protocol", occasions I would get clients getting errors and giving them a quick fix so they can access the protocol they want.. I would send them a reset password link to their account. ... I figure why not do this to my account here..

From the Client Window.. I clicked the link to forgot ID/Password , I reset my password and changed it..

1 minute later after changing the password. I was able to get the Que wait window, at 77 list and I logged in.

I'm not saying this will work for you but it worked for me..

Ive been trying to log in since 10am EST

3 minutes + now , logged in

oh shit it worked

Grats lol, pass it along

ddint work

eh.. that's only managing your account with SE AM... has nothing to do with moving you up the queues for the game worlds. You authenticate with SE AM in the launcher, before you go into the lobby and such.

Nice try though.... might have worked if the authentication was handled closer to the actual servers hosting the world.

I don't understand how this will lift the cap that has been reached on my server. Care to elaborate on the internal mechanics that is supposed to allow this to work? If the server is full then isn't it, you know, full?

Quote:

---

Originally Posted by Arminus

I don't understand how this will lift the cap that has been reached on my server. Care to elaborate on the internal mechanics that is supposed to allow this to work? If the server is full then isn't it, you know, full?

---

It doesn't. Not only are the issues with servers in different subnets, for NA/EU, they are in different countries as well. Initial authentication and such is queued in a separate process in the launcher before you go to game launch. If the issue were an authentication with SE AM prior to going to the lobby, this could be a valid thing to try to get higher priority in THAT queue. Unfortunately, we are talking a different server and queue problem.

Tried it, tested it, does not work. Move along people.

Quote:

---

Originally Posted by Arminus

I don't understand how this will lift the cap that has been reached on my server. Care to elaborate on the internal mechanics that is supposed to allow this to work? If the server is full then isn't it, you know, full?

---

Some implementation of LDAP services force a immediate propagation when something in the account changes. Usually the default propagation frequency is fast enough for normal small business network. For large enterprises that has many geographical locations, multiple network segments, along with replicating directory services (Active Directory from Microsoft is one example), propagation can take longer. When communication problem occurs, local reference controllers can go out of sync. Changing a password is a quick (and dirty) way to force a re-sync.

Mechanically, it should *NOT* enable you to login all of a sudden. Unless something was wrong with the local reference to begin with. If this is indeed the problem, they have bigger issues than 1017.