The SSSE form of the eqgame.exe error and cause

[Vastlee]

If you succeed Dark, it would be greatly appreciated if you share your success. I'm on my 12th today...

[indigoblue]

This error is driving me crazy..I've got my fingers crossed you can figure out what's going on!!

[Gopdar]

I think that I may have found a solution. Ever since I made the following modification to my eqlsPlayerData file I have yet to receive the error. Here is the contents of the file:

[MISC]
LastServerID=28
LastServerName=[0.7.0] [PEQ]The Grand Creation [legit-luclin]
HasReadSWarning=true
HasViewedWebOrder12864=true
HasViewedWebOrder297546304=true
WebOrderViews297546304=0
HasViewedWebOrder339489344=true
WebOrderViews339489344=0

[UI]
XMLFilename=EQLSUI.xml

[CHAT_OPTIONS]
PlayerNameColor=-1
PlayerChatColor=-6768006
GuideNameColor=-7021579
GuideChatColor=-7691265
AdminNameColor=-569803
AdminChatColor=-1807589
TellColor=-16715776
CommandColor=-16527105
SystemMessageColor=-1
FontSize=3

[PLAYER]
Username=
[NEWS]
LastViewed=-1709800869

All that I modified were the parts in the [MISC] section that said anything about WebOrder to true. Hopefully this works for others.

[Dralanna]

That did not work for me... still getting the error.

This error is definitely on the server, not on your machine.

Note previously in the thread

Agreed, I have 5 machines. The accounts that are "immune" are so on all machines.

[indigoblue]

I tried the fix also, no luck. Although I'm happy it fixed yours for you!!

[zuperzip]

There is a work around that a player by the name of Blasticus on PEQ recently discovered and told us about. At one point I thought accessing a webpage while simultanously logging in would prevent an SSSE but couldn't get it to work the majority of the time. Blasticus tried using a speed test and found it worked very well and so have I. Here is what works for me, open the EQ client and type in your username and password in windowed mode so it is ready to go. Now find any speed test website with your webbrowser (I've been using performance.toast.com or infospeed.verizon.net) and get ready to start the speed test. Start the speed test then switch to the EQ client and quickly log in.

What's important is you 1) start the EQEmu authentication process and 2) get past the server select screen _while_ the speed test is downloading its sample.

It also apparently works if you do the speed test on another system that uses the same router as your EQEmu system.

Hair brained? It sure is... but it works so well for me during a meteor shower of SSSEs that it's more than just dumb luck. I suppose if I want to figure out why it works I'll need to put my nose back into packet sniffing.

[Chewbenator]

Speedtest fix doesn't work for me, but deleting the client files does, very tedious to reset my key sets and resolution though.

[Goggin]

First of all I'm sort of a newb, so this probably doesnt mean anything...

But I noticed after I deleted my client data (as described above) and tried to log in, it gives me a VERY brief error message before crashing. The only reason I was able to see it is by doing a print screen:

"Sorry %3, you already have the maximum number of active tasks"

Any ideas?

*P.S. Almost positive that this has something to do with me deleting the wrong file, but I thought I'd post it anyway just in case. Going to reinstall EQ and see if I get the same thing.

[Vastlee]

Uggh... and it begins. As I mentioned before in this thread please do not post if your symptoms do not match the original post 100%. Already the other crash type posts are starting.

Are there any devs that happen to be reading this thread? I'd very much like to hear their input on the survey packets being sent theory.

[Dralanna]

I'm guessing that people are having luck with the speed test trick because it uses a lot of bandwidth and is probably delaying the survey packet long enough for you to login.

Did anyone trying this also do a packet capture?

[KileSmith]

after altering the eqlsPlayerData file to be exactly the same as Gopdar, it didn't stop the error from occuring. However, it doesn't do it nearly as often, and i can generally get in after 2 or 3 tries...