Update Failed

[Wargasm 1,927]

Posting this on behalf of a villager that I've been trying to help fix this.

 

She downloaded a brand new 64 bit wurm launcher (she uses Windows 10).  After installing, it writes to her Wurm folder, creates a desktop icon, and launches when the installation screen finishes.

 

The launcher pops up, and says "Update failed" at the bottom.  I noticed she had 32 bit and 64 bit Java installed, so I uninstalled 32 bit.  I also looked at the properties of her desktop shortcut (to make sure it wasn't old) and it was pointing to the correct folder.  Even navigating to the folder and clicking the "WurmLauncher64" file results in the same "Update failed" error.

 

Please help   I don't know what else to do.

[Brash_Endeavors 4,735]

 does it also say (Error: Error opening connection to patch server) like this

(this is an older version of the launcher):

 

 

 

Some old threads, might not be same issue, generally it was a DNS or network error and they eventually resolved on their own but it sometimes took most of a day.

 

It's frustrating for those unable to connect, as other people seem to have no issue, and generally is an issue between their ISP and the server, resolving DNS or other issues.

 

edit: the patch server seems to be different from the games+login servers and  the server where you download/install clients or use forums/wurmpedia. It has periodically been the source of frustration for players in specific areas/regions/ISPs who are affected while the bulk of players are not affected, possibly due to periodic changes in DNS lookup. Some ISPs will catch on immediately, others take hours or even days to catch on to the new address.

 

 

 

 

Edited December 7, 2019 by Brash_Endeavors

[Wargasm 1,927]

So, just install the game, if I see that error again just wait 3 days?

[Brash_Endeavors 4,735]

 

I don't know. it could well have been a very temporary problem that is already fine again now.

 

The majority of "can't update' because of  error opening connection to patch server will eventually resolve on its own, but should never take 3 days. Did we confirm that was the actual error message?

 

Maybe also check the HOSTS file in systems32/drivers to make sure it makes no reference to wurm patch server. Some people edited that to resolve a past problem, and now they are stuck with being permanently redirected to a non valid address.

 

[Wargasm 1,927]

Yeah, she's still getting the same thing...

 

 

I checked her system32 folder, I don't see any "Wurm" related .dll file or anything... I even went so far as to search the directory for "Wurm" and got nothing.

 

One thing I did notice is that I installed the game to C:\Users\Public\Wurm Online  , the game threw an error saying that the C:\Users\Public\wurm\Wurm Online folder didn't exist, so I had to reinstall it in the proper place.  That leads me to believe that some reference somewhere on her computer is set wrong.

[Wargasm 1,927]

Also, trying the "generic JNLP" client, I get this:

 

Unable to Launch the Application...

 

java.net.SocketException: Address family not supported by protocol family: connect
    at java.net.DualStackPlainSocketImpl.connect0(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
    at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at sun.net.NetworkClient.doConnect(Unknown Source)
    at sun.net.www.http.HttpClient.openServer(Unknown Source)
    at sun.net.www.http.HttpClient.openServer(Unknown Source)
    at sun.net.www.http.HttpClient.<init>(Unknown Source)
    at sun.net.www.http.HttpClient.New(Unknown Source)
    at sun.net.www.http.HttpClient.New(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
    at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
    at com.sun.deploy.net.BasicHttpRequest.doHeadRequestEX(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.checkUpdateAvailable(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.isUpdateAvailable(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
    at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
    at com.sun.javaws.Launcher.launch(Unknown Source)
    at com.sun.javaws.Main.launchApp(Unknown Source)
    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
    at com.sun.javaws.Main.access$000(Unknown Source)
    at com.sun.javaws.Main$1.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

[Wargasm 1,927]

Here's the "error" for the missing/broken directory...

 

[Wargasm 1,927]

Thinking about it more, there must be some pointing reference somewhere that is broken.... otherwise, how does the launcher know her account name without me filling it in every time I install?

[Brash_Endeavors 4,735]

17 hours ago, Wargasm said:

I checked her system32 folder, I don't see any "Wurm" related .dll file or anything... I even went so far as to search the directory for "Wurm" and got nothing.

 

 

it's not a wurm file or wurm dll in system32 -- in the past, a few people tried to fix the error 'cant connect to update server" by editing their Windows HOSTS file.  The reason was because the wurm update server changed its DNS address, their ISP could not locate the wurmonline update server due to a DNS address change, and rather than wait paitiently for their ISP to eventually catch up with the new address,  they would hand edit the HOSTS file to point to the new IP address. It was an easy shortterm fix that would get them back into the game quickly, but cause longterm issues because the next time the server changed its DNS address again, (and eventually it would change again), they would now be pointing to the wrong address, and their ISP could no longer resolve the address on its own because they had hand edited  the HOST file to always point at a static address. 

 

It's perhaps UNLIKELY this was the case here, but if say a year or two ago they had a similar issue with connecting to the update server, and someone suggested they edit the HOSTS file, it could prevent them anytime after that from resolving the address naturally.  So a long shot thing to check would be, open the HOSTS file with notepad and make sure that HOSTS file did not mention wurm anywhere. 

 

If you are not sure what any of that means, I would just skip all that.  I think I am making it more complicated and hard to understand, and I suspect this is not the issue  if it is also complaining about the Wurm install path being broken.

 

______________________________________

 

 

I always hate to see Wurm or other games installed to system paths like  C:\Users\Public\wurm\Wurm Online   -- sometimes windows gets really nasty about letting "protected system folders"   get changed or updated. 

 

If it were me, I would probably completely uninstall, check the registry for any wurm references and clean those all out, then make a NEW install path someplace like:

 

C:\games\Wurm

or 

D:\Wurm

 

and do a fresh install to a location like that. And also make sure it is not doing /wurm/Wurm Online/ -- no need to have a wurm folder and then a Wurm Online folder inside it -- just one or the other.

 

______________________________________

 

However, it sounds like there may be more than one issue.

• It cannot connect to the update server (usually a network connection issue, and not directly related to the installation path)
• second and unrelated,  is not being able to find correct directory, or looking in multiple places for files, which sounds like probably multiple installations in the past that are now confusing everything. 

 

 

 

Edited December 9, 2019 by Brash_Endeavors

[Brash_Endeavors 4,735]

You could also check this thread, it mentions the same error of java.net.SocketException: Address family not supported by protocol family: connect and they eventually resolved it:

 

 

 

Edited December 9, 2019 by Brash_Endeavors