As shown at http://www.wowace.com/forums/index.php?topic=13733.20 the crash is happening because WAU is trying to connect to an add server by a name which no longer resolves to an IP address. Until WAU can be updated to not use this server name or better handle the error, we must make that server name resolve into an IP addres. This is done by editing the "hosts" file on your computer.
Launch WordPad from the Start Menu. File: Open, then paste in the following:
Add this line to the end of the file, then click the Save button and close WordPad:
WAU show stop crashing now. To double check your work, open a Command Prompt from the Start Menu (or Start: Run: CMD) and type "ping wdnaddons.com". If you get replies from 188.8.131.52 then it worked.
Vista (less simple)
The host file cannot be edited by a normal user. Instead you must run WordPad as Administrator (which is not the same as being logged in as an administrator).
To do this, find WordPad on your Start Menu, then right-click it and choose "Run as administrator". Follow the XP instructions from there, the rest should be the same.
LOL, That CPA Firm's hosting ISP is probably gonna be like
"WTF?! How'd these guys get so popular all of the sudden?!" :-p
A web server can serve multiple websites using the same IP address. When your web broswer requests a page, it provides the domain name in your address bar. The web server then uses that provided domain to determine where to find the rest of the address your browser requested.
To demonstrate, first apply to change the hosts file as shown above. Browse to wdnaddons.com, and then browse to 184.108.40.206. You should see two totally different sites.
Ultimately I believe it is the same server providing the adds. We are just bypassing the fact that wdnaddons.com no longer resolves to an IP. Since the wdnaddons.com site itself does not appear, I'm guessing their account on that server has been shut down.
The ultimate question is. Why does it craash why is the timeout/reponse not captured and ignored?
From the posts in the thread referenced in my original post, it appears that WUA was written with the expectation that the domain name would always resolve, and therefore no error handling would be needed. It takes a lot of time to create handlers for every possible exception, so it is not uncommon for the less likely scenarios to go ignored. Some call this lazy, others call it efficient.
To be specific, the website is not timing out. The domain name of the website is not resolving to an IP address.
This is actually the IP of wowcompares.com which is what WAU wants, but for some reason trying to access the IP itself redirects to oliverco.com who's IP is 220.127.116.11, which gives an error when you try to reach it. I administrate networks for a living, and SOMEONE has some serious configuration errors in their DNS records...
The most easiest thing for me to do... Is simply move the crash report window out of the way and update your mods just as you usually do. When your done just close WAU, bring the window back into view and click Don't Send... or you can click Send Error Report your call :P
But yea... hopefully this error will have a permanent fix soon.
Kolie pushed a fix. The cause of the exceptions was the DNS lookup failure. The reason for the crash was the exception handler only caught a subset of exceptions, it wasn't a catch-all, it was just a bug - they happen.