Aller au contenu

Photo

Unable to Launch


14 réponses à ce sujet

#1
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
Hi everyone - to help coordinate the clutter, I'm creating a series of official sticky threads covering major issues.

This is the official thread for any issues that are preventing you from LAUNCHING the game. If you're experiencing such an issue or have a solution to such an issue, please post and discuss it here.

Thanks!

UPDATE [March 12, 10:20pm MST]:
Thanks for your patience everyone. We released a BETA patch this afternoon that fixed a number of these release-control related issues as well as an issue where the game would ask for non-existent drives. Also, we have further updates and workarounds for a number of these issues. Hopefully this will get the bulk of you up and running in time for the weekend. If you are still affected, please continue to post and help each other out and we'll continue to make these blocking issues a priority.

The primary culprits for many of these issues remain out of date video drivers, interference from antivirus software, Windows administration rights, and errors within users' Windows setups. We're continuing to investigate these issues and are identifying fixes and workarounds wherever possible.

:D EV#52959 – Some are getting “The application will not run on a Windows guest account or an account with insufficient privileges” error, regardless of Admin status.
  • We have confirmed internally that this issue is not resolved by the BETA patch.
  • We believe this to be a result of WMI misconfiguration in a user's
    system. You can see if this is the case if your Windows is unable to see
    your system's hardware components (ie. processor, RAM, etc). You can
    verify if you are in this situation by doing the following:

    WinXP:
    1) Right click on My Computer and click on Properties
    2)
    Incorrect information will be displayed for your system's Processor and
    potentially other hardware components in the bottom right

    Win7/Vista
    1) Go to the Control Panel
    2) Click on System.
    3) You should see something similar to this: http://i.imgur.com/HN86i.jpg

    If
    this is what you're seeing, your WMI configuration has been corrupted.
    As a result, Windows is unable to determine your Processor and other
    hardware components and therefore DA2 is unable to determine your
    hardware components during activation.

    To fix this, you will need to rebuild your WMI repository. I
    want to stress that this fix is not for users who are not running as
    Administrators. You must be logged in as an Administrator. In
    addition, if you are at all uncomfortable with the process of touching
    your system's WMI files, please wait for a more official fix.

    WinXP:
    Download the WMI Diagnosis Utility from Microsoft's site and execute the VBS script within. http://www.microsoft...1E-4C64192AE97D

    Win7/Vista:
    1) Open a Command Prompt (Windows Key + R, then enter 'cmd')
    2) Within the command prompt, execute the following command: ' net stop winmgmt ' without quotations.
    3) Rename your Repository folder (%SystemRoot%\\System32\\WBEM\\Repository) just in case you wish to restore it.
    4) Within the command prompt, execute the following command: 'winmgmt /salvagerepository' without quotations.
    5) The above command will rebuild the repository if it is corrupted and then restart the WMI service.

    After your WMI repository has been rebuilt, please try and activate DA2. If you're still seeing the same symptoms, it could be that you're running on an older BIOS that needs to be updated. We've also had user reports of having to enter "c:\\>net localgroup administrators NetworkService /ADD" in the command prompt as a final step. Another user reports that their winmgmt service was disabled. They were able to run msconfig and enable it, then start winmgmt from the command prompt, which finally fixed it for them.
:wizard: EV#52957 – Some are getting a “Dragon Age II has stopped working” error
  • Users have confirmed that this issue is not resolved by the BETA patch.
  • Some (but not all) users have been able to resolve this issue by installing the latest ATI or Nvidia beta drivers. For more
    info about graphics drivers, see the DX11 thread -
    http://social.biowar...0/index/6420212
:wizard: EV#52973 – Some are getting a AWC.dll error
  • Early reports suggested that this was due to an outdated version of the Windows .NET Framework, but we no longer believe that to be the case. Instead, we now believe it to be related to Admin accounts. Some users are reporting that the issue is resolved by creating a new user with Admin rights in the Users control panel, then logging under that account to install and validate the game. After having done that, they were able to log back into their regular account to play the game.
:wizard: EV#53092 – Some are getting a black popup that disappears immediately.
  • We believe this is related to interference from anti-virus software.
    Users are reporting that the issue resolves if you turn off all
    anti-virus software as well as your Windows firewall and then reinstall.
:wizard: EV#53093 – Some are gettting partway through the release check progress bar, then crashing.
  • User reports suggest that this has to do with Administration privileges. Under Windows 7, you will need to run an elevated command prompt (basically run cmd.exe as administrator). Then you have to enable the hidden built-ina dministrator account for Windows 7 using the following command prompt: "C:\\windows\\system32>net user administrator active:yes"  ...Then log off of your account and log into the built-in administrator account where Dragon Age II should now run successfully. If you need more detailed instructions on the built in administrator go here - http://www.sevenforu...le-disable.html ...Windows Vista is essentially the same process - see http://support.microsoft.com/kb/555910
:wizard: EV#53094 – Some are failing silently after pressing Play.
  • User reports suggest this is resolved with the 1.01 BETA patch.
  • For Steam users unable to access the BETA patch, previous reports suggested that it might be tied to interference from AVG or other anti-virus software. Other reports suggest it might be related to graphics drivers.
:blink: EV#53095 - Some are getting a "Dragon Age II has encountered a problem and needs
to close. We are sorry for the inconvenience." error
  • We have more reports of this but are still trying to identify the cause.
:blink: EV#53198 - Some are getting a "The version of the file is not compatible with the version of windows your running" error
  • User reports suggest that it might be tied to interference from AVG or other anti-virus software. We're continuing to investigate.
  • A lot of users are reporting success from the following procedure: Under AVG settings, go to the "exceptions" tab
    under Resident Shield then unblock the activation software by adding this line to the "add path" tab:
    C:\\Users\\Username\\AppData\\Local\\Temp\\mtka_tmp ...It's possible this file is causing problems with other forms of anti-virus software as well.
:wizard: Some are successfully getting through release control but hitting the DX11 issues immediately upon launch. Some can’t access the launcher, however, and therefore can’t drop their settings down to DX9.
  • Definitely grab the latest ATI and Nvidia beta drivers, as described in the DX11 thread - http://social.biowar...0/index/6420212 ...Turn your settings down to DirectX9 if you can. If you can't run the launcher or config utility, there is a DX11 line in the DragonAge.ini file which you can set to UseDirectX11Renderer=0 - it doesn't exist until you run the game, however. Depending on when you're failing, you may not have an *.ini file to edit.

Modifié par Rob Bartel, 13 mars 2011 - 05:22 .


#2
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
UPDATE [March 10, 9:45pm MST]:
Some workarounds and user fixes are now available. These may not work in all cases and, as we've been unable to reproduce many of these issues internally, the bulk of our information remains user-reported. That said, if this information helps get you unstuck, please spread the word. Likewise, if the fixes don't help or if you have new solutions, please continue adding to this thread. Thanks for your help and patience - we know how frustrating it must be and we're frustrated by these issues too - we'd much rather you were in-game and playing than battling with the launch process.

:( EV#52959 – Some are getting “The application will not run on a Windows
guest account or an account with insufficient privileges” error,
regardless of Admin status.
  • We've succeeded in reproducing this internally but have not yet identified a fix. Some users have had this issue disappear but their fixes don't appear to be reproducible. We're continuing to work on this.
:wizard: EV#52957 – Some are getting a “Dragon Age II has stopped working” error
  • This issue appears to be related to graphics drivers and should fix itself if you install the latest ATI or Nvidia beta drivers. For more info about graphics drivers, see the DX11 thread - http://social.biowar...0/index/6420212
:wizard: EV#52973 – Some are getting a AWC.dll error
  • This appears to be due to computers having an outdated version of the Windows .NET Framework. If you perform a Windows Update, there should be an update to upgrade to .NET
    Framework 4. Grab that, and we believe that this issue will correct itself.
:wizard: EV#53092 – Some are getting a black popup that disappears immediately.
  • We believe this is related to interference from anti-virus software. Users are reporting that the issue resolves if you turn off all anti-virus software as well as your Windows firewall and then reinstall.
:wizard: EV#53093 – Some are gettting partway through the release check progress bar, then crashing.
  • User reports suggest that this has to do with Administration privileges. Under Windows 7, you will need to run an elevated command prompt (basically run cmd.exe as
    administrator). Then you have to enable the hidden built-ina dministrator account for Windows 7 using the following command prompt: "C:\\windows\\system32>net user administrator active:yes"  ...Then log off of your account and log into the built-in administrator account where Dragon Age II should now run successfully. If you need more detailed instructions on the built in administrator go here - http://www.sevenforu...le-disable.html ...Windows Vista is essentially the same process - see http://support.microsoft.com/kb/555910
:wizard: EV#53094 – Some are failing silently after pressing Play.
  • User reports suggest that it might be tied to interference from AVG or other anti-virus software. Other reports suggest it might be related to graphics drivers. At this point it remains unclear.
:alien: EV#53095
- Some are getting a "Dragon Age II has encountered a problem and needs
to close. We are sorry for the inconvenience." error
  • This may be a one-off. We haven't seen further reports of this. If you're blocked by it, please post to let us know.
:wizard: EV#53198 - Some are getting a "The version of the file is not compatible with the version of windows your running" error undow Windows Vista 64-bit
  • This is a new one. User reports suggest that it might be tied to interference from AVG or other anti-virus software, however.
:wizard: Some are
successfully getting through release control but hitting the DX11 issues
immediately upon launch. Some can’t access the launcher, however,
and therefore can’t drop their settings down to DX9.
  • Definitely grab the latest ATI and Nvidia beta drivers, as described in the DX11 thread - http://social.biowar...0/index/6420212 ...Turn your settings down to DirectX9 if you can. If you can't run the launcher or config utility, there is a DX11 line in the DragonAge.ini file which you can set to UseDirectX11Renderer=0 - it doesn't exist until you run the game, however. Depending on when you're failing, you may not have an *.ini file to edit.


#3
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
As I said, I know you're frustrated and so are we. We're definitely working on the issue on our end and have some further fixes and solutions pending. In the meantime, the workarounds proposed here are ones that have worked for some users - I've highlighted them in the interest of getting as many people unstuck as quickly as possible. I'm sorry that the workarounds aren't helping in your particular case.

#4
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages

Malcher wrote...


I have an instance of EV#53095 - "Dragon Age has encountered a problem
and needs to close". This happens right after clicking on "Play" button in the launcher (also when directly executing the game).

System information:
- Game on disk
- Win XP 32bit SP3
- Core 2 Duo P9500 @ 2.53GHz
- 3.0 GB RAM
- nVidia GT9600M GT (drivers 259.31)


I don't know if this will fix it but your drivers are out of date. You need the 267.24 BETA drivers. Report back and let us know if that fixed it.

Thanks!

#5
JamesLeung

JamesLeung
  • BioWare Employees
  • 40 messages
Hi everyone. Sorry for the long wait. We believe we may have a preliminary solution for the Admin error. To be specific, the issue where users are seeing this image when attempting to activate the game:

http://i352.photobuc.../shaoel/da2.jpg

We believe this to be a result of WMI misconfiguration in a user's system. You can see if this is the case if your Windows is unable to see your system's hardware components (ie. processor, RAM, etc). You can verify if you are in this situation by doing the following:

WinXP:
1) Right click on My Computer and click on Properties
2) Incorrect information will be displayed for your system's Processor and potentially other hardware components in the bottom right

Win7/Vista
1) Go to the Control Panel
2) Click on System.
3) You should see something similar to this: http://i.imgur.com/HN86i.jpg

If this is what you're seeing, your WMI configuration has been corrupted. As a result, Windows is unable to determine your Processor and other hardware components and therefore DA2 is unable to determine your hardware components during activation.

To fix this, you will need to rebuild your WMI repository. I want to stress that this fix is not for users who are not running as Administrators. You must be logged in as an Administrator. In addition, if you are at all uncomfortable with the process of touching your system's WMI files, please wait for a more official fix.

WinXP:
Download the WMI Diagnosis Utility from Microsoft's site and execute the VBS script within. http://www.microsoft...1E-4C64192AE97D

Win7/Vista:
1) Open a Command Prompt (Windows Key + R, then enter 'cmd')
2) Within the command prompt, execute the following command: ' net stop winmgmt ' without quotations.
3) Backup your Repository folder (%SystemRoot%\\System32\\WBEM\\Repository) just in case you wish to restore it
4) Within the command prompt, execute the following command: 'winmgmt /salvagerepository' without quotations.
5) The above command will rebuild the repository if it is corrupted and then restart the WMI service.


After your WMI repository has been rebuilt, please try and activate DA2.

Modifié par JamesLeung, 11 mars 2011 - 07:02 .


#6
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
A BETA patch is available to non-Steam-users and should fix any issues specifically related to the Release Control DRM. Other issues remain, however, and I'm keeping to opening post of this thread up-to-date with the latest issues, fixes and workarounds. Hopefully we can have most of you up and running in time for the weekend.

Thanks!

#7
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages

Ned Coleman wrote...

NO Solution for me! ...
Still get the error:The application will not run on a Windows guest account or an account with insufficient privileges... blablabla
I tried the WMI repository solution, and after this: c:>net localgroup administrators NetworkService /ADD

Still nothing, still the same problem. I can't play. Now what?


Is the System Information dialog still showing the symptom of no CPU or memory info? Can you confirm that you're renaming/destroying their current repository folder before running the 'winmgmt
/salvagerepository' command?

Thanks!

Modifié par Rob Bartel, 12 mars 2011 - 02:32 .


#8
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
Good to hear! Thank you for the update, LeetGoose.

#9
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
For those still experiencing the Admin error (EV#52959), are you still exhibiting the out-of-game symptoms described here:

"You can verify if you are in this situation by doing the following:

WinXP:
1) Right click on My Computer and click on Properties
2) Incorrect information will be displayed for your system's Processor and potentially other hardware components in the bottom right

Win7/Vista
1) Go to the Control Panel
2) Click on System.
3) You should see something similar to this: http://i.imgur.com/HN86i.jpg "

#10
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
Thanks chris2c2 - and just to be triple-sure can you confirm that you...
  • ...renamed/destroyed your current repository folder before running the 'winmgmt/salvagerepository' command?
  • ...ran the “net localgroup administrators NetworkService /ADD” command prompt?
Sorry - still trying to hammer this out with the engineers.

Modifié par Rob Bartel, 12 mars 2011 - 04:10 .


#11
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
Regarding the Admin problem, I've had another user reporting success with the following:

"Hi, i'm running Vista x64. I tried your fix, but it didn't work. You were right, that it is a winmgmt problem as in computer properties i had unavailible information for cpu and memory.

In my case your fix didn't work because the winmgmt service was disabled. I ran msconfig and enabled it. Then started winmgmt from comand promt. Than It worked. Hope this will help others."

#12
Rob Bartel

Rob Bartel
  • BioWare Employees
  • 444 messages
We're still here and we're still investigating. Nothing new to report as of yet. Sorry. =o(

#13
Allan Schumacher

Allan Schumacher
  • BioWare Employees
  • 7 640 messages

camhappybunny wrote...

So not impressed. Patch does the same thing as the beta patch: without it, the RDC at least starts, though it crashes before finishing. With it, I get absolutely nothing.

This burns me, because out of all of my friends, I've been the one to say, "Hey, if you enjoy a game, you should buy a legit copy. People spend years of their lives developing these things and we should support them. Downloading illegally is stealing..." and other sanctimonious things. Now, I'm about ready to ask one of my friends for his "source" just so I can make use of what I legally purchased. Maybe I'll just wait a decade for it to go on gog.com where I can buy it without DRM...

Bioware, please tell us that you or EA is seriously working on this and not planning to leave us all out to dry! The patch fixed the problem for some people, but not for me!


When you try running the game you say you get nothing.  Is this through the configuration utility (assuming you're not having issues with the configuration utility), or trying to run the game via bin_ship folder.

If absolutely nothing is happening, try installing Process Explorer and report back precisely what processes are trying to run, if any, when you click on play or try to run the game through bin_ship.

Just as a sanity check, have you tried the steps for repairing/rebuilding the WMI repository?


Please reply to the thread as it will let others in QA see the responses.  Thank you.


(note: Note, it makes sense that the Release Date Checker does not show up with the patch, as it has been stripped from the .exe)

Allan

#14
Luke Barrett

Luke Barrett
  • BioWare Employees
  • 1 638 messages
We've got a fix for this in the next patch. Unfortunately there were several different issues causing this awc.dll to display as having an error but we believe we've got them all.

#15
Luke Barrett

Luke Barrett
  • BioWare Employees
  • 1 638 messages
I believe you should just have to run the patch and *hopefully* all will be well.