It did not work. All it did was a) not allowing me to run the game due to missing an XML file and then b) reinstall which let me back at the start.
But considering how many times I already reinstalled, I must admit that any suggestion to re-install without the mention of something fixed server sides seems ......... pointless and stalling.
Key features of the issue:
Red exlamation mark on tab.
Red game version number required in every DLC, even those requiring 1.0
Faliled download at zero percent with no attempt at the patching seems to actually take place.
Now here's the kicker, which I already mentioned previously:
The update files seems to point to a dead CDN URL indicating there's an error here - namely the URI http://na.llnet.bioware.cdn.ea.com/u/f/eagames/bioware/dragonage/offers
I installed a program to monitor my network traffic, because the updater seemed to fail really fast indicating that it was not a timeout. Also because no download was ever initialized it couldn't be a user rights issue - although I did try to run the DA Updater service under a privliged account and with different account settings.
But what I noticed seems to just further underline my supecision that this has to do with the patch server not being located correctly.
So - this is what I saw in the network traffic.
Traffic from my computer to biostore.bioware.com for *.dadmp files
These calls succeeded plus I could open it in a browser.
However in those dadmp files - if you open them up - you see another URI link to the http://na.llnet.bioware.cdn.ea.com/u/f/eagames/bioware/dragonage/offers for the dazip files.
However that URI does NOT open in a browser. Also I can NOT ping the URI plus dnsstuff.com does not seem to have any registration information on this domain.
These things lead me to think that http://na.llnet.bioware.cdn.ea.com/u/f/eagames/bioware/dragonage/offers is NOT the right URI to download dazip files from.
Could you please confirm that the URI http://na.llnet.bioware.cdn.ea.com/u/f/eagames/bioware/dragonage/offers is correct or whether it's incorrect?
Because if it is not correct - it might very well be your problem - if it is correct, I can eliminate it from my own investigation.
After all - it should be pretty straight forward to verify that URI.