Short-term solution for the 1017 Error

F

Feroce

Dalayan Beginner
Hey, I've been plagued with this 1017 error for a while, and I seem to have stumbled upon a fix. This is NOT a permanent solution, but it does the trick.

I noticed that I had no troubles with the 1017 error when I first installed the SoD files and ran the patcher. Once it started hitting, though, I couldn't get in. So here's what I did:

1. Deleted files.txt
2. Went to the Manual Download Patch Files thread at http://forum.shardsofdalaya.com/index.php?topic=8036.0 and downloaded the full patch.
3. Keeping the zipped folder open afterwards, I extracted the files to my EQ install directory.
4. Ran the SoD patcher, hitting "repatch all" in the advanced menu before I hit "Patch and run".

At this point, I can log in with no 1017 error. Now once every few zones, I crash to the login screen, and the 1017 error usually pops up. When it does, since I kept the zipped folder, all I have to do is steps 1, 3, and 4. It takes a few minutes, but it fixes the problem, at least until I crash to the login screen again.

This has changed 1017 from a game-breaking bug to an annoying hassle. I have no idea why this works, but it works.
 
Sorry if I sound like a complete ass, but I don't think this remedies the error, the full patch download is old and repatching them basically overwrites those files anyway. I think the 1017 error is tied to latency + timing on both ends, and not a messed-up file. It seems to be a hit or miss situation.
 
You may be right; I don't understand the error or why it happens. But I do know that once it pops up, I can't get in again until I do what I outlined above . After getting the error, I've tried 15 times over 24 hours without success. Then I did the above-mentioned trick, and I got in on the first shot.

Since then, I've crashed to the login 3 times and gotten the 1017 error. All three times I did this, and all three times I got right back in afterwards.

If it's a coincidence, it's a peculiar one. I don't doubt that latency issues set this error off, but the persistent nature of the error after the first crash to the login screen suggests that there's something else at work.
 
1017 is just a general time out error. The client has a set amount of time that it attempts to contact the server, if it takes too long you get the 1017 errors. High server load will attribute to more frequent 1017 errors, just be patient and eventually you'll get in, unless you have a really poor/slow internet connection.
 
You're right, Xardon. I should have been more specific.

I'm referring to a persistent 1017 error I've observed that happens even when there are less than a hundred people on. Now I have no real doubt that latency issues are what trigger this, but there is some other factor at play here that continues to hit me with these 1017's until I do what I outlined in the original post.
 
Sometimes rebooting your computer as well as your Cable/DSL modem and/or Firewall/Router (depending on your network setup) can also help eliminate connection issues.
 
I've tried that when I get persistent 1017 errors, without success.

You should know that while the internet connection I have is decent, it is on the far side of the planet, so latency can be an issue. That explains why I have frequent crashes upon zoning, but not why I get this persistent 1017 error after the initial crash.
 
I'm on the other side of the world too, and I've been getting consistent 1017 errors. I've been waiting on a set of replacement titanium discs to come in the mail so I can reinstall, but I think if I tried your fix it just might work. I'll try it.
 
Addendum to this... I have noticed over the last several days that I haven't had to do this as much. I'm usually getting in as long as I keep trying (10 tries is my limit, after that I do this trick again). It does make me wonder if it isn't just about latency after all, since the patcher is very fickle from this side of the planet, and only likes to work during certain hours when the connection speeds are generally good.
 
You must log in or register to reply here.
Back
Top Bottom