75 replies to this topic

[RF Greywolf]

In any case Thank You for finding the issue and trying to get a solution to it. I know that sometimes the bigger battle is finding the cause then the fix.

Once again, Thank You devs!

[Ninthshadow]

GlycerineOxide, on 16 July 2014 - 03:00 PM, said:

Heartfelt apologies one and all

No need to apologise. You've easily been one of the better contributors to the threads I've seen on this.

As for the problem, I'm glad it's been found and a fix seems to be on the way.

At the very least, quantity of conversation during this has been pretty good, I recall in the previous (and now locked) thread we had several blue posts back to back, especially when the thread was running pretty quickly. I definitely appreciate that sort of thing.

I'm looking forward to playing again.

PS. Also yes, This sounds like one of those really painful issues to deal with. I imagine it took a fair amount of effort to sort this out as quickly as it has been. So, a second "Thank you" for sticking with us to the Devs.

Edited by Ninthshadow, 16 July 2014 - 03:25 PM.

[Kyle Polulak]

The official problem is how ISP's break DNS results by returning a record for NXDOMAINS, in fact this is what I named in my first post.

The ISP's in question have a nice 'error page' that shows results from Google (with ads) when a non-existant domain is tried in your browser. We use both a known DNS name and a known failure DNS name to check our response codes. This caused the failure in the patcher. Basically, if your ISP returns search results when hitting this URL: http://thisisadomain...sinesshere.com/ and you experienced the problem with the patcher then this is the cause.

Users on ISP's that don't do this were unaffected at all. Certain ISP's allow users to Opt-Out of these error pages. Virigin Media for instance in the UK has this page explaining their system: http://www.virginmed.../advancederror/

The reason Google DNS/OpenDNS work is because they will not return helper pages by default. OpenDNS has an option to enable but last I remember is that system is Opt-In instead of Opt-Out.

There was an instance of a user with spyware that was redirecting his non-existent domains to an ad heavy search page which we solved with Microsoft Essentials.

[Krist Smith]

Ninthshadow, on 16 July 2014 - 03:21 PM, said:

No need to apologise. You've easily been one of the better contributors to the threads I've seen on this.

As for the problem, I'm glad it's been found and a fix seems to be on the way.

At the very least, quantity of conversation during this has been pretty good, I recall in the previous (and now locked) thread we had several blue posts back to back, especially when the thread was running pretty quickly. I definitely appreciate that sort of thing.

I'm looking forward to playing again.

Thanks for your understanding. It's actually difficult for us at times to post while we're still investigating the problems. Yes, we represent our company, but we do get frustrated when things outside our control don't work as expected, forcing us to adjust our efforts and expectations. I hope a certain amount of understanding can be shared on both sides given the nature of forums.

[Anais Opal]

Krist Smith, on 16 July 2014 - 03:27 PM, said:

Thanks for your understanding. It's actually difficult for us at times to post while we're still investigating the problems. Yes, we represent our company, but we do get frustrated when things outside our control don't work as expected, forcing us to adjust our efforts and expectations. I hope a certain amount of understanding can be shared on both sides given the nature of forums.

Awesome work Krist.

Can I say please check you PM's, I proposed a redundancy solution for you to think about. It does mean alittle more work, but the pay off is worth it if there are further 'uncontrollable' issues.

xoxox

Edited by GlycerineOxide, 16 July 2014 - 03:36 PM.

[J0anna]

Perhaps you should consider having a backup system for patching in the future (like the patch available for direct download from your website). Even if that won't work, I'll chalk this up to "live and learn" while I understand that this problem isn't specifically "yours" and I appreciate all the time and effort you guys are going through, not having a backup plan or "safety net" is something that is completely "yours" and is something I would hope you'll remedy in the future.

[Krist Smith]

Moenrg, on 16 July 2014 - 03:36 PM, said:

Perhaps you should consider having a backup system for patching in the future (like the patch available for direct download from your website). Even if that won't work, I'll chalk this up to "live and learn" while I understand that this problem isn't specifically "yours" and I appreciate all the time and effort you guys are going through, not having a backup plan or "safety net" is something that is completely "yours" and is something I would hope you'll remedy in the future.

As it stands right now, the Repair Tool is essentially our safety net. At the start of this project (lo, those many years ago) I had been planning on a "drag-n-drop" function for applying patches as some have suggested, but this is a difficult approach to secure. It's always bouncing around in my head, though.

At any rate, might I ask that some of you try running the Repair Tool in the game's Bin32 folder at this point?

[Anais Opal]

Krist Smith, on 16 July 2014 - 03:40 PM, said:

As it stands right now, the Repair Tool is essentially our safety net. At the start of this project (lo, those many years ago) I had been planning on a "drag-n-drop" function for applying patches as some have suggested, but this is a difficult approach to secure. It's always bouncing around in my head, though.

At any rate, might I ask that some of you try running the Repair Tool in the game's Bin32 folder at this point?

Check
Your
PMs

easy redundancy solution

[J0anna]

Krist Smith, on 16 July 2014 - 03:40 PM, said:

As it stands right now, the Repair Tool is essentially our safety net. At the start of this project (lo, those many years ago) I had been planning on a "drag-n-drop" function for applying patches as some have suggested, but this is a difficult approach to secure. It's always bouncing around in my head, though.

At any rate, might I ask that some of you try running the Repair Tool in the game's Bin32 folder at this point?

I'll gladly run the repair tool and update this post when it finishes.....

The safety net (the repair tool) worked - thanks for the help.

Edited by Moenrg, 16 July 2014 - 04:28 PM.

[wanderer]

Whelp, that explains why MWO constantly says "The servers are currently undergoing maintenance..."

I thought something had crashed and burned at PGI's end, not that the patcher was to blame for thinking the servers were dead.

[Krist Smith]

This issue has been resolved, all that's required is for you to run the MWO Repair Tool. This tool exists in the game's Bin32 folder. If you installed the game using "Typical" settings, this should be here:
C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin32

An alternate way to find this location is to right-click the shortcut to MWO, and click "Open File Location" (Windows Vista, 7, 8, or 8.1), or click "Properties" and then click the "Open File Location" button in the properties window.

Double click "MWORepairTool.exe". Review the options, change them as you see fit(two-way consolodation means that the tool will delete any files that it determines shouldn't be there, so if you like to keep backups in your game folder, you might wanna disable this option), and then start a scan. Once it's complete, go ahead and click fix. That should do it.

Moenrg, on 16 July 2014 - 03:59 PM, said:

I'll gladly run the repair tool and update this post when it finishes.....

The safety net (the repair tool) worked - thanks for the help.

Thank you for the double-check.

[Ninthshadow]

I can confirm: Repair tool got me in. You did it, way to go!

It seemed to 'hang' on the last file, never quite formally completing but when I ran the Patcher it went straight to "Play" no problem.

Success!

[Krist Smith]

Ninthshadow, on 16 July 2014 - 04:51 PM, said:

I can confirm: Repair tool got me in. You did it, way to go!

It seemed to 'hang' on the last file, never quite formally completing but when I ran the Patcher it went straight to "Play" no problem.

Success!

Very glad to hear it. Happy meching!

[Deepbelow]

Repair tool work for me as well,

Great job

[Deathlike]

I still think the MWO Repair Tool needs to be offered as an official standalone option when the patcher is not working correctly. It would be nice to have it built that way (like the combo PTS+official repair version - which was still a beta product at the time).

Edit:
Also, the updated patcher and MWO build works just great.

Edited by Deathlike, 16 July 2014 - 05:18 PM.

[wanderer]

It's busily patching for me...50 MB file at the moment.

[RF Greywolf]

I am glad to report that ALL SYSTEMS NOMINAL!

Thank you once again Kyle and Krist for the updates. Thank your team for me as well.

[WarGanisM]

Just ran the Repair tool and that seems to of fixed the issue! Would like to thank the Devs/Staff and Glycerineoxide for their efforts throughout this past 24hours.

One thing; I'm a UK VirginMedia user and obviously someone who had the problem, but when I press that link Krist http://www.thisisado...sinesshere.com/ I did not get a ISP related search result, I just get "Problem loading page" Server not found

Firefox can't find the server at www.thisisadomainthatwillnotworkbecauseno-oneiscrazyenoughtostarttheirbusinesshere.com.

Check the address for typing errors such as ww.example.com instead of www.example.com
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

[Tarl Cabot]

Should have seen the mess over at SOE. Someone forgot to pay the piper and they lost their domain name for part of a day this week. Players were having similar issues once it was taken care of, where the DNS cache was not updating everywhere with the renewal.

[Tannhauser Gate]

I avoid anything SOE. Im one of those who lived through the Star Wars Galaxies train wreck of abysmal mismanagement and subsequent hostility towards devoted players. Nothing PGI could ever do by mistake could come close what SOE management did to the paying fans intentionally. Am I bitter? no, I just choose to share my experience and take my money elsewhere.