Could not successfully retrieve new file xxxx.xxx (-100)

sikk · Post by **sikk** » Fri Sep 11, 2009 11:03 pm

Hello,

Just registered for WinEQ 2.0 Pro. Had used WinEQ in the past and juyst got back into boxxing after a return to EQ a few months back.

I am using 64bit Vista with a ping time of ~280mS to lavishsoft.com (I'm in Australia). I'm on a ADSL2+ service here (24Mb I think) which is rock solid usually.

Upon install (as admin) I launch WinEQ 2.0 Pro (as admin) and the patcher starts. After a brief period the patcher window goes white and after a while (say 3-5min, sometiimes longer it seems) I see a dialogue box which says

Code: Select all

Could not successfully retrieve new file xxxx.xxx &#40;-100&#41;. Aborting patch. You may countinue to use this software.

on hitting OK I get the following

Code: Select all

Connection to Lavish Software license server failed. The server may be inaccessible to you at this time, or the amount of network lag between you and the server may be extrordinarily high.

If I rerun the login repeatedly it seems to gradually get through each file progressively, but this takes ages - time which I don't want to deal with

I have done the following things

1. ping lavishsoft.com

Code: Select all

ping lavishsoft.com

Pinging lavishsoft.com [208.64.39.116] with 32 bytes of data&#58;

Reply from 208.64.39.116&#58; bytes=32 time=293ms TTL=42
Reply from 208.64.39.116&#58; bytes=32 time=293ms TTL=42
Reply from 208.64.39.116&#58; bytes=32 time=292ms TTL=42
Reply from 208.64.39.116&#58; bytes=32 time=294ms TTL=42

Ping statistics for 208.64.39.116&#58;
    Packets&#58; Sent = 4, Received = 4, Lost = 0 &#40;0% loss&#41;,
Approximate round trip times in milli-seconds&#58;
    Minimum = 292ms, Maximum = 294ms, Average = 293ms

2. Turned off my firewall

So. DNS is not busted, and ping times and packet loss do not seem to be an issue.

Would a transparent proxy affect the patcher? Should I look there? Right now patching is working ever so slowly but getting there, I'm watching the patch files land in the Win EQ 2.0 folder one by one, the errors still continue though.

Any suggestions?

Post by **Lax** » Fri Sep 11, 2009 11:21 pm

Would a transparent proxy affect the patcher? Should I look there? Right now patching is working ever so slowly but getting there, I'm watching the patch files land in the Win EQ 2.0 folder one by one, the errors still continue though.

I would definitely try without it if you're using one

sikk · Post by **sikk** » Fri Sep 11, 2009 11:29 pm

Lax,

Thnaks for the prompt reply.

No - I am not using a transparent proxy - however it may be possible that my ISP is. Seen this type of behaviour before?

sikk · Post by **sikk** » Sat Sep 12, 2009 12:27 am

Lax

Getting nowhere here. Rerunning is not successfull.

What diagnistic woulf you have me perfrom.

As some further info. I ran up WinEQ 2.0 and Wireshark in a test VM to look at network traffic. I am seeing data exchange going on port 11500. When the time out occurs i see FIN, ACK frames, which seems to be the client dropping the connection.

In the stream I see some frame retransmitts, a few lost segments, and teh odd dupe ACK, which is not ideal. Other TCP sessions (file dl for example) on the same VM proceed without these types of errors. Is it possible that these TCP errors ar ethe source of the issue?

Any chance you can released a packaged version rather than a patcher driven release?

Post by **Lax** » Sat Sep 12, 2009 9:23 am

Here is a full download for you. Every once in a while I get someone with a busted-ass PC like yours who needs a complete download

http://www.lavishsoft.com/downloads/WinEQ2-20090820.zip

sikk · Post by **sikk** » Sat Sep 12, 2009 5:21 pm

Lax,

Thanks mate.