I've reinstalled from Direct2Drive twice and the EA Download manager twice and I keep getting the same message when I try to play the game. The launch screen comes up and the music starts but when I hit "play" I get:
AWC.dll
The game cannot launch because of a misconfiguration. Please reinstall your game and try again.
Anyone else have this problem and if so did you get it fixed?
Anyone get this: The game cannot launch because of a misconfiguration.
Débuté par
kentrat
, nov. 10 2009 06:29
Retour en haut
#2
Posté 10 novembre 2009 - 06:31
JironGhrad
-
- Members
- 1 657 messages
have you run the configuration utility? and had it scan for your hardware?
#3
Posté 10 novembre 2009 - 06:54
kentrat
-
- Members
- 3 messages
Yes. It scans and there doesn't seem to be any problems but I keep getting the message.
#4
Posté 10 novembre 2009 - 06:55
JironGhrad
-
- Members
- 1 657 messages
has it ever run correctly? and did you install the patch?
#5
Posté 10 novembre 2009 - 07:21
kentrat
-
- Members
- 3 messages
It has never run correctly. I installed the patch and got the same message. I've found other forum discussions with people who have experienced the exact same problem but there does not seem to be a difinitive solution.
#6
Posté 14 décembre 2009 - 01:13
darue.keller
-
- Members
- 1 messages
just started getting the same problem after applying the 1.02 patch. rescan and save with the config tool does nothing. have reinstalled and repatched and the problem remains.
#7
Posté 14 décembre 2009 - 02:52
Cazien
-
- Members
- 2 messages
I found a work around for this. You have to run EACORESERVER first, then promptly run Dragons exe. I just made a shortcut of eacoreserver app. A minor pain, but it works
#8
Posté 16 janvier 2010 - 04:50
deChetwode
-
- Members
- 1 messages
#9
Posté 19 janvier 2010 - 06:18
JackFirelake
-
- Members
- 13 messages
Cazien wrote...
I found a work around for this. You have to run EACORESERVER first, then promptly run Dragons exe.
That's the only way I can launch the game, too. Not much of a problem once you know it, but it took me 5 hours extra just to get the game running in the first place. I wish BioWare would keep the hell away from EA in the future. I know this was the first, last, and only game I buy through EA store. (hint hint BioWare)
#10
Posté 19 janvier 2010 - 06:34
Gorath Alpha
-
- Members
- 10 605 messages
Bioware's owners sold their company to EA about a year ago.
#12
Posté 20 janvier 2010 - 03:29
Valaskjalf
-
- Members
- 283 messages
JackFirelake wrote...
Cazien wrote...
I found a work around for this. You have to run EACORESERVER first, then promptly run Dragons exe.
That's the only way I can launch the game, too. Not much of a problem once you know it, but it took me 5 hours extra just to get the game running in the first place. I wish BioWare would keep the hell away from EA in the future. I know this was the first, last, and only game I buy through EA store. (hint hint BioWare)
Something may be wrong with your EACore_App.ini in the Dragon Age/Bin_Ship folder. Make sure all the paths are actually pointing to real programs.
If thats ok, check your localhost. run CMD and type "ping localhost -4" . It should ping 127.0.0.1. If it doesn't you need to reset your hosts file.
#14
Posté 12 février 2010 - 11:53
ShrinkingFish
-
- Members
- 1 214 messages
Cazien wrote...
I found a work around for this. You have to run EACORESERVER first, then promptly run Dragons exe. I just made a shortcut of eacoreserver app. A minor pain, but it works
Thank you so much for this work around. I've been trying to figure out the fix for this for a week. I made the mistake of submitting the question to their customer support and hoping for a timely response. That'll teach me.
Thanks again. Big relief.
#15
Posté 18 mars 2010 - 05:02
hachibushu
-
- Members
- 2 messages
Has anyone heard a response to this issue? Running the eacoreserver then daorigins.exe works for me, but it is a pain...
#16
Posté 11 août 2010 - 04:24
killed-bill
-
- Members
- 1 messages
I've experienced this problem, having purchased the game from D2D too, it seemed to happen when I patched to v1.4 from 1.0. The tip from Valaskjalf helped (thank you). Hopefully this will help someone too...
I uninstalled the game but kept EA installed, I then did a fresh download and install of Dragon (from EA's Download Manager used the serial supplied by D2D) before I did so, I made sure all elements had been removed including reg settings. When I installed Dragon I made sure to keep the default installation settings rather than my usual custom directory setting - this sealed the deal.
Have now also updated to 1.4. I rely on launching the game from EA - which isn't a problem for me - so long as it works!
All the best wise ones!
I uninstalled the game but kept EA installed, I then did a fresh download and install of Dragon (from EA's Download Manager used the serial supplied by D2D) before I did so, I made sure all elements had been removed including reg settings. When I installed Dragon I made sure to keep the default installation settings rather than my usual custom directory setting - this sealed the deal.
Have now also updated to 1.4. I rely on launching the game from EA - which isn't a problem for me - so long as it works!
All the best wise ones!
Modifié par killed-bill, 11 août 2010 - 04:41 .
