![]() |
|
#1
|
|||
|
|||
|
I play on rodcet and am getting the error a lot more frequently now. Anyone else havin this prob? I'm goin nuts.
|
|
#2
|
|||
|
|||
|
Only 11 times in the last week for me...
|
|
#3
|
|||
|
|||
|
just started for me tonight but i'm thinking the servers are comming to a big crash for a time period unknown. I can see something like the servers going down for a few days to try and fix things.
|
|
#4
|
|||
|
|||
|
I have been seeing this for about 3 days, as of 6 hours ago though it has been nonstop for me. I cant play.
|
|
#5
|
|||
|
|||
|
I logged out to do something earlier and neither my husband nor myself can log onto the Tunare server, we've tried restarting our computers and everything, keep getting that darned 1017 error.
|
|
#6
|
|||
|
|||
|
The GMs try to say its your computer, but its not. They suggest doing full file scans and restarting, but that only makes you leave and not come back for 10mins. They have started to admit its serverside (when chat goes from 1, to 6 different generals), but still they say its your fault, even though the definition of the 1017 is an overload of the server. You can usually notice slow zoning and 5 mins to do a /who all or /tell before hand, and then you just gotta try not to zone...
|
|
#7
|
|||
|
|||
|
Got flooded with 1017s today on RN
|
|
#8
|
|||
|
|||
|
In some ways I'm glad to see it isn't just a problem with the Bristlebroke server, but in other ways that means a lot more people are suffering through 1017s
![]() Sad to spend $13/month, finally get time to play, and then be stuck not able to logon due to 1017 errors. |
|
#9
|
|||
|
|||
|
Rodcet has been horrible as of late.
During raids half my guild get's booted on zoning and then it takes 15 to 30 mins for them to get back in. Other strange things: Had a person agro a mob in the Vah Shir City.. mob couldn't be targeted but was also not causing any damage. Three NPC where hitting it to no avail. The person fighting it had a pet on it but it too wasn't doing any damage. While hunting my Zerker in the castle in Lake of Ill Omen, me and a friend of mine experenced some "auto pulling". We were in a relatively safe area but mobs started popping on top of us. It was real fun at first, but then it got to be silly... then deadly. We had a total of 8 mobs on us at one point in time. It was similar to what happens when a mob runs and agros the zone and mobs start popping, but we didn't have any mobs get away (love snare) and the "auto pulling" was to sparatic. Then I died and my friend went LD and I went LD while zoning to my bind spot. After that the problem went away. |
|
#10
|
|||
|
|||
|
The only thing that I found to help this problem (I am not saying it is a fix, it may be only coincidental, dunno) has been this:
1. Log out completely from EQ 2. Restart EQ, and make sure the autoplay box is unchecked 3. Do a complete file scan 4. Keep the autoplay box unchecked and hit "play" manually Like I said, I don't know that this is any form of actualy fix, it just works for me. I had quite a few 1017 errors a couple months ago, and haven't had one since, and that is the only things that I have changed on my PC. EQ is all I use that one for, so no other settings have been adjusted. Good luck, 1017's blow. |
|
#11
|
|||
|
|||
|
I Concur with Zergy. the only way to cut down the amount of 1017 errors is to exit completely and do a complete file scan this always gets me in without the 1017 error. I think it is also quicker to do that than to keep punching play until you get in. Hope this helps you all out it always helps me
![]() |
|
#12
|
|||
|
|||
|
Quote:
I know several guilds who have stoped raiding because of this. |
|
#13
|
|||
|
|||
|
I did run a complete file scan last night and I was missing some files. Albeit they were Stonebrunt Mnt files.
I don't use the autoplay feature and I tried to log in last night after about 30 mins to no avail. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|