lotro - Isengard patch fails w/ pylotro

tparker · Post by **tparker** » Mon Sep 26, 2011 2:48 pm

I'm using pylotro 1.1.15a, game has been playing fine but I have been
trying to start the Isengard update patch and pylotro will not connect
to the server. The server is active and all the windows clients in the
house can connect to it fine.

message from patch attempts:

Connecting to patch.lotro.com:80

Connection to patch server failed error code: 0x80041003
Failed to connect to the patch server: OEC_E_CONNECTIONFAILED(0x80041003)

Connecting to patch.lotro.com:80

Connection to patch server failed error code: 0x80041003
Failed to connect to the patch server: OEC_E_CONNECTIONFAILED(0x80041003)

Connecting to patch.lotro.com:80

Connection to patch server failed error code: 0x80041003
Failed to connect to the patch server: OEC_E_CONNECTIONFAILED(0x80041003)

*** Finished ***

I have checked in the options tab and tried to re-save the patch dll
(patchclient.dll) like we had to in older version of pylotro and I
still got the same message.

I have not been able to find anything on google for this and the appdb
page is pretty outdated.

bcpeterson · Post by **bcpeterson** » Mon Sep 26, 2011 6:56 pm

Both the codeweavers forum and the lotro forum have even windows users having problems patching.

http://www.codeweavers.com/compatibilit ... msg=112146

Their patch server is getting slammed. =(

At this point it isn't pylotro or wine. Good luck getting connected. =)

tparker · Post by **tparker** » Mon Sep 26, 2011 7:10 pm

I re-downloaded and reinstalled both pylotro 1.1.15a and
patchclient2.dll. Pylotro was then able to connect to the patch server
and says that it has completed patching:

Connecting to patch.lotro.com:80

checking data...
data patches: 0 bytes to download: 0
unlock: 0 empty: 0
result code: 0x00000000
Patching data:

Data patching complete.
All patching complete.

*** Finished ***

I have gone through that step multiple times to be sure there is not a
series of patches that I need to rerun pylotro to get through.

However when I log into the game I get a pop up error box saying:

'connection failed. you do not have the current version of the client
installed.'

I am not sure if this is something in pylotro that does not pass the
update information for the new expansion on to the servers properly or
if this is a wine issue. I did notice the the people around me on
windows computers had a new EULA to agree to and I did not get one so
far in my process. Again, I do not know if that is part of the issue.

I'm asking here because the appdb instructions for installation uses the
pylotro launcher as a work around to the native launcher and it is
likely that problems with it will end up as wine discussions anyway.

tparker · Post by **tparker** » Mon Sep 26, 2011 7:28 pm

On 09/26/2011 07:56 PM, bcpeterson wrote:

Both the codeweavers forum and the lotro forum have even windows users having problems patching.

http://www.codeweavers.com/compatibilit ... msg=112146

Their patch server is getting slammed. =(

At this point it isn't pylotro or wine. Good luck getting connected. =)

I had thought that was probably the issue as well, but now everyone on
the lotro forums using pylotro has been able to patch but not connect.
Everyone seems to be getting the same 'connection failed. you do not
have the current version of the client installed.' error that I did
after patching and the log in servers are not overloaded, at least the
three windows boxes in the house can log in to servers fine with no wait
or queue. Granted, paid accounts on low pop servers may play into that
but those same accounts get the fail error in Linux.

Is there a way to tell if the command line parameters sent to the
servers from the launcher are handled by pylotro or through wine? If
it's pylotro then we may may be stuck until it is updated to send the
correct info for the expansion, but if it's wine maybe we can patch it?

tparker · Post by **tparker** » Mon Sep 26, 2011 9:01 pm

It looks like pylotro may only be grabbing the .dat files and nothing
else. A poster on the Lotro forum post for this issue says they were
able to copy the .dll, .exe, etc. over from an updated windows box and
everything worked. I am in the process of copying a windows game folder
over to my linux box to test that.

tparker · Post by **tparker** » Tue Sep 27, 2011 9:13 am

On 09/26/2011 09:59 PM, tparker wrote:

It looks like pylotro may only be grabbing the .dat files and nothing
else. A poster on the Lotro forum post for this issue says they were
able to copy the .dll, .exe, etc. over from an updated windows box and
everything worked. I am in the process of copying a windows game
folder over to my linux box to test that.

Just adding this in case anyone comes looking later:

Pylotro seems to be grabbing one of the three needed 'chunks' of patch
at a time, and not always seeing there is more. Some people on the Lotro
forums have been able to continually rerun the patch process, sometimes
taking many tries, until it manages to find and complete all three
chunks. Others have patched a windows install and copied the Lotro
folder from that to overwrite their wine Lotro folder (inside user/drive
c/program files/turbine).

Even this morning with the servers no longer overloaded (no time outs,
delays, or drops) I was not able to get the patcher to grab anything
else, it still insisted it already had everything but the game said I
was out of date. I was able to copy from windows and have verified that
as working with no obvious issues in Wine 1.3.28.

bcpeterson · Post by **bcpeterson** » Tue Sep 27, 2011 10:47 am

Glad that worked out...for the most part pylotro works great but I think Turbine has been made some changes to their launcher which makes the patching not work as well. The teleport screens are a good example of this, and who knows what else has changed.